DNS response history for fifty1.com

fifty1.com 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 144 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 fifty1.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

144 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

92.205.180.135

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 fifty1.com

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
24 ms 92.205.180.135
34 2026-08-27 10:47 639234243654907465
3 ms 92.205.180.135
33 2026-08-27 10:29 639234233269654413
49 ms 92.205.180.135
32 2026-08-27 10:12 639234222943951923
51 ms 92.205.180.135
31 2026-08-27 09:55 639234212558002823
2095 ms 92.205.180.135
30 2026-08-27 09:37 639234202117531850
4 ms 92.205.180.135
29 2026-08-27 09:20 639234191649612722
43 ms 92.205.180.135
28 2026-08-27 09:02 639234181105879568
17 ms 92.205.180.135
27 2026-08-27 08:45 639234170713214496
22 ms 92.205.180.135
26 2026-08-27 08:28 639234160341037652
26 ms 92.205.180.135
25 2026-08-27 08:10 639234149799404224
30 ms 92.205.180.135
24 2026-08-27 07:53 639234139553286469
2028 ms 92.205.180.135
23 2026-08-27 06:59 639234107183588293
52 ms 92.205.180.135
22 2026-08-27 06:42 639234096905435724
53 ms 92.205.180.135
21 2026-08-27 06:25 639234086579410775
34 ms 92.205.180.135
20 2026-08-27 06:08 639234076291157956
27 ms 92.205.180.135
19 2026-08-27 05:51 639234065981939454
49 ms 92.205.180.135
18 2026-08-27 05:33 639234055548642997
31 ms 92.205.180.135
17 2026-08-27 05:16 639234045267979603
27 ms 92.205.180.135
16 2026-08-27 04:59 639234034999717463
13 ms 92.205.180.135
15 2026-08-27 04:42 639234024739225358
23 ms 92.205.180.135
14 2026-08-27 04:25 639234014311170162
36 ms 92.205.180.135
13 2026-08-27 04:07 639234003806017640
42 ms 92.205.180.135
12 2026-08-27 03:50 639233993356203030
18 ms 92.205.180.135
11 2026-08-27 02:56 639233961301716608
15 ms 92.205.180.135
10 2026-08-27 02:39 639233950834200647
24 ms 92.205.180.135
9 2026-08-27 02:21 639233940431849026
17 ms 92.205.180.135
8 2026-08-27 02:04 639233930110596398
20 ms 92.205.180.135
7 2026-08-27 01:47 639233919705434540
35 ms 92.205.180.135
6 2026-08-27 01:30 639233909452807845
39 ms 92.205.180.135
5 2026-08-27 01:12 639233899096420820
22 ms 92.205.180.135
4 2026-08-27 00:55 639233888707824939
15 ms 92.205.180.135
3 2026-08-27 00:38 639233878461203802
19 ms 92.205.180.135
2 2026-08-27 00:21 639233868060868209
17 ms 92.205.180.135
1 2026-08-27 00:03 639233857450922991
18 ms 92.205.180.135