DNS response history for ns2.prsidepok.com

ns2.prsidepok.com 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 33 DNS check records, 32 successful responses, 1 failed responses, and 306 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.prsidepok.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

306 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

94.23.156.169

Most recently resolved hosting IP on selected date

Successful Responses

32

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.prsidepok.com

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
33 2026-08-26 10:36 639233370841350248
2082 ms 94.23.156.169
32 2026-08-26 10:19 639233360361507238
67 ms 94.23.156.169
31 2026-08-26 10:02 639233350067824371
31 ms 94.23.156.169
30 2026-08-26 09:45 639233339545274518
8 ms 94.23.156.169
29 2026-08-26 09:27 639233329214918079
33 ms 94.23.156.169
28 2026-08-26 09:10 639233318749762337
42 ms 94.23.156.169
27 2026-08-26 08:53 639233308387917838
93 ms 94.23.156.169
26 2026-08-26 08:35 639233297961740122
12 ms 94.23.156.169
25 2026-08-26 08:18 639233287487159094
87 ms 94.23.156.169
24 2026-08-26 08:00 639233276995531707
58 ms 94.23.156.169
23 2026-08-26 07:43 639233266521568229
54 ms 94.23.156.169
22 2026-08-26 07:25 639233256081047431
43 ms 94.23.156.169
21 2026-08-26 06:31 639233223620132921
82 ms 94.23.156.169
20 2026-08-26 06:14 639233213287814244
71 ms 94.23.156.169
19 2026-08-26 05:57 639233202925983161
-
18 2026-08-26 05:40 639233192644780696
2033 ms 94.23.156.169
17 2026-08-26 05:22 639233182401183833
34 ms 94.23.156.169
16 2026-08-26 05:05 639233172074181051
168 ms 94.23.156.169
15 2026-08-26 04:48 639233161808421455
122 ms 94.23.156.169
14 2026-08-26 04:31 639233151357344052
40 ms 94.23.156.169
13 2026-08-26 04:14 639233141034116946
57 ms 94.23.156.169
12 2026-08-26 03:57 639233130828334142
33 ms 94.23.156.169
11 2026-08-26 03:39 639233120373450007
37 ms 94.23.156.169
10 2026-08-26 03:22 639233110066216193
38 ms 94.23.156.169
9 2026-08-26 02:29 639233078065410564
23 ms 94.23.156.169
8 2026-08-26 02:12 639233067787457832
45 ms 94.23.156.169
7 2026-08-26 01:54 639233057501801162
2050 ms 94.23.156.169
6 2026-08-26 01:37 639233047089431703
2028 ms 94.23.156.169
5 2026-08-26 01:20 639233036754790688
60 ms 94.23.156.169
4 2026-08-26 01:03 639233026412602472
37 ms 94.23.156.169
3 2026-08-26 00:45 639233016064066127
145 ms 94.23.156.169
2 2026-08-26 00:28 639233005922655772
42 ms 94.23.156.169
1 2026-08-26 00:11 639232995672256907
46 ms 94.23.156.169