DNS response history for ns1.sensor-tokyo.com

ns1.sensor-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-24. For this date, NameServerHistory found 26 DNS check records, 26 successful responses, 0 failed responses, and 264 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.sensor-tokyo.com.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

264 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 10:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

151.80.201.169

Most recently resolved hosting IP on selected date

Successful Responses

26

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.sensor-tokyo.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
26 2026-08-24 10:31 639231641791249939
92 ms 151.80.201.169
25 2026-08-24 10:14 639231631866211033
43 ms 151.80.201.169
24 2026-08-24 09:57 639231621644955316
67 ms 151.80.201.169
23 2026-08-24 09:40 639231611478799259
75 ms 151.80.201.169
22 2026-08-24 08:48 639231579923718211
20 ms 151.80.201.169
21 2026-08-24 08:31 639231569810702936
2041 ms 151.80.201.169
20 2026-08-24 08:14 639231559762411619
3 ms 151.80.201.169
19 2026-08-24 07:57 639231549663595407
34 ms 151.80.201.169
18 2026-08-24 07:05 639231518076817246
34 ms 151.80.201.169
17 2026-08-24 06:48 639231508078650885
84 ms 151.80.201.169
16 2026-08-24 06:32 639231498210697093
32 ms 151.80.201.169
15 2026-08-24 06:15 639231488109699360
41 ms 151.80.201.169
14 2026-08-24 05:22 639231456772510692
48 ms 151.80.201.169
13 2026-08-24 05:06 639231447084631185
3 ms 151.80.201.169
12 2026-08-24 04:50 639231437208519473
5 ms 151.80.201.169
11 2026-08-24 04:33 639231427209627490
2028 ms 151.80.201.169
10 2026-08-24 03:41 639231395791246644
3 ms 151.80.201.169
9 2026-08-24 03:25 639231386075551458
48 ms 151.80.201.169
8 2026-08-24 03:08 639231376208713791
31 ms 151.80.201.169
7 2026-08-24 02:51 639231366170589276
48 ms 151.80.201.169
6 2026-08-24 01:59 639231334732159368
3 ms 151.80.201.169
5 2026-08-24 01:43 639231325035670078
2025 ms 151.80.201.169
4 2026-08-24 01:26 639231315132253837
32 ms 151.80.201.169
3 2026-08-24 01:10 639231305014280808
4 ms 151.80.201.169
2 2026-08-24 00:18 639231273779380675
3 ms 151.80.201.169
1 2026-08-24 00:02 639231264180839154
4 ms 151.80.201.169