DNS response history for ns.cct-s.jp

ns.cct-s.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 30 DNS check records, 30 successful responses, 0 failed responses, and 335 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.cct-s.jp.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

335 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

153.122.10.61

Most recently resolved hosting IP on selected date

Successful Responses

30

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.cct-s.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
30 2026-08-24 12:26 639231703815441688
545 ms 153.122.10.61
29 2026-08-24 12:10 639231693747052549
572 ms 153.122.10.61
28 2026-08-24 11:53 639231683712487276
798 ms 153.122.10.61
27 2026-08-24 11:36 639231673513573868
547 ms 153.122.10.61
26 2026-08-24 10:43 639231641791249939
563 ms 153.122.10.61
25 2026-08-24 10:26 639231631866211033
586 ms 153.122.10.61
24 2026-08-24 10:10 639231621644955316
539 ms 153.122.10.61
23 2026-08-24 09:52 639231611478799259
6 ms 153.122.10.61
22 2026-08-24 09:00 639231579923718211
3 ms 153.122.10.61
21 2026-08-24 08:43 639231569810702936
549 ms 153.122.10.61
20 2026-08-24 08:26 639231559762411619
589 ms 153.122.10.61
19 2026-08-24 08:09 639231549663595407
539 ms 153.122.10.61
18 2026-08-24 07:16 639231518076817246
534 ms 153.122.10.61
17 2026-08-24 07:00 639231508078650885
548 ms 153.122.10.61
16 2026-08-24 06:43 639231498210697093
4 ms 153.122.10.61
15 2026-08-24 06:27 639231488109699360
564 ms 153.122.10.61
14 2026-08-24 05:34 639231456772510692
4 ms 153.122.10.61
13 2026-08-24 05:18 639231447084631185
3 ms 153.122.10.61
12 2026-08-24 05:02 639231437208519473
9 ms 153.122.10.61
11 2026-08-24 04:45 639231427209627490
561 ms 153.122.10.61
10 2026-08-24 03:52 639231395791246644
12 ms 153.122.10.61
9 2026-08-24 03:37 639231386075551458
26 ms 153.122.10.61
8 2026-08-24 03:20 639231376208713791
528 ms 153.122.10.61
7 2026-08-24 03:04 639231366170589276
786 ms 153.122.10.61
6 2026-08-24 02:11 639231334732159368
25 ms 153.122.10.61
5 2026-08-24 01:55 639231325035670078
9 ms 153.122.10.61
4 2026-08-24 01:38 639231315132253837
549 ms 153.122.10.61
3 2026-08-24 01:22 639231305014280808
3 ms 153.122.10.61
2 2026-08-24 00:29 639231273779380675
35 ms 153.122.10.61
1 2026-08-24 00:13 639231264180839154
9 ms 153.122.10.61