DNS response history for ns1.cpi.ne.jp

ns1.cpi.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-24. For this date, NameServerHistory found 27 DNS check records, 27 successful responses, 0 failed responses, and 459 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 ns1.cpi.ne.jp.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

459 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 11:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.133.115.61

Most recently resolved hosting IP on selected date

Successful Responses

27

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 ns1.cpi.ne.jp

Showing DNS history for 2026-08-24 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
27 2026-08-24 11:36 639231673513573868
529 ms 202.133.115.61
26 2026-08-24 10:43 639231641791249939
543 ms 202.133.115.61
25 2026-08-24 10:26 639231631866211033
538 ms 202.133.115.61
24 2026-08-24 10:10 639231621644955316
1074 ms 202.133.115.61
23 2026-08-24 09:53 639231611478799259
541 ms 202.133.115.61
22 2026-08-24 09:00 639231579923718211
277 ms 202.133.115.61
21 2026-08-24 08:43 639231569810702936
682 ms 202.133.115.61
20 2026-08-24 08:26 639231559762411619
532 ms 202.133.115.61
19 2026-08-24 08:10 639231549663595407
279 ms 202.133.115.61
18 2026-08-24 07:17 639231518076817246
330 ms 202.133.115.61
17 2026-08-24 07:00 639231508078650885
301 ms 202.133.115.61
16 2026-08-24 06:44 639231498210697093
551 ms 202.133.115.61
15 2026-08-24 06:27 639231488109699360
573 ms 202.133.115.61
14 2026-08-24 05:35 639231456772510692
1147 ms 202.133.115.61
13 2026-08-24 05:18 639231447084631185
364 ms 202.133.115.61
12 2026-08-24 05:02 639231437208519473
283 ms 202.133.115.61
11 2026-08-24 04:45 639231427209627490
289 ms 202.133.115.61
10 2026-08-24 03:53 639231395791246644
443 ms 202.133.115.61
9 2026-08-24 03:37 639231386075551458
2 ms 202.133.115.61
8 2026-08-24 03:20 639231376208713791
555 ms 202.133.115.61
7 2026-08-24 03:04 639231366170589276
268 ms 202.133.115.61
6 2026-08-24 02:11 639231334732159368
291 ms 202.133.115.61
5 2026-08-24 01:55 639231325035670078
2 ms 202.133.115.61
4 2026-08-24 01:39 639231315132253837
566 ms 202.133.115.61
3 2026-08-24 01:22 639231305014280808
572 ms 202.133.115.61
2 2026-08-24 00:29 639231273779380675
324 ms 202.133.115.61
1 2026-08-24 00:13 639231264180839154
543 ms 202.133.115.61