DNS response history for dayan.gna.ne.jp

dayan.gna.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 30 DNS check records, 30 successful responses, 0 failed responses, and 370 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 dayan.gna.ne.jp.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

370 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

61.114.232.131

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 dayan.gna.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
30 2026-08-24 12:26 639231703815441688
532 ms 61.114.232.131
29 2026-08-24 12:09 639231693747052549
5 ms 61.114.232.131
28 2026-08-24 11:53 639231683712487276
546 ms 61.114.232.131
27 2026-08-24 11:36 639231673513573868
759 ms 61.114.232.131
26 2026-08-24 10:42 639231641791249939
313 ms 61.114.232.131
25 2026-08-24 10:26 639231631866211033
252 ms 61.114.232.131
24 2026-08-24 10:09 639231621644955316
258 ms 61.114.232.131
23 2026-08-24 09:52 639231611478799259
525 ms 61.114.232.131
22 2026-08-24 09:00 639231579923718211
3 ms 61.114.232.131
21 2026-08-24 08:43 639231569810702936
511 ms 61.114.232.131
20 2026-08-24 08:26 639231559762411619
505 ms 61.114.232.131
19 2026-08-24 08:09 639231549663595407
510 ms 61.114.232.131
18 2026-08-24 07:16 639231518076817246
241 ms 61.114.232.131
17 2026-08-24 07:00 639231508078650885
319 ms 61.114.232.131
16 2026-08-24 06:43 639231498210697093
500 ms 61.114.232.131
15 2026-08-24 06:27 639231488109699360
509 ms 61.114.232.131
14 2026-08-24 05:34 639231456772510692
3 ms 61.114.232.131
13 2026-08-24 05:18 639231447084631185
3 ms 61.114.232.131
12 2026-08-24 05:02 639231437208519473
495 ms 61.114.232.131
11 2026-08-24 04:45 639231427209627490
508 ms 61.114.232.131
10 2026-08-24 03:52 639231395791246644
490 ms 61.114.232.131
9 2026-08-24 03:36 639231386075551458
2 ms 61.114.232.131
8 2026-08-24 03:20 639231376208713791
501 ms 61.114.232.131
7 2026-08-24 03:03 639231366170589276
531 ms 61.114.232.131
6 2026-08-24 02:11 639231334732159368
515 ms 61.114.232.131
5 2026-08-24 01:55 639231325035670078
2 ms 61.114.232.131
4 2026-08-24 01:38 639231315132253837
495 ms 61.114.232.131
3 2026-08-24 01:22 639231305014280808
497 ms 61.114.232.131
2 2026-08-24 00:29 639231273779380675
257 ms 61.114.232.131
1 2026-08-24 00:13 639231264180839154
499 ms 61.114.232.131