DNS response history for ns1.tokyoehs.com

ns1.tokyoehs.com 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 248 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.tokyoehs.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

248 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

153.75.233.8

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 ns1.tokyoehs.com

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:20 639231703815441688
109 ms 153.75.233.8
29 2026-08-24 12:03 639231693747052549
10 ms 153.75.233.8
28 2026-08-24 11:46 639231683712487276
201 ms 153.75.233.8
27 2026-08-24 11:29 639231673513573868
126 ms 153.75.233.8
26 2026-08-24 10:37 639231641791249939
116 ms 153.75.233.8
25 2026-08-24 10:20 639231631866211033
121 ms 153.75.233.8
24 2026-08-24 10:03 639231621644955316
105 ms 153.75.233.8
23 2026-08-24 09:46 639231611478799259
119 ms 153.75.233.8
22 2026-08-24 08:54 639231579923718211
128 ms 153.75.233.8
21 2026-08-24 08:37 639231569810702936
198 ms 153.75.233.8
20 2026-08-24 08:20 639231559762411619
194 ms 153.75.233.8
19 2026-08-24 08:03 639231549663595407
16 ms 153.75.233.8
18 2026-08-24 07:11 639231518076817246
187 ms 153.75.233.8
17 2026-08-24 06:54 639231508078650885
208 ms 153.75.233.8
16 2026-08-24 06:37 639231498210697093
12 ms 153.75.233.8
15 2026-08-24 06:21 639231488109699360
95 ms 153.75.233.8
14 2026-08-24 05:28 639231456772510692
11 ms 153.75.233.8
13 2026-08-24 05:12 639231447084631185
151 ms 153.75.233.8
12 2026-08-24 04:56 639231437208519473
31 ms 153.75.233.8
11 2026-08-24 04:39 639231427209627490
34 ms 153.75.233.8
10 2026-08-24 03:47 639231395791246644
17 ms 153.75.233.8
9 2026-08-24 03:31 639231386075551458
26 ms 153.75.233.8
8 2026-08-24 03:14 639231376208713791
9 ms 153.75.233.8
7 2026-08-24 02:57 639231366170589276
229 ms 153.75.233.8
6 2026-08-24 02:05 639231334732159368
189 ms 153.75.233.8
5 2026-08-24 01:49 639231325035670078
198 ms 153.75.233.8
4 2026-08-24 01:32 639231315132253837
2032 ms 153.75.233.8
3 2026-08-24 01:15 639231305014280808
2236 ms 153.75.233.8
2 2026-08-24 00:23 639231273779380675
216 ms 153.75.233.8
1 2026-08-24 00:07 639231264180839154
113 ms 153.75.233.8