DNS response history for ns.p-com.ne.jp

ns.p-com.ne.jp 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 29 DNS check records, 29 successful responses, 0 failed responses, and 784 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 ns.p-com.ne.jp.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

784 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:48

All timestamps shown in UTC

Latest Resolved IP on Selected Date

101.97.22.7

Most recently resolved hosting IP on selected date

Successful Responses

29

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 ns.p-com.ne.jp

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
29 2026-08-25 09:48 639232471861770303
1082 ms 101.97.22.7
28 2026-08-25 09:31 639232461630217327
1048 ms 101.97.22.7
27 2026-08-25 09:13 639232451282965990
542 ms 101.97.22.7
26 2026-08-25 08:56 639232440814614938
540 ms 101.97.22.7
25 2026-08-25 08:39 639232430410720425
765 ms 101.97.22.7
24 2026-08-25 08:21 639232420003096185
1020 ms 101.97.22.7
23 2026-08-25 08:04 639232409467287444
536 ms 101.97.22.7
22 2026-08-25 07:47 639232399077195997
1075 ms 101.97.22.7
21 2026-08-25 07:29 639232388731528337
541 ms 101.97.22.7
20 2026-08-25 07:12 639232378288598612
1024 ms 101.97.22.7
19 2026-08-25 06:18 639232346196373643
799 ms 101.97.22.7
18 2026-08-25 06:01 639232336112370741
831 ms 101.97.22.7
17 2026-08-25 05:44 639232326146508970
570 ms 101.97.22.7
16 2026-08-25 05:28 639232316189381720
690 ms 101.97.22.7
15 2026-08-25 05:11 639232306217998913
424 ms 101.97.22.7
14 2026-08-25 04:55 639232296255744174
760 ms 101.97.22.7
13 2026-08-25 04:38 639232286095760789
708 ms 101.97.22.7
12 2026-08-25 04:21 639232276086186273
790 ms 101.97.22.7
11 2026-08-25 04:04 639232265900986425
507 ms 101.97.22.7
10 2026-08-25 03:47 639232255723518075
503 ms 101.97.22.7
9 2026-08-25 03:30 639232245484452890
1135 ms 101.97.22.7
8 2026-08-25 03:13 639232235157175331
1301 ms 101.97.22.7
7 2026-08-25 02:20 639232203197189095
1062 ms 101.97.22.7
6 2026-08-25 02:03 639232192844564298
1094 ms 101.97.22.7
5 2026-08-25 01:45 639232182496008942
530 ms 101.97.22.7
4 2026-08-25 01:28 639232172197053132
953 ms 101.97.22.7
3 2026-08-25 00:35 639232140250307418
524 ms 101.97.22.7
2 2026-08-25 00:18 639232129927860324
793 ms 101.97.22.7
1 2026-08-25 00:01 639232119551972438
586 ms 101.97.22.7