DNS response history for ns1.ncikk.co.jp

ns1.ncikk.co.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 34 DNS check records, 34 successful responses, 0 failed responses, and 480 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.ncikk.co.jp.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

480 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

219.122.38.170

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 ns1.ncikk.co.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
34 2026-08-24 14:10 639231765923559455
561 ms 219.122.38.170
33 2026-08-24 13:53 639231755868832964
1488 ms 219.122.38.170
32 2026-08-24 13:36 639231745628278877
844 ms 219.122.38.170
31 2026-08-24 13:19 639231735407682062
565 ms 219.122.38.170
30 2026-08-24 12:26 639231703815441688
4 ms 219.122.38.170
29 2026-08-24 12:10 639231693747052549
567 ms 219.122.38.170
28 2026-08-24 11:53 639231683712487276
4 ms 219.122.38.170
27 2026-08-24 11:36 639231673513573868
567 ms 219.122.38.170
26 2026-08-24 10:43 639231641791249939
4 ms 219.122.38.170
25 2026-08-24 10:27 639231631866211033
545 ms 219.122.38.170
24 2026-08-24 10:10 639231621644955316
544 ms 219.122.38.170
23 2026-08-24 09:53 639231611478799259
561 ms 219.122.38.170
22 2026-08-24 09:00 639231579923718211
574 ms 219.122.38.170
21 2026-08-24 08:43 639231569810702936
625 ms 219.122.38.170
20 2026-08-24 08:26 639231559762411619
589 ms 219.122.38.170
19 2026-08-24 08:10 639231549663595407
4 ms 219.122.38.170
18 2026-08-24 07:17 639231518076817246
584 ms 219.122.38.170
17 2026-08-24 07:00 639231508078650885
565 ms 219.122.38.170
16 2026-08-24 06:44 639231498210697093
557 ms 219.122.38.170
15 2026-08-24 06:27 639231488109699360
21 ms 219.122.38.170
14 2026-08-24 05:35 639231456772510692
534 ms 219.122.38.170
13 2026-08-24 05:18 639231447084631185
561 ms 219.122.38.170
12 2026-08-24 05:02 639231437208519473
577 ms 219.122.38.170
11 2026-08-24 04:45 639231427209627490
597 ms 219.122.38.170
10 2026-08-24 03:53 639231395791246644
333 ms 219.122.38.170
9 2026-08-24 03:37 639231386075551458
550 ms 219.122.38.170
8 2026-08-24 03:20 639231376208713791
553 ms 219.122.38.170
7 2026-08-24 03:04 639231366170589276
556 ms 219.122.38.170
6 2026-08-24 02:11 639231334732159368
2 ms 219.122.38.170
5 2026-08-24 01:55 639231325035670078
3 ms 219.122.38.170
4 2026-08-24 01:39 639231315132253837
575 ms 219.122.38.170
3 2026-08-24 01:22 639231305014280808
555 ms 219.122.38.170
2 2026-08-24 00:29 639231273779380675
555 ms 219.122.38.170
1 2026-08-24 00:14 639231264180839154
579 ms 219.122.38.170