DNS response history for ns5.scanet.tokyo

ns5.scanet.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-27. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 540 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 ns5.scanet.tokyo.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

540 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

153.120.2.251

Most recently resolved hosting IP on selected date

Successful Responses

35

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 ns5.scanet.tokyo

Showing DNS history for 2026-08-27 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
35 2026-08-27 11:17 639234253963286387
547 ms 153.120.2.251
34 2026-08-27 11:00 639234243654907465
562 ms 153.120.2.251
33 2026-08-27 10:43 639234233269654413
551 ms 153.120.2.251
32 2026-08-27 10:25 639234222943951923
546 ms 153.120.2.251
31 2026-08-27 10:08 639234212558002823
548 ms 153.120.2.251
30 2026-08-27 09:51 639234202117531850
553 ms 153.120.2.251
29 2026-08-27 09:34 639234191649612722
552 ms 153.120.2.251
28 2026-08-27 09:16 639234181105879568
538 ms 153.120.2.251
27 2026-08-27 08:58 639234170713214496
547 ms 153.120.2.251
26 2026-08-27 08:41 639234160341037652
528 ms 153.120.2.251
25 2026-08-27 08:24 639234149799404224
557 ms 153.120.2.251
24 2026-08-27 08:06 639234139553286469
547 ms 153.120.2.251
23 2026-08-27 07:13 639234107183588293
539 ms 153.120.2.251
22 2026-08-27 06:55 639234096905435724
518 ms 153.120.2.251
21 2026-08-27 06:38 639234086579410775
544 ms 153.120.2.251
20 2026-08-27 06:21 639234076291157956
531 ms 153.120.2.251
19 2026-08-27 06:04 639234065981939454
530 ms 153.120.2.251
18 2026-08-27 05:47 639234055548642997
541 ms 153.120.2.251
17 2026-08-27 05:29 639234045267979603
523 ms 153.120.2.251
16 2026-08-27 05:12 639234034999717463
537 ms 153.120.2.251
15 2026-08-27 04:55 639234024739225358
533 ms 153.120.2.251
14 2026-08-27 04:38 639234014311170162
524 ms 153.120.2.251
13 2026-08-27 04:20 639234003806017640
573 ms 153.120.2.251
12 2026-08-27 04:03 639233993356203030
535 ms 153.120.2.251
11 2026-08-27 03:10 639233961301716608
515 ms 153.120.2.251
10 2026-08-27 02:52 639233950834200647
531 ms 153.120.2.251
9 2026-08-27 02:35 639233940431849026
550 ms 153.120.2.251
8 2026-08-27 02:18 639233930110596398
516 ms 153.120.2.251
7 2026-08-27 02:00 639233919705434540
546 ms 153.120.2.251
6 2026-08-27 01:43 639233909452807845
518 ms 153.120.2.251
5 2026-08-27 01:26 639233899096420820
564 ms 153.120.2.251
4 2026-08-27 01:09 639233888707824939
538 ms 153.120.2.251
3 2026-08-27 00:51 639233878461203802
552 ms 153.120.2.251
2 2026-08-27 00:34 639233868060868209
554 ms 153.120.2.251
1 2026-08-27 00:17 639233857450922991
524 ms 153.120.2.251