DNS response history for ns2.pucitedu.net

ns2.pucitedu.net 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 550 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.pucitedu.net.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

550 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.147.169.220

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 ns2.pucitedu.net

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:46 639233370841350248
600 ms 202.147.169.220
33 2026-08-26 10:29 639233360361507238
838 ms 202.147.169.220
32 2026-08-26 10:11 639233350067824371
559 ms 202.147.169.220
31 2026-08-26 09:54 639233339545274518
628 ms 202.147.169.220
30 2026-08-26 09:37 639233329214918079
453 ms 202.147.169.220
29 2026-08-26 09:19 639233318749762337
402 ms 202.147.169.220
28 2026-08-26 09:02 639233308387917838
604 ms 202.147.169.220
27 2026-08-26 08:45 639233297961740122
577 ms 202.147.169.220
26 2026-08-26 08:27 639233287487159094
554 ms 202.147.169.220
25 2026-08-26 08:10 639233276995531707
554 ms 202.147.169.220
24 2026-08-26 07:52 639233266521568229
601 ms 202.147.169.220
23 2026-08-26 07:35 639233256081047431
574 ms 202.147.169.220
22 2026-08-26 06:41 639233223620132921
408 ms 202.147.169.220
21 2026-08-26 06:23 639233213287814244
571 ms 202.147.169.220
20 2026-08-26 06:06 639233202925983161
573 ms 202.147.169.220
19 2026-08-26 05:49 639233192644780696
570 ms 202.147.169.220
18 2026-08-26 05:32 639233182401183833
554 ms 202.147.169.220
17 2026-08-26 05:15 639233172074181051
595 ms 202.147.169.220
16 2026-08-26 04:57 639233161808421455
403 ms 202.147.169.220
15 2026-08-26 04:40 639233151357344052
579 ms 202.147.169.220
14 2026-08-26 04:23 639233141034116946
557 ms 202.147.169.220
13 2026-08-26 04:06 639233130828334142
601 ms 202.147.169.220
12 2026-08-26 03:49 639233120373450007
570 ms 202.147.169.220
11 2026-08-26 03:31 639233110066216193
598 ms 202.147.169.220
10 2026-08-26 02:38 639233078065410564
561 ms 202.147.169.220
9 2026-08-26 02:21 639233067787457832
601 ms 202.147.169.220
8 2026-08-26 02:04 639233057501801162
561 ms 202.147.169.220
7 2026-08-26 01:47 639233047089431703
396 ms 202.147.169.220
6 2026-08-26 01:29 639233036754790688
590 ms 202.147.169.220
5 2026-08-26 01:12 639233026412602472
563 ms 202.147.169.220
4 2026-08-26 00:55 639233016064066127
395 ms 202.147.169.220
3 2026-08-26 00:38 639233005922655772
558 ms 202.147.169.220
2 2026-08-26 00:21 639232995672256907
405 ms 202.147.169.220
1 2026-08-26 00:03 639232985300872416
562 ms 202.147.169.220