DNS response history for c.zero52.com

c.zero52.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 33 DNS check records, 33 successful responses, 0 failed responses, and 1267 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 c.zero52.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

1267 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

27.133.136.165

Most recently resolved hosting IP on selected date

Successful Responses

33

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 c.zero52.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
33 2026-08-27 10:27 639234222943951923
257 ms 27.133.136.165
32 2026-08-27 10:10 639234212558002823
846 ms 27.133.136.165
31 2026-08-27 09:52 639234202117531850
268 ms 27.133.136.165
30 2026-08-27 09:35 639234191649612722
837 ms 27.133.136.165
29 2026-08-27 09:17 639234181105879568
860 ms 27.133.136.165
28 2026-08-27 09:00 639234170713214496
2435 ms 27.133.136.165
27 2026-08-27 08:43 639234160341037652
3162 ms 27.133.136.165
26 2026-08-27 08:25 639234149799404224
2280 ms 27.133.136.165
25 2026-08-27 08:08 639234139553286469
861 ms 27.133.136.165
24 2026-08-27 07:14 639234107183588293
859 ms 27.133.136.165
23 2026-08-27 06:57 639234096905435724
271 ms 27.133.136.165
22 2026-08-27 06:40 639234086579410775
269 ms 27.133.136.165
21 2026-08-27 06:22 639234076291157956
847 ms 27.133.136.165
20 2026-08-27 06:05 639234065981939454
845 ms 27.133.136.165
19 2026-08-27 05:48 639234055548642997
2330 ms 27.133.136.165
18 2026-08-27 05:31 639234045267979603
2250 ms 27.133.136.165
17 2026-08-27 05:14 639234034999717463
263 ms 27.133.136.165
16 2026-08-27 04:56 639234024739225358
268 ms 27.133.136.165
15 2026-08-27 04:39 639234014311170162
2257 ms 27.133.136.165
14 2026-08-27 04:22 639234003806017640
2247 ms 27.133.136.165
13 2026-08-27 04:04 639233993356203030
2246 ms 27.133.136.165
12 2026-08-27 03:11 639233961301716608
256 ms 27.133.136.165
11 2026-08-27 02:54 639233950834200647
2894 ms 27.133.136.165
10 2026-08-27 02:36 639233940431849026
2350 ms 27.133.136.165
9 2026-08-27 02:19 639233930110596398
847 ms 27.133.136.165
8 2026-08-27 02:02 639233919705434540
2513 ms 27.133.136.165
7 2026-08-27 01:44 639233909452807845
2494 ms 27.133.136.165
6 2026-08-27 01:27 639233899096420820
265 ms 27.133.136.165
5 2026-08-27 01:10 639233888707824939
270 ms 27.133.136.165
4 2026-08-27 00:53 639233878461203802
263 ms 27.133.136.165
3 2026-08-27 00:35 639233868060868209
282 ms 27.133.136.165
2 2026-08-27 00:18 639233857450922991
275 ms 27.133.136.165
1 2026-08-27 00:00 639233846871926285
2352 ms 27.133.136.165