DNS response history for ns501.olink.ne.jp

ns501.olink.ne.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 574 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 ns501.olink.ne.jp.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

574 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

203.140.99.120

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 ns501.olink.ne.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:40 639233403515141099
762 ms 203.140.99.120
34 2026-08-26 10:45 639233370841350248
533 ms 203.140.99.120
33 2026-08-26 10:28 639233360361507238
646 ms 203.140.99.120
32 2026-08-26 10:11 639233350067824371
906 ms 203.140.99.120
31 2026-08-26 09:53 639233339545274518
561 ms 203.140.99.120
30 2026-08-26 09:36 639233329214918079
542 ms 203.140.99.120
29 2026-08-26 09:19 639233318749762337
568 ms 203.140.99.120
28 2026-08-26 09:01 639233308387917838
561 ms 203.140.99.120
27 2026-08-26 08:44 639233297961740122
508 ms 203.140.99.120
26 2026-08-26 08:26 639233287487159094
699 ms 203.140.99.120
25 2026-08-26 08:09 639233276995531707
505 ms 203.140.99.120
24 2026-08-26 07:52 639233266521568229
518 ms 203.140.99.120
23 2026-08-26 07:34 639233256081047431
911 ms 203.140.99.120
22 2026-08-26 06:40 639233223620132921
519 ms 203.140.99.120
21 2026-08-26 06:23 639233213287814244
791 ms 203.140.99.120
20 2026-08-26 06:05 639233202925983161
514 ms 203.140.99.120
19 2026-08-26 05:48 639233192644780696
516 ms 203.140.99.120
18 2026-08-26 05:31 639233182401183833
536 ms 203.140.99.120
17 2026-08-26 05:14 639233172074181051
525 ms 203.140.99.120
16 2026-08-26 04:57 639233161808421455
520 ms 203.140.99.120
15 2026-08-26 04:40 639233151357344052
505 ms 203.140.99.120
14 2026-08-26 04:22 639233141034116946
522 ms 203.140.99.120
13 2026-08-26 04:05 639233130828334142
507 ms 203.140.99.120
12 2026-08-26 03:48 639233120373450007
508 ms 203.140.99.120
11 2026-08-26 03:31 639233110066216193
551 ms 203.140.99.120
10 2026-08-26 02:37 639233078065410564
509 ms 203.140.99.120
9 2026-08-26 02:20 639233067787457832
507 ms 203.140.99.120
8 2026-08-26 02:03 639233057501801162
515 ms 203.140.99.120
7 2026-08-26 01:46 639233047089431703
520 ms 203.140.99.120
6 2026-08-26 01:29 639233036754790688
519 ms 203.140.99.120
5 2026-08-26 01:11 639233026412602472
515 ms 203.140.99.120
4 2026-08-26 00:54 639233016064066127
519 ms 203.140.99.120
3 2026-08-26 00:37 639233005922655772
745 ms 203.140.99.120
2 2026-08-26 00:20 639232995672256907
501 ms 203.140.99.120
1 2026-08-26 00:03 639232985300872416
518 ms 203.140.99.120