DNS response history for ns2.policesecretariat.gov.za

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

33

Historical checks stored for this nameserver on selected date

Average Latency

404 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:49

All timestamps shown in UTC

Latest Resolved IP on Selected Date

164.151.136.131

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 ns2.policesecretariat.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
33 2026-08-25 11:49 639232545839529039
354 ms 164.151.136.131
32 2026-08-25 11:32 639232535349285207
353 ms 164.151.136.131
31 2026-08-25 11:15 639232524938080723
353 ms 164.151.136.131
30 2026-08-25 10:21 639232492740373468
185 ms 164.151.136.131
29 2026-08-25 10:04 639232482235303141
369 ms 164.151.136.131
28 2026-08-25 09:46 639232471861770303
354 ms 164.151.136.131
27 2026-08-25 09:29 639232461630217327
353 ms 164.151.136.131
26 2026-08-25 09:12 639232451282965990
346 ms 164.151.136.131
25 2026-08-25 08:55 639232440814614938
351 ms 164.151.136.131
24 2026-08-25 08:37 639232430410720425
355 ms 164.151.136.131
23 2026-08-25 08:20 639232420003096185
524 ms 164.151.136.131
22 2026-08-25 08:02 639232409467287444
352 ms 164.151.136.131
21 2026-08-25 07:45 639232399077195997
355 ms 164.151.136.131
20 2026-08-25 07:28 639232388731528337
354 ms 164.151.136.131
19 2026-08-25 07:10 639232378288598612
354 ms 164.151.136.131
18 2026-08-25 06:17 639232346196373643
352 ms 164.151.136.131
17 2026-08-25 06:00 639232336112370741
354 ms 164.151.136.131
16 2026-08-25 05:43 639232326146508970
352 ms 164.151.136.131
15 2026-08-25 05:26 639232316189381720
532 ms 164.151.136.131
14 2026-08-25 05:10 639232306217998913
523 ms 164.151.136.131
13 2026-08-25 04:53 639232296255744174
531 ms 164.151.136.131
12 2026-08-25 04:36 639232286095760789
519 ms 164.151.136.131
11 2026-08-25 04:19 639232276086186273
522 ms 164.151.136.131
10 2026-08-25 04:03 639232265900986425
521 ms 164.151.136.131
9 2026-08-25 03:46 639232255723518075
526 ms 164.151.136.131
8 2026-08-25 03:29 639232245484452890
335 ms 164.151.136.131
7 2026-08-25 03:12 639232235157175331
353 ms 164.151.136.131
6 2026-08-25 02:18 639232203197189095
525 ms 164.151.136.131
5 2026-08-25 02:01 639232192844564298
490 ms 164.151.136.131
4 2026-08-25 01:44 639232182496008942
352 ms 164.151.136.131
3 2026-08-25 01:27 639232172197053132
351 ms 164.151.136.131
2 2026-08-25 00:33 639232140250307418
352 ms 164.151.136.131
1 2026-08-25 00:16 639232129927860324
526 ms 164.151.136.131