DNS response history for ns2.prposts.site

ns2.prposts.site 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 32 DNS check records, 32 successful responses, 0 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.prposts.site.
Records on Selected Date

32

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:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

191.101.233.201

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 ns2.prposts.site

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
32 2026-08-26 10:24 639233360361507238
324 ms 191.101.233.201
31 2026-08-26 10:07 639233350067824371
320 ms 191.101.233.201
30 2026-08-26 09:49 639233339545274518
313 ms 191.101.233.201
29 2026-08-26 09:32 639233329214918079
326 ms 191.101.233.201
28 2026-08-26 09:15 639233318749762337
321 ms 191.101.233.201
27 2026-08-26 08:57 639233308387917838
317 ms 191.101.233.201
26 2026-08-26 08:40 639233297961740122
326 ms 191.101.233.201
25 2026-08-26 08:22 639233287487159094
318 ms 191.101.233.201
24 2026-08-26 08:05 639233276995531707
340 ms 191.101.233.201
23 2026-08-26 07:47 639233266521568229
317 ms 191.101.233.201
22 2026-08-26 07:30 639233256081047431
318 ms 191.101.233.201
21 2026-08-26 06:36 639233223620132921
316 ms 191.101.233.201
20 2026-08-26 06:19 639233213287814244
313 ms 191.101.233.201
19 2026-08-26 06:01 639233202925983161
316 ms 191.101.233.201
18 2026-08-26 05:44 639233192644780696
381 ms 191.101.233.201
17 2026-08-26 05:27 639233182401183833
312 ms 191.101.233.201
16 2026-08-26 05:10 639233172074181051
323 ms 191.101.233.201
15 2026-08-26 04:53 639233161808421455
316 ms 191.101.233.201
14 2026-08-26 04:36 639233151357344052
311 ms 191.101.233.201
13 2026-08-26 04:18 639233141034116946
318 ms 191.101.233.201
12 2026-08-26 04:01 639233130828334142
313 ms 191.101.233.201
11 2026-08-26 03:44 639233120373450007
312 ms 191.101.233.201
10 2026-08-26 03:27 639233110066216193
311 ms 191.101.233.201
9 2026-08-26 02:33 639233078065410564
191 ms 191.101.233.201
8 2026-08-26 02:16 639233067787457832
336 ms 191.101.233.201
7 2026-08-26 01:59 639233057501801162
314 ms 191.101.233.201
6 2026-08-26 01:42 639233047089431703
318 ms 191.101.233.201
5 2026-08-26 01:25 639233036754790688
316 ms 191.101.233.201
4 2026-08-26 01:07 639233026412602472
312 ms 191.101.233.201
3 2026-08-26 00:50 639233016064066127
313 ms 191.101.233.201
2 2026-08-26 00:33 639233005922655772
31 ms 191.101.233.201
1 2026-08-26 00:16 639232995672256907
282 ms 191.101.233.201