DNS response history for ns4.ebara.tokyo

ns4.ebara.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 34 DNS check records, 34 successful responses, 0 failed responses, and 338 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 ns4.ebara.tokyo.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

338 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

221.246.229.86

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 ns4.ebara.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
34 2026-08-24 14:10 639231765923559455
6 ms 221.246.229.86
33 2026-08-24 13:54 639231755868832964
474 ms 221.246.229.86
32 2026-08-24 13:37 639231745628278877
238 ms 221.246.229.86
31 2026-08-24 13:19 639231735407682062
4 ms 221.246.229.86
30 2026-08-24 12:27 639231703815441688
240 ms 221.246.229.86
29 2026-08-24 12:10 639231693747052549
238 ms 221.246.229.86
28 2026-08-24 11:53 639231683712487276
245 ms 221.246.229.86
27 2026-08-24 11:36 639231673513573868
1066 ms 221.246.229.86
26 2026-08-24 10:43 639231641791249939
242 ms 221.246.229.86
25 2026-08-24 10:27 639231631866211033
240 ms 221.246.229.86
24 2026-08-24 10:10 639231621644955316
1072 ms 221.246.229.86
23 2026-08-24 09:53 639231611478799259
1080 ms 221.246.229.86
22 2026-08-24 09:00 639231579923718211
6 ms 221.246.229.86
21 2026-08-24 08:44 639231569810702936
255 ms 221.246.229.86
20 2026-08-24 08:27 639231559762411619
1068 ms 221.246.229.86
19 2026-08-24 08:10 639231549663595407
241 ms 221.246.229.86
18 2026-08-24 07:17 639231518076817246
6 ms 221.246.229.86
17 2026-08-24 07:01 639231508078650885
15 ms 221.246.229.86
16 2026-08-24 06:44 639231498210697093
252 ms 221.246.229.86
15 2026-08-24 06:27 639231488109699360
236 ms 221.246.229.86
14 2026-08-24 05:35 639231456772510692
491 ms 221.246.229.86
13 2026-08-24 05:19 639231447084631185
470 ms 221.246.229.86
12 2026-08-24 05:02 639231437208519473
245 ms 221.246.229.86
11 2026-08-24 04:46 639231427209627490
3 ms 221.246.229.86
10 2026-08-24 03:53 639231395791246644
474 ms 221.246.229.86
9 2026-08-24 03:37 639231386075551458
550 ms 221.246.229.86
8 2026-08-24 03:21 639231376208713791
2 ms 221.246.229.86
7 2026-08-24 03:04 639231366170589276
1058 ms 221.246.229.86
6 2026-08-24 02:12 639231334732159368
3 ms 221.246.229.86
5 2026-08-24 01:55 639231325035670078
3 ms 221.246.229.86
4 2026-08-24 01:39 639231315132253837
476 ms 221.246.229.86
3 2026-08-24 01:22 639231305014280808
248 ms 221.246.229.86
2 2026-08-24 00:30 639231273779380675
3 ms 221.246.229.86
1 2026-08-24 00:14 639231264180839154
238 ms 221.246.229.86