DNS response history for ns2.adecor.tokyo

ns2.adecor.tokyo 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 24 DNS check records, 24 successful responses, 0 failed responses, and 537 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 ns2.adecor.tokyo.
Records on Selected Date

24

Historical checks stored for this nameserver on selected date

Average Latency

537 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 10:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

153.126.131.247

Most recently resolved hosting IP on selected date

Successful Responses

24

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 ns2.adecor.tokyo

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
24 2026-08-24 10:09 639231621644955316
583 ms 153.126.131.247
23 2026-08-24 09:52 639231611478799259
591 ms 153.126.131.247
22 2026-08-24 08:59 639231579923718211
2275 ms 153.126.131.247
21 2026-08-24 08:43 639231569810702936
380 ms 153.126.131.247
20 2026-08-24 08:26 639231559762411619
586 ms 153.126.131.247
19 2026-08-24 08:09 639231549663595407
274 ms 153.126.131.247
18 2026-08-24 07:16 639231518076817246
293 ms 153.126.131.247
17 2026-08-24 07:00 639231508078650885
583 ms 153.126.131.247
16 2026-08-24 06:43 639231498210697093
296 ms 153.126.131.247
15 2026-08-24 06:26 639231488109699360
308 ms 153.126.131.247
14 2026-08-24 05:34 639231456772510692
384 ms 153.126.131.247
13 2026-08-24 05:18 639231447084631185
297 ms 153.126.131.247
12 2026-08-24 05:01 639231437208519473
294 ms 153.126.131.247
11 2026-08-24 04:45 639231427209627490
577 ms 153.126.131.247
10 2026-08-24 03:52 639231395791246644
3 ms 153.126.131.247
9 2026-08-24 03:36 639231386075551458
274 ms 153.126.131.247
8 2026-08-24 03:20 639231376208713791
563 ms 153.126.131.247
7 2026-08-24 03:03 639231366170589276
2296 ms 153.126.131.247
6 2026-08-24 02:11 639231334732159368
2 ms 153.126.131.247
5 2026-08-24 01:54 639231325035670078
582 ms 153.126.131.247
4 2026-08-24 01:38 639231315132253837
299 ms 153.126.131.247
3 2026-08-24 01:21 639231305014280808
574 ms 153.126.131.247
2 2026-08-24 00:29 639231273779380675
571 ms 153.126.131.247
1 2026-08-24 00:13 639231264180839154
3 ms 153.126.131.247