DNS response history for ns1.belabela.gov.za

ns1.belabela.gov.za 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-25. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 435 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 ns1.belabela.gov.za.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

435 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

164.151.136.18

Most recently resolved hosting IP on selected date

Successful Responses

32

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 ns1.belabela.gov.za

Showing DNS history for 2026-08-25 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
32 2026-08-25 11:32 639232535349285207
356 ms 164.151.136.18
31 2026-08-25 11:15 639232524938080723
185 ms 164.151.136.18
30 2026-08-25 10:21 639232492740373468
182 ms 164.151.136.18
29 2026-08-25 10:04 639232482235303141
182 ms 164.151.136.18
28 2026-08-25 09:46 639232471861770303
531 ms 164.151.136.18
27 2026-08-25 09:29 639232461630217327
549 ms 164.151.136.18
26 2026-08-25 09:12 639232451282965990
545 ms 164.151.136.18
25 2026-08-25 08:55 639232440814614938
352 ms 164.151.136.18
24 2026-08-25 08:37 639232430410720425
523 ms 164.151.136.18
23 2026-08-25 08:20 639232420003096185
183 ms 164.151.136.18
22 2026-08-25 08:03 639232409467287444
363 ms 164.151.136.18
21 2026-08-25 07:45 639232399077195997
524 ms 164.151.136.18
20 2026-08-25 07:28 639232388731528337
189 ms 164.151.136.18
19 2026-08-25 07:10 639232378288598612
368 ms 164.151.136.18
18 2026-08-25 06:17 639232346196373643
364 ms 164.151.136.18
17 2026-08-25 06:00 639232336112370741
3175 ms 164.151.136.18
16 2026-08-25 05:43 639232326146508970
353 ms 164.151.136.18
15 2026-08-25 05:27 639232316189381720
704 ms 164.151.136.18
14 2026-08-25 05:10 639232306217998913
521 ms 164.151.136.18
13 2026-08-25 04:53 639232296255744174
194 ms 164.151.136.18
12 2026-08-25 04:37 639232286095760789
531 ms 164.151.136.18
11 2026-08-25 04:20 639232276086186273
184 ms 164.151.136.18
10 2026-08-25 04:03 639232265900986425
376 ms 164.151.136.18
9 2026-08-25 03:46 639232255723518075
187 ms 164.151.136.18
8 2026-08-25 03:29 639232245484452890
182 ms 164.151.136.18
7 2026-08-25 03:12 639232235157175331
351 ms 164.151.136.18
6 2026-08-25 02:18 639232203197189095
182 ms 164.151.136.18
5 2026-08-25 02:01 639232192844564298
185 ms 164.151.136.18
4 2026-08-25 01:44 639232182496008942
521 ms 164.151.136.18
3 2026-08-25 01:27 639232172197053132
179 ms 164.151.136.18
2 2026-08-25 00:33 639232140250307418
192 ms 164.151.136.18
1 2026-08-25 00:17 639232129927860324
519 ms 164.151.136.18