DNS response history for ns2.persal.gov.za

ns2.persal.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 36 DNS check records, 36 successful responses, 0 failed responses, and 365 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 ns2.persal.gov.za.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

365 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

164.151.131.147

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 ns2.persal.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
36 2026-08-25 12:41 639232576780683689
192 ms 164.151.131.147
35 2026-08-25 12:24 639232566381512620
354 ms 164.151.131.147
34 2026-08-25 12:07 639232556111768563
356 ms 164.151.131.147
33 2026-08-25 11:49 639232545839529039
526 ms 164.151.131.147
32 2026-08-25 11:32 639232535349285207
716 ms 164.151.131.147
31 2026-08-25 11:15 639232524938080723
334 ms 164.151.131.147
30 2026-08-25 10:21 639232492740373468
351 ms 164.151.131.147
29 2026-08-25 10:04 639232482235303141
184 ms 164.151.131.147
28 2026-08-25 09:46 639232471861770303
545 ms 164.151.131.147
27 2026-08-25 09:29 639232461630217327
522 ms 164.151.131.147
26 2026-08-25 09:12 639232451282965990
184 ms 164.151.131.147
25 2026-08-25 08:55 639232440814614938
532 ms 164.151.131.147
24 2026-08-25 08:37 639232430410720425
505 ms 164.151.131.147
23 2026-08-25 08:20 639232420003096185
183 ms 164.151.131.147
22 2026-08-25 08:02 639232409467287444
186 ms 164.151.131.147
21 2026-08-25 07:45 639232399077195997
362 ms 164.151.131.147
20 2026-08-25 07:28 639232388731528337
184 ms 164.151.131.147
19 2026-08-25 07:10 639232378288598612
703 ms 164.151.131.147
18 2026-08-25 06:16 639232346196373643
418 ms 164.151.131.147
17 2026-08-25 06:00 639232336112370741
529 ms 164.151.131.147
16 2026-08-25 05:43 639232326146508970
185 ms 164.151.131.147
15 2026-08-25 05:26 639232316189381720
543 ms 164.151.131.147
14 2026-08-25 05:10 639232306217998913
183 ms 164.151.131.147
13 2026-08-25 04:53 639232296255744174
441 ms 164.151.131.147
12 2026-08-25 04:36 639232286095760789
185 ms 164.151.131.147
11 2026-08-25 04:19 639232276086186273
183 ms 164.151.131.147
10 2026-08-25 04:03 639232265900986425
334 ms 164.151.131.147
9 2026-08-25 03:46 639232255723518075
531 ms 164.151.131.147
8 2026-08-25 03:29 639232245484452890
184 ms 164.151.131.147
7 2026-08-25 03:12 639232235157175331
363 ms 164.151.131.147
6 2026-08-25 02:18 639232203197189095
182 ms 164.151.131.147
5 2026-08-25 02:01 639232192844564298
353 ms 164.151.131.147
4 2026-08-25 01:44 639232182496008942
3 ms 164.151.131.147
3 2026-08-25 01:27 639232172197053132
544 ms 164.151.131.147
2 2026-08-25 00:33 639232140250307418
546 ms 164.151.131.147
1 2026-08-25 00:16 639232129927860324
520 ms 164.151.131.147