DNS response history for ns2.puripranayam.co

ns2.puripranayam.co 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, 33 successful responses, 0 failed responses, and 299 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.puripranayam.co.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

299 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.116.232.128

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.puripranayam.co

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:41 639233370841350248
272 ms 66.116.232.128
32 2026-08-26 10:24 639233360361507238
258 ms 66.116.232.128
31 2026-08-26 10:07 639233350067824371
270 ms 66.116.232.128
30 2026-08-26 09:50 639233339545274518
267 ms 66.116.232.128
29 2026-08-26 09:32 639233329214918079
254 ms 66.116.232.128
28 2026-08-26 09:15 639233318749762337
250 ms 66.116.232.128
27 2026-08-26 08:57 639233308387917838
250 ms 66.116.232.128
26 2026-08-26 08:40 639233297961740122
253 ms 66.116.232.128
25 2026-08-26 08:23 639233287487159094
257 ms 66.116.232.128
24 2026-08-26 08:05 639233276995531707
264 ms 66.116.232.128
23 2026-08-26 07:48 639233266521568229
258 ms 66.116.232.128
22 2026-08-26 07:30 639233256081047431
184 ms 66.116.232.128
21 2026-08-26 06:36 639233223620132921
250 ms 66.116.232.128
20 2026-08-26 06:19 639233213287814244
266 ms 66.116.232.128
19 2026-08-26 06:02 639233202925983161
259 ms 66.116.232.128
18 2026-08-26 05:44 639233192644780696
259 ms 66.116.232.128
17 2026-08-26 05:27 639233182401183833
253 ms 66.116.232.128
16 2026-08-26 05:10 639233172074181051
135 ms 66.116.232.128
15 2026-08-26 04:53 639233161808421455
254 ms 66.116.232.128
14 2026-08-26 04:36 639233151357344052
264 ms 66.116.232.128
13 2026-08-26 04:18 639233141034116946
266 ms 66.116.232.128
12 2026-08-26 04:01 639233130828334142
252 ms 66.116.232.128
11 2026-08-26 03:44 639233120373450007
131 ms 66.116.232.128
10 2026-08-26 03:27 639233110066216193
2134 ms 66.116.232.128
9 2026-08-26 02:34 639233078065410564
270 ms 66.116.232.128
8 2026-08-26 02:16 639233067787457832
268 ms 66.116.232.128
7 2026-08-26 01:59 639233057501801162
261 ms 66.116.232.128
6 2026-08-26 01:42 639233047089431703
256 ms 66.116.232.128
5 2026-08-26 01:25 639233036754790688
3 ms 66.116.232.128
4 2026-08-26 01:08 639233026412602472
248 ms 66.116.232.128
3 2026-08-26 00:50 639233016064066127
261 ms 66.116.232.128
2 2026-08-26 00:33 639233005922655772
255 ms 66.116.232.128
1 2026-08-26 00:16 639232995672256907
272 ms 66.116.232.128