DNS response history for ns2.fightprofile.net

ns2.fightprofile.net is a DNS nameserver monitored by NameServerHistory. This page provides historical DNS response-time data, nameserver uptime signals, DNS latency observations, resolved IP history, successful response counts, failed response counts, and reliability indicators for this nameserver.

The selected UTC date is 2026-08-27. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 157 ms average response time. Current selected-date status: At least one successful DNS response was recorded for the selected date.

  • Use this report to investigate historical DNS uptime and nameserver reliability.
  • Compare DNS latency changes, failed DNS checks, and response behavior over time.
  • Review the latest resolved IP address and raw DNS check history for ns2.fightprofile.net.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

157 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:04

All timestamps shown in UTC

Latest Resolved IP on Selected Date

173.249.20.11

Most recently resolved hosting IP on selected date

Successful Responses

35

Checks that returned a measurable response

Failed Responses

0

Checks with no response or no returned latency

Failure Rate

0%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.fightprofile.net

Showing DNS history for 2026-08-27 UTC. Newest records appear first.

Latency bars are scaled to a maximum of 5000 ms for quick visual comparison.

# Query Time (UTC) Correlation ID Latency Response IP Address
35 2026-08-27 11:04 639234253963286387
31 ms 173.249.20.11
34 2026-08-27 10:47 639234243654907465
48 ms 173.249.20.11
33 2026-08-27 10:30 639234233269654413
55 ms 173.249.20.11
32 2026-08-27 10:13 639234222943951923
55 ms 173.249.20.11
31 2026-08-27 09:55 639234212558002823
53 ms 173.249.20.11
30 2026-08-27 09:38 639234202117531850
51 ms 173.249.20.11
29 2026-08-27 09:20 639234191649612722
45 ms 173.249.20.11
28 2026-08-27 09:03 639234181105879568
34 ms 173.249.20.11
27 2026-08-27 08:46 639234170713214496
46 ms 173.249.20.11
26 2026-08-27 08:28 639234160341037652
36 ms 173.249.20.11
25 2026-08-27 08:11 639234149799404224
35 ms 173.249.20.11
24 2026-08-27 07:54 639234139553286469
41 ms 173.249.20.11
23 2026-08-27 07:00 639234107183588293
34 ms 173.249.20.11
22 2026-08-27 06:43 639234096905435724
39 ms 173.249.20.11
21 2026-08-27 06:25 639234086579410775
33 ms 173.249.20.11
20 2026-08-27 06:08 639234076291157956
71 ms 173.249.20.11
19 2026-08-27 05:51 639234065981939454
34 ms 173.249.20.11
18 2026-08-27 05:34 639234055548642997
36 ms 173.249.20.11
17 2026-08-27 05:17 639234045267979603
56 ms 173.249.20.11
16 2026-08-27 04:59 639234034999717463
57 ms 173.249.20.11
15 2026-08-27 04:42 639234024739225358
4017 ms 173.249.20.11
14 2026-08-27 04:25 639234014311170162
81 ms 173.249.20.11
13 2026-08-27 04:07 639234003806017640
32 ms 173.249.20.11
12 2026-08-27 03:50 639233993356203030
59 ms 173.249.20.11
11 2026-08-27 02:57 639233961301716608
43 ms 173.249.20.11
10 2026-08-27 02:39 639233950834200647
39 ms 173.249.20.11
9 2026-08-27 02:22 639233940431849026
35 ms 173.249.20.11
8 2026-08-27 02:05 639233930110596398
49 ms 173.249.20.11
7 2026-08-27 01:47 639233919705434540
38 ms 173.249.20.11
6 2026-08-27 01:30 639233909452807845
40 ms 173.249.20.11
5 2026-08-27 01:13 639233899096420820
33 ms 173.249.20.11
4 2026-08-27 00:56 639233888707824939
43 ms 173.249.20.11
3 2026-08-27 00:39 639233878461203802
40 ms 173.249.20.11
2 2026-08-27 00:21 639233868060868209
35 ms 173.249.20.11
1 2026-08-27 00:03 639233857450922991
36 ms 173.249.20.11