DNS response history for ns1.seimy.tokyo

ns1.seimy.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 27 DNS check records, 27 successful responses, 0 failed responses, and 270 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.seimy.tokyo.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

270 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 11:35

All timestamps shown in UTC

Latest Resolved IP on Selected Date

180.222.187.126

Most recently resolved hosting IP on selected date

Successful Responses

27

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.seimy.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
27 2026-08-24 11:35 639231673513573868
255 ms 180.222.187.126
26 2026-08-24 10:41 639231641791249939
244 ms 180.222.187.126
25 2026-08-24 10:25 639231631866211033
2 ms 180.222.187.126
24 2026-08-24 10:08 639231621644955316
282 ms 180.222.187.126
23 2026-08-24 09:51 639231611478799259
543 ms 180.222.187.126
22 2026-08-24 08:59 639231579923718211
545 ms 180.222.187.126
21 2026-08-24 08:42 639231569810702936
561 ms 180.222.187.126
20 2026-08-24 08:25 639231559762411619
302 ms 180.222.187.126
19 2026-08-24 08:08 639231549663595407
257 ms 180.222.187.126
18 2026-08-24 07:15 639231518076817246
93 ms 180.222.187.126
17 2026-08-24 06:59 639231508078650885
243 ms 180.222.187.126
16 2026-08-24 06:42 639231498210697093
3 ms 180.222.187.126
15 2026-08-24 06:26 639231488109699360
3 ms 180.222.187.126
14 2026-08-24 05:33 639231456772510692
385 ms 180.222.187.126
13 2026-08-24 05:17 639231447084631185
2 ms 180.222.187.126
12 2026-08-24 05:00 639231437208519473
525 ms 180.222.187.126
11 2026-08-24 04:44 639231427209627490
558 ms 180.222.187.126
10 2026-08-24 03:51 639231395791246644
3 ms 180.222.187.126
9 2026-08-24 03:35 639231386075551458
9 ms 180.222.187.126
8 2026-08-24 03:19 639231376208713791
536 ms 180.222.187.126
7 2026-08-24 03:02 639231366170589276
553 ms 180.222.187.126
6 2026-08-24 02:10 639231334732159368
261 ms 180.222.187.126
5 2026-08-24 01:53 639231325035670078
558 ms 180.222.187.126
4 2026-08-24 01:37 639231315132253837
6 ms 180.222.187.126
3 2026-08-24 01:20 639231305014280808
562 ms 180.222.187.126
2 2026-08-24 00:28 639231273779380675
2 ms 180.222.187.126
1 2026-08-24 00:12 639231264180839154
2 ms 180.222.187.126