DNS response history for b.zero52.net

b.zero52.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 36 DNS check records, 36 successful responses, 0 failed responses, and 359 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 b.zero52.net.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

359 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

27.133.136.167

Most recently resolved hosting IP on selected date

Successful Responses

36

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 b.zero52.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
36 2026-08-27 12:11 639234286253196126
264 ms 27.133.136.167
35 2026-08-27 11:17 639234253963286387
386 ms 27.133.136.167
34 2026-08-27 11:00 639234243654907465
372 ms 27.133.136.167
33 2026-08-27 10:43 639234233269654413
376 ms 27.133.136.167
32 2026-08-27 10:25 639234222943951923
262 ms 27.133.136.167
31 2026-08-27 10:08 639234212558002823
535 ms 27.133.136.167
30 2026-08-27 09:51 639234202117531850
359 ms 27.133.136.167
29 2026-08-27 09:33 639234191649612722
259 ms 27.133.136.167
28 2026-08-27 09:16 639234181105879568
254 ms 27.133.136.167
27 2026-08-27 08:58 639234170713214496
257 ms 27.133.136.167
26 2026-08-27 08:41 639234160341037652
347 ms 27.133.136.167
25 2026-08-27 08:24 639234149799404224
532 ms 27.133.136.167
24 2026-08-27 08:06 639234139553286469
532 ms 27.133.136.167
23 2026-08-27 07:12 639234107183588293
254 ms 27.133.136.167
22 2026-08-27 06:55 639234096905435724
260 ms 27.133.136.167
21 2026-08-27 06:38 639234086579410775
403 ms 27.133.136.167
20 2026-08-27 06:21 639234076291157956
351 ms 27.133.136.167
19 2026-08-27 06:04 639234065981939454
272 ms 27.133.136.167
18 2026-08-27 05:47 639234055548642997
346 ms 27.133.136.167
17 2026-08-27 05:29 639234045267979603
265 ms 27.133.136.167
16 2026-08-27 05:12 639234034999717463
313 ms 27.133.136.167
15 2026-08-27 04:55 639234024739225358
252 ms 27.133.136.167
14 2026-08-27 04:38 639234014311170162
266 ms 27.133.136.167
13 2026-08-27 04:20 639234003806017640
392 ms 27.133.136.167
12 2026-08-27 04:03 639233993356203030
261 ms 27.133.136.167
11 2026-08-27 03:09 639233961301716608
423 ms 27.133.136.167
10 2026-08-27 02:52 639233950834200647
419 ms 27.133.136.167
9 2026-08-27 02:35 639233940431849026
362 ms 27.133.136.167
8 2026-08-27 02:17 639233930110596398
552 ms 27.133.136.167
7 2026-08-27 02:00 639233919705434540
536 ms 27.133.136.167
6 2026-08-27 01:43 639233909452807845
256 ms 27.133.136.167
5 2026-08-27 01:26 639233899096420820
266 ms 27.133.136.167
4 2026-08-27 01:08 639233888707824939
532 ms 27.133.136.167
3 2026-08-27 00:51 639233878461203802
377 ms 27.133.136.167
2 2026-08-27 00:34 639233868060868209
537 ms 27.133.136.167
1 2026-08-27 00:17 639233857450922991
301 ms 27.133.136.167