DNS response history for ns.eagle-net.ne.jp

ns.eagle-net.ne.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 26 DNS check records, 26 successful responses, 0 failed responses, and 459 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.eagle-net.ne.jp.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

459 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 10:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

61.120.101.1

Most recently resolved hosting IP on selected date

Successful Responses

26

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.eagle-net.ne.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
26 2026-08-24 10:43 639231641791249939
580 ms 61.120.101.1
25 2026-08-24 10:27 639231631866211033
359 ms 61.120.101.1
24 2026-08-24 10:10 639231621644955316
3 ms 61.120.101.1
23 2026-08-24 09:53 639231611478799259
577 ms 61.120.101.1
22 2026-08-24 09:00 639231579923718211
4 ms 61.120.101.1
21 2026-08-24 08:44 639231569810702936
570 ms 61.120.101.1
20 2026-08-24 08:26 639231559762411619
3 ms 61.120.101.1
19 2026-08-24 08:10 639231549663595407
594 ms 61.120.101.1
18 2026-08-24 07:17 639231518076817246
591 ms 61.120.101.1
17 2026-08-24 07:01 639231508078650885
5 ms 61.120.101.1
16 2026-08-24 06:44 639231498210697093
576 ms 61.120.101.1
15 2026-08-24 06:27 639231488109699360
577 ms 61.120.101.1
14 2026-08-24 05:35 639231456772510692
3 ms 61.120.101.1
13 2026-08-24 05:18 639231447084631185
4 ms 61.120.101.1
12 2026-08-24 05:02 639231437208519473
676 ms 61.120.101.1
11 2026-08-24 04:46 639231427209627490
586 ms 61.120.101.1
10 2026-08-24 03:53 639231395791246644
431 ms 61.120.101.1
9 2026-08-24 03:37 639231386075551458
556 ms 61.120.101.1
8 2026-08-24 03:21 639231376208713791
1784 ms 61.120.101.1
7 2026-08-24 03:04 639231366170589276
605 ms 61.120.101.1
6 2026-08-24 02:12 639231334732159368
574 ms 61.120.101.1
5 2026-08-24 01:55 639231325035670078
585 ms 61.120.101.1
4 2026-08-24 01:39 639231315132253837
280 ms 61.120.101.1
3 2026-08-24 01:22 639231305014280808
580 ms 61.120.101.1
2 2026-08-24 00:30 639231273779380675
289 ms 61.120.101.1
1 2026-08-24 00:14 639231264180839154
531 ms 61.120.101.1