DNS response history for ns1.desperatelyreply.tokyo

ns1.desperatelyreply.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-25. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 577 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.desperatelyreply.tokyo.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

577 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.40.98.67

Most recently resolved hosting IP on selected date

Successful Responses

29

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.desperatelyreply.tokyo

Showing DNS history for 2026-08-25 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
29 2026-08-25 09:47 639232471861770303
964 ms 103.40.98.67
28 2026-08-25 09:30 639232461630217327
490 ms 103.40.98.67
27 2026-08-25 09:13 639232451282965990
524 ms 103.40.98.67
26 2026-08-25 08:55 639232440814614938
253 ms 103.40.98.67
25 2026-08-25 08:38 639232430410720425
263 ms 103.40.98.67
24 2026-08-25 08:21 639232420003096185
516 ms 103.40.98.67
23 2026-08-25 08:03 639232409467287444
248 ms 103.40.98.67
22 2026-08-25 07:46 639232399077195997
269 ms 103.40.98.67
21 2026-08-25 07:28 639232388731528337
526 ms 103.40.98.67
20 2026-08-25 07:11 639232378288598612
961 ms 103.40.98.67
19 2026-08-25 06:17 639232346196373643
503 ms 103.40.98.67
18 2026-08-25 06:00 639232336112370741
403 ms 103.40.98.67
17 2026-08-25 05:44 639232326146508970
263 ms 103.40.98.67
16 2026-08-25 05:27 639232316189381720
262 ms 103.40.98.67
15 2026-08-25 05:11 639232306217998913
263 ms 103.40.98.67
14 2026-08-25 04:54 639232296255744174
963 ms 103.40.98.67
13 2026-08-25 04:37 639232286095760789
247 ms 103.40.98.67
12 2026-08-25 04:20 639232276086186273
955 ms 103.40.98.67
11 2026-08-25 04:04 639232265900986425
259 ms 103.40.98.67
10 2026-08-25 03:47 639232255723518075
511 ms 103.40.98.67
9 2026-08-25 03:30 639232245484452890
519 ms 103.40.98.67
8 2026-08-25 03:12 639232235157175331
953 ms 103.40.98.67
7 2026-08-25 02:19 639232203197189095
1278 ms 103.40.98.67
6 2026-08-25 02:02 639232192844564298
265 ms 103.40.98.67
5 2026-08-25 01:45 639232182496008942
762 ms 103.40.98.67
4 2026-08-25 01:27 639232172197053132
1631 ms 103.40.98.67
3 2026-08-25 00:34 639232140250307418
533 ms 103.40.98.67
2 2026-08-25 00:17 639232129927860324
528 ms 103.40.98.67
1 2026-08-25 00:00 639232119551972438
627 ms 103.40.98.67