DNS response history for ns.c-three.jp

ns.c-three.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 29 DNS check records, 29 successful responses, 0 failed responses, and 1009 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.c-three.jp.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

1009 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

59.106.59.233

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.c-three.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
29 2026-08-24 12:11 639231693747052549
1095 ms 59.106.59.233
28 2026-08-24 11:54 639231683712487276
1120 ms 59.106.59.233
27 2026-08-24 11:37 639231673513573868
1092 ms 59.106.59.233
26 2026-08-24 10:44 639231641791249939
1094 ms 59.106.59.233
25 2026-08-24 10:28 639231631866211033
1107 ms 59.106.59.233
24 2026-08-24 10:11 639231621644955316
851 ms 59.106.59.233
23 2026-08-24 09:54 639231611478799259
1088 ms 59.106.59.233
22 2026-08-24 09:01 639231579923718211
1110 ms 59.106.59.233
21 2026-08-24 08:45 639231569810702936
1135 ms 59.106.59.233
20 2026-08-24 08:28 639231559762411619
1089 ms 59.106.59.233
19 2026-08-24 08:11 639231549663595407
1094 ms 59.106.59.233
18 2026-08-24 07:18 639231518076817246
1100 ms 59.106.59.233
17 2026-08-24 07:02 639231508078650885
1096 ms 59.106.59.233
16 2026-08-24 06:45 639231498210697093
1092 ms 59.106.59.233
15 2026-08-24 06:28 639231488109699360
1091 ms 59.106.59.233
14 2026-08-24 05:36 639231456772510692
1062 ms 59.106.59.233
13 2026-08-24 05:19 639231447084631185
1089 ms 59.106.59.233
12 2026-08-24 05:03 639231437208519473
247 ms 59.106.59.233
11 2026-08-24 04:47 639231427209627490
1068 ms 59.106.59.233
10 2026-08-24 03:54 639231395791246644
1097 ms 59.106.59.233
9 2026-08-24 03:38 639231386075551458
1082 ms 59.106.59.233
8 2026-08-24 03:22 639231376208713791
1112 ms 59.106.59.233
7 2026-08-24 03:05 639231366170589276
1111 ms 59.106.59.233
6 2026-08-24 02:12 639231334732159368
1093 ms 59.106.59.233
5 2026-08-24 01:56 639231325035670078
485 ms 59.106.59.233
4 2026-08-24 01:40 639231315132253837
1082 ms 59.106.59.233
3 2026-08-24 01:23 639231305014280808
1114 ms 59.106.59.233
2 2026-08-24 00:30 639231273779380675
1096 ms 59.106.59.233
1 2026-08-24 00:15 639231264180839154
283 ms 59.106.59.233