DNS response history for ns1.neody.ad.jp

ns1.neody.ad.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 34 DNS check records, 34 successful responses, 0 failed responses, and 446 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 ns1.neody.ad.jp.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

446 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

43.229.16.132

Most recently resolved hosting IP on selected date

Successful Responses

34

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 ns1.neody.ad.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
34 2026-08-24 14:10 639231765923559455
526 ms 43.229.16.132
33 2026-08-24 13:54 639231755868832964
6 ms 43.229.16.132
32 2026-08-24 13:37 639231745628278877
1199 ms 43.229.16.132
31 2026-08-24 13:19 639231735407682062
937 ms 43.229.16.132
30 2026-08-24 12:27 639231703815441688
542 ms 43.229.16.132
29 2026-08-24 12:10 639231693747052549
739 ms 43.229.16.132
28 2026-08-24 11:53 639231683712487276
557 ms 43.229.16.132
27 2026-08-24 11:36 639231673513573868
541 ms 43.229.16.132
26 2026-08-24 10:43 639231641791249939
923 ms 43.229.16.132
25 2026-08-24 10:27 639231631866211033
930 ms 43.229.16.132
24 2026-08-24 10:10 639231621644955316
669 ms 43.229.16.132
23 2026-08-24 09:53 639231611478799259
562 ms 43.229.16.132
22 2026-08-24 09:00 639231579923718211
514 ms 43.229.16.132
21 2026-08-24 08:44 639231569810702936
3 ms 43.229.16.132
20 2026-08-24 08:27 639231559762411619
4 ms 43.229.16.132
19 2026-08-24 08:10 639231549663595407
534 ms 43.229.16.132
18 2026-08-24 07:17 639231518076817246
4 ms 43.229.16.132
17 2026-08-24 07:01 639231508078650885
553 ms 43.229.16.132
16 2026-08-24 06:44 639231498210697093
560 ms 43.229.16.132
15 2026-08-24 06:27 639231488109699360
549 ms 43.229.16.132
14 2026-08-24 05:35 639231456772510692
2 ms 43.229.16.132
13 2026-08-24 05:19 639231447084631185
563 ms 43.229.16.132
12 2026-08-24 05:02 639231437208519473
506 ms 43.229.16.132
11 2026-08-24 04:46 639231427209627490
536 ms 43.229.16.132
10 2026-08-24 03:53 639231395791246644
2 ms 43.229.16.132
9 2026-08-24 03:37 639231386075551458
271 ms 43.229.16.132
8 2026-08-24 03:21 639231376208713791
263 ms 43.229.16.132
7 2026-08-24 03:04 639231366170589276
573 ms 43.229.16.132
6 2026-08-24 02:12 639231334732159368
263 ms 43.229.16.132
5 2026-08-24 01:55 639231325035670078
2 ms 43.229.16.132
4 2026-08-24 01:39 639231315132253837
2 ms 43.229.16.132
3 2026-08-24 01:22 639231305014280808
800 ms 43.229.16.132
2 2026-08-24 00:30 639231273779380675
4 ms 43.229.16.132
1 2026-08-24 00:14 639231264180839154
527 ms 43.229.16.132