DNS response history for ns1.policesecretariat.gov.za

ns1.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-26. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 497 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.policesecretariat.gov.za.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

497 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

164.151.136.130

Most recently resolved hosting IP on selected date

Successful Responses

34

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.policesecretariat.gov.za

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
34 2026-08-26 10:44 639233370841350248
535 ms 164.151.136.130
33 2026-08-26 10:27 639233360361507238
183 ms 164.151.136.130
32 2026-08-26 10:10 639233350067824371
351 ms 164.151.136.130
31 2026-08-26 09:53 639233339545274518
349 ms 164.151.136.130
30 2026-08-26 09:35 639233329214918079
352 ms 164.151.136.130
29 2026-08-26 09:18 639233318749762337
418 ms 164.151.136.130
28 2026-08-26 09:00 639233308387917838
181 ms 164.151.136.130
27 2026-08-26 08:43 639233297961740122
353 ms 164.151.136.130
26 2026-08-26 08:26 639233287487159094
357 ms 164.151.136.130
25 2026-08-26 08:08 639233276995531707
528 ms 164.151.136.130
24 2026-08-26 07:51 639233266521568229
2339 ms 164.151.136.130
23 2026-08-26 07:33 639233256081047431
519 ms 164.151.136.130
22 2026-08-26 06:39 639233223620132921
522 ms 164.151.136.130
21 2026-08-26 06:22 639233213287814244
184 ms 164.151.136.130
20 2026-08-26 06:05 639233202925983161
179 ms 164.151.136.130
19 2026-08-26 05:47 639233192644780696
2503 ms 164.151.136.130
18 2026-08-26 05:30 639233182401183833
180 ms 164.151.136.130
17 2026-08-26 05:13 639233172074181051
352 ms 164.151.136.130
16 2026-08-26 04:56 639233161808421455
525 ms 164.151.136.130
15 2026-08-26 04:39 639233151357344052
329 ms 164.151.136.130
14 2026-08-26 04:21 639233141034116946
518 ms 164.151.136.130
13 2026-08-26 04:04 639233130828334142
184 ms 164.151.136.130
12 2026-08-26 03:47 639233120373450007
522 ms 164.151.136.130
11 2026-08-26 03:30 639233110066216193
182 ms 164.151.136.130
10 2026-08-26 02:37 639233078065410564
185 ms 164.151.136.130
9 2026-08-26 02:19 639233067787457832
223 ms 164.151.136.130
8 2026-08-26 02:02 639233057501801162
522 ms 164.151.136.130
7 2026-08-26 01:45 639233047089431703
522 ms 164.151.136.130
6 2026-08-26 01:28 639233036754790688
330 ms 164.151.136.130
5 2026-08-26 01:11 639233026412602472
522 ms 164.151.136.130
4 2026-08-26 00:53 639233016064066127
361 ms 164.151.136.130
3 2026-08-26 00:36 639233005922655772
524 ms 164.151.136.130
2 2026-08-26 00:19 639232995672256907
533 ms 164.151.136.130
1 2026-08-26 00:02 639232985300872416
522 ms 164.151.136.130