DNS response history for ns.tokyo-lemonche.jp

ns.tokyo-lemonche.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-27. For this date, NameServerHistory found 25 DNS check records, 25 successful responses, 0 failed responses, and 87 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 ns.tokyo-lemonche.jp.
Records on Selected Date

25

Historical checks stored for this nameserver on selected date

Average Latency

87 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 08:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

153.123.9.22

Most recently resolved hosting IP on selected date

Successful Responses

25

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 ns.tokyo-lemonche.jp

Showing DNS history for 2026-08-27 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
25 2026-08-27 08:16 639234149799404224
84 ms 153.123.9.22
24 2026-08-27 07:58 639234139553286469
66 ms 153.123.9.22
23 2026-08-27 07:05 639234107183588293
66 ms 153.123.9.22
22 2026-08-27 06:47 639234096905435724
71 ms 153.123.9.22
21 2026-08-27 06:30 639234086579410775
48 ms 153.123.9.22
20 2026-08-27 06:13 639234076291157956
75 ms 153.123.9.22
19 2026-08-27 05:56 639234065981939454
86 ms 153.123.9.22
18 2026-08-27 05:39 639234055548642997
93 ms 153.123.9.22
17 2026-08-27 05:21 639234045267979603
88 ms 153.123.9.22
16 2026-08-27 05:04 639234034999717463
68 ms 153.123.9.22
15 2026-08-27 04:47 639234024739225358
52 ms 153.123.9.22
14 2026-08-27 04:30 639234014311170162
66 ms 153.123.9.22
13 2026-08-27 04:12 639234003806017640
47 ms 153.123.9.22
12 2026-08-27 03:55 639233993356203030
391 ms 153.123.9.22
11 2026-08-27 03:01 639233961301716608
70 ms 153.123.9.22
10 2026-08-27 02:44 639233950834200647
89 ms 153.123.9.22
9 2026-08-27 02:27 639233940431849026
155 ms 153.123.9.22
8 2026-08-27 02:09 639233930110596398
117 ms 153.123.9.22
7 2026-08-27 01:52 639233919705434540
73 ms 153.123.9.22
6 2026-08-27 01:35 639233909452807845
102 ms 153.123.9.22
5 2026-08-27 01:18 639233899096420820
27 ms 153.123.9.22
4 2026-08-27 01:00 639233888707824939
100 ms 153.123.9.22
3 2026-08-27 00:43 639233878461203802
41 ms 153.123.9.22
2 2026-08-27 00:26 639233868060868209
69 ms 153.123.9.22
1 2026-08-27 00:08 639233857450922991
36 ms 153.123.9.22