DNS response history for ns1.derive-tokyo.com

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

29

Historical checks stored for this nameserver on selected date

Average Latency

181 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:54

All timestamps shown in UTC

Latest Resolved IP on Selected Date

91.134.131.80

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.derive-tokyo.com

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:54 639232482235303141
47 ms 91.134.131.80
28 2026-08-25 09:37 639232471861770303
21 ms 91.134.131.80
27 2026-08-25 09:20 639232461630217327
62 ms 91.134.131.80
26 2026-08-25 09:03 639232451282965990
51 ms 91.134.131.80
25 2026-08-25 08:45 639232440814614938
2033 ms 91.134.131.80
24 2026-08-25 08:28 639232430410720425
19 ms 91.134.131.80
23 2026-08-25 08:11 639232420003096185
65 ms 91.134.131.80
22 2026-08-25 07:53 639232409467287444
146 ms 91.134.131.80
21 2026-08-25 07:36 639232399077195997
23 ms 91.134.131.80
20 2026-08-25 07:18 639232388731528337
32 ms 91.134.131.80
19 2026-08-25 07:01 639232378288598612
115 ms 91.134.131.80
18 2026-08-25 06:08 639232346196373643
52 ms 91.134.131.80
17 2026-08-25 05:51 639232336112370741
31 ms 91.134.131.80
16 2026-08-25 05:34 639232326146508970
5 ms 91.134.131.80
15 2026-08-25 05:18 639232316189381720
5 ms 91.134.131.80
14 2026-08-25 05:01 639232306217998913
40 ms 91.134.131.80
13 2026-08-25 04:44 639232296255744174
26 ms 91.134.131.80
12 2026-08-25 04:27 639232286095760789
24 ms 91.134.131.80
11 2026-08-25 04:11 639232276086186273
79 ms 91.134.131.80
10 2026-08-25 03:54 639232265900986425
2055 ms 91.134.131.80
9 2026-08-25 03:37 639232255723518075
28 ms 91.134.131.80
8 2026-08-25 03:20 639232245484452890
43 ms 91.134.131.80
7 2026-08-25 03:02 639232235157175331
43 ms 91.134.131.80
6 2026-08-25 02:09 639232203197189095
8 ms 91.134.131.80
5 2026-08-25 01:52 639232192844564298
36 ms 91.134.131.80
4 2026-08-25 01:35 639232182496008942
72 ms 91.134.131.80
3 2026-08-25 01:17 639232172197053132
30 ms 91.134.131.80
2 2026-08-25 00:24 639232140250307418
28 ms 91.134.131.80
1 2026-08-25 00:07 639232129927860324
38 ms 91.134.131.80