DNS response history for ns03.e-nyusatsu-tok.jp

ns03.e-nyusatsu-tok.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 589 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 ns03.e-nyusatsu-tok.jp.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

589 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

202.248.5.5

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 ns03.e-nyusatsu-tok.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
559 ms 202.248.5.5
33 2026-08-24 13:53 639231755868832964
812 ms 202.248.5.5
32 2026-08-24 13:36 639231745628278877
1049 ms 202.248.5.5
31 2026-08-24 13:19 639231735407682062
659 ms 202.248.5.5
30 2026-08-24 12:26 639231703815441688
514 ms 202.248.5.5
29 2026-08-24 12:10 639231693747052549
495 ms 202.248.5.5
28 2026-08-24 11:53 639231683712487276
522 ms 202.248.5.5
27 2026-08-24 11:36 639231673513573868
531 ms 202.248.5.5
26 2026-08-24 10:43 639231641791249939
515 ms 202.248.5.5
25 2026-08-24 10:27 639231631866211033
507 ms 202.248.5.5
24 2026-08-24 10:10 639231621644955316
568 ms 202.248.5.5
23 2026-08-24 09:53 639231611478799259
519 ms 202.248.5.5
22 2026-08-24 09:00 639231579923718211
498 ms 202.248.5.5
21 2026-08-24 08:43 639231569810702936
507 ms 202.248.5.5
20 2026-08-24 08:26 639231559762411619
526 ms 202.248.5.5
19 2026-08-24 08:10 639231549663595407
520 ms 202.248.5.5
18 2026-08-24 07:17 639231518076817246
508 ms 202.248.5.5
17 2026-08-24 07:00 639231508078650885
513 ms 202.248.5.5
16 2026-08-24 06:44 639231498210697093
510 ms 202.248.5.5
15 2026-08-24 06:27 639231488109699360
515 ms 202.248.5.5
14 2026-08-24 05:35 639231456772510692
514 ms 202.248.5.5
13 2026-08-24 05:18 639231447084631185
575 ms 202.248.5.5
12 2026-08-24 05:02 639231437208519473
503 ms 202.248.5.5
11 2026-08-24 04:45 639231427209627490
511 ms 202.248.5.5
10 2026-08-24 03:53 639231395791246644
489 ms 202.248.5.5
9 2026-08-24 03:37 639231386075551458
511 ms 202.248.5.5
8 2026-08-24 03:20 639231376208713791
515 ms 202.248.5.5
7 2026-08-24 03:04 639231366170589276
505 ms 202.248.5.5
6 2026-08-24 02:11 639231334732159368
548 ms 202.248.5.5
5 2026-08-24 01:55 639231325035670078
495 ms 202.248.5.5
4 2026-08-24 01:39 639231315132253837
503 ms 202.248.5.5
3 2026-08-24 01:22 639231305014280808
2271 ms 202.248.5.5
2 2026-08-24 00:29 639231273779380675
246 ms 202.248.5.5
1 2026-08-24 00:14 639231264180839154
489 ms 202.248.5.5