DNS response history for ns2.p2j.co

ns2.p2j.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-25. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 574 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.p2j.co.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

574 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:22

All timestamps shown in UTC

Latest Resolved IP on Selected Date

172.237.150.251

Most recently resolved hosting IP on selected date

Successful Responses

31

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

Showing DNS history for 2026-08-25 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
31 2026-08-25 10:22 639232492740373468
536 ms 172.237.150.251
30 2026-08-25 10:04 639232482235303141
551 ms 172.237.150.251
29 2026-08-25 09:47 639232471861770303
539 ms 172.237.150.251
28 2026-08-25 09:30 639232461630217327
539 ms 172.237.150.251
27 2026-08-25 09:13 639232451282965990
541 ms 172.237.150.251
26 2026-08-25 08:55 639232440814614938
535 ms 172.237.150.251
25 2026-08-25 08:38 639232430410720425
542 ms 172.237.150.251
24 2026-08-25 08:21 639232420003096185
528 ms 172.237.150.251
23 2026-08-25 08:03 639232409467287444
549 ms 172.237.150.251
22 2026-08-25 07:46 639232399077195997
554 ms 172.237.150.251
21 2026-08-25 07:28 639232388731528337
528 ms 172.237.150.251
20 2026-08-25 07:11 639232378288598612
551 ms 172.237.150.251
19 2026-08-25 06:17 639232346196373643
538 ms 172.237.150.251
18 2026-08-25 06:00 639232336112370741
522 ms 172.237.150.251
17 2026-08-25 05:44 639232326146508970
522 ms 172.237.150.251
16 2026-08-25 05:27 639232316189381720
555 ms 172.237.150.251
15 2026-08-25 05:11 639232306217998913
539 ms 172.237.150.251
14 2026-08-25 04:54 639232296255744174
546 ms 172.237.150.251
13 2026-08-25 04:37 639232286095760789
545 ms 172.237.150.251
12 2026-08-25 04:20 639232276086186273
535 ms 172.237.150.251
11 2026-08-25 04:03 639232265900986425
543 ms 172.237.150.251
10 2026-08-25 03:47 639232255723518075
539 ms 172.237.150.251
9 2026-08-25 03:29 639232245484452890
530 ms 172.237.150.251
8 2026-08-25 03:12 639232235157175331
549 ms 172.237.150.251
7 2026-08-25 02:19 639232203197189095
527 ms 172.237.150.251
6 2026-08-25 02:02 639232192844564298
535 ms 172.237.150.251
5 2026-08-25 01:45 639232182496008942
528 ms 172.237.150.251
4 2026-08-25 01:27 639232172197053132
539 ms 172.237.150.251
3 2026-08-25 00:34 639232140250307418
539 ms 172.237.150.251
2 2026-08-25 00:17 639232129927860324
536 ms 172.237.150.251
1 2026-08-25 00:00 639232119551972438
1634 ms 172.237.150.251