DNS response history for b.ns.zaps.org

b.ns.zaps.org 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-26. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 639 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.ns.zaps.org.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

639 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

158.101.137.238

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 b.ns.zaps.org

Showing DNS history for 2026-08-26 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-26 11:39 639233403515141099
971 ms 158.101.137.238
34 2026-08-26 10:44 639233370841350248
673 ms 158.101.137.238
33 2026-08-26 10:27 639233360361507238
672 ms 158.101.137.238
32 2026-08-26 10:10 639233350067824371
599 ms 158.101.137.238
31 2026-08-26 09:53 639233339545274518
4 ms 158.101.137.238
30 2026-08-26 09:35 639233329214918079
1007 ms 158.101.137.238
29 2026-08-26 09:18 639233318749762337
528 ms 158.101.137.238
28 2026-08-26 09:00 639233308387917838
858 ms 158.101.137.238
27 2026-08-26 08:43 639233297961740122
297 ms 158.101.137.238
26 2026-08-26 08:26 639233287487159094
852 ms 158.101.137.238
25 2026-08-26 08:08 639233276995531707
328 ms 158.101.137.238
24 2026-08-26 07:51 639233266521568229
960 ms 158.101.137.238
23 2026-08-26 07:33 639233256081047431
724 ms 158.101.137.238
22 2026-08-26 06:39 639233223620132921
1000 ms 158.101.137.238
21 2026-08-26 06:22 639233213287814244
730 ms 158.101.137.238
20 2026-08-26 06:05 639233202925983161
2550 ms 158.101.137.238
19 2026-08-26 05:47 639233192644780696
326 ms 158.101.137.238
18 2026-08-26 05:30 639233182401183833
682 ms 158.101.137.238
17 2026-08-26 05:13 639233172074181051
722 ms 158.101.137.238
16 2026-08-26 04:56 639233161808421455
501 ms 158.101.137.238
15 2026-08-26 04:39 639233151357344052
248 ms 158.101.137.238
14 2026-08-26 04:21 639233141034116946
244 ms 158.101.137.238
13 2026-08-26 04:04 639233130828334142
747 ms 158.101.137.238
12 2026-08-26 03:47 639233120373450007
731 ms 158.101.137.238
11 2026-08-26 03:30 639233110066216193
296 ms 158.101.137.238
10 2026-08-26 02:37 639233078065410564
772 ms 158.101.137.238
9 2026-08-26 02:19 639233067787457832
7 ms 158.101.137.238
8 2026-08-26 02:02 639233057501801162
505 ms 158.101.137.238
7 2026-08-26 01:45 639233047089431703
969 ms 158.101.137.238
6 2026-08-26 01:28 639233036754790688
7 ms 158.101.137.238
5 2026-08-26 01:11 639233026412602472
862 ms 158.101.137.238
4 2026-08-26 00:53 639233016064066127
483 ms 158.101.137.238
3 2026-08-26 00:36 639233005922655772
247 ms 158.101.137.238
2 2026-08-26 00:19 639232995672256907
481 ms 158.101.137.238
1 2026-08-26 00:02 639232985300872416
770 ms 158.101.137.238