DNS response history for ns1.doorlink.jp

ns1.doorlink.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-26. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 1064 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.doorlink.jp.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

1064 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

118.22.22.34

Most recently resolved hosting IP on selected date

Successful Responses

35

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.doorlink.jp

Showing DNS history for 2026-08-26 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
35 2026-08-26 11:41 639233403515141099
1725 ms 118.22.22.34
34 2026-08-26 10:46 639233370841350248
286 ms 118.22.22.34
33 2026-08-26 10:29 639233360361507238
842 ms 118.22.22.34
32 2026-08-26 10:12 639233350067824371
1700 ms 118.22.22.34
31 2026-08-26 09:54 639233339545274518
1701 ms 118.22.22.34
30 2026-08-26 09:37 639233329214918079
838 ms 118.22.22.34
29 2026-08-26 09:20 639233318749762337
1699 ms 118.22.22.34
28 2026-08-26 09:02 639233308387917838
1732 ms 118.22.22.34
27 2026-08-26 08:45 639233297961740122
839 ms 118.22.22.34
26 2026-08-26 08:27 639233287487159094
904 ms 118.22.22.34
25 2026-08-26 08:10 639233276995531707
290 ms 118.22.22.34
24 2026-08-26 07:52 639233266521568229
1711 ms 118.22.22.34
23 2026-08-26 07:35 639233256081047431
939 ms 118.22.22.34
22 2026-08-26 06:41 639233223620132921
839 ms 118.22.22.34
21 2026-08-26 06:24 639233213287814244
1721 ms 118.22.22.34
20 2026-08-26 06:06 639233202925983161
1694 ms 118.22.22.34
19 2026-08-26 05:49 639233192644780696
1711 ms 118.22.22.34
18 2026-08-26 05:32 639233182401183833
1721 ms 118.22.22.34
17 2026-08-26 05:15 639233172074181051
846 ms 118.22.22.34
16 2026-08-26 04:58 639233161808421455
290 ms 118.22.22.34
15 2026-08-26 04:41 639233151357344052
1708 ms 118.22.22.34
14 2026-08-26 04:23 639233141034116946
1127 ms 118.22.22.34
13 2026-08-26 04:06 639233130828334142
843 ms 118.22.22.34
12 2026-08-26 03:49 639233120373450007
284 ms 118.22.22.34
11 2026-08-26 03:32 639233110066216193
863 ms 118.22.22.34
10 2026-08-26 02:38 639233078065410564
12 ms 118.22.22.34
9 2026-08-26 02:21 639233067787457832
1111 ms 118.22.22.34
8 2026-08-26 02:04 639233057501801162
1691 ms 118.22.22.34
7 2026-08-26 01:47 639233047089431703
261 ms 118.22.22.34
6 2026-08-26 01:29 639233036754790688
1138 ms 118.22.22.34
5 2026-08-26 01:12 639233026412602472
256 ms 118.22.22.34
4 2026-08-26 00:55 639233016064066127
1136 ms 118.22.22.34
3 2026-08-26 00:38 639233005922655772
1696 ms 118.22.22.34
2 2026-08-26 00:21 639232995672256907
251 ms 118.22.22.34
1 2026-08-26 00:04 639232985300872416
844 ms 118.22.22.34