DNS response history for wtk-ns03.usen.ad.jp

wtk-ns03.usen.ad.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 32 DNS check records, 32 successful responses, 0 failed responses, and 334 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 wtk-ns03.usen.ad.jp.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

334 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

61.122.112.97

Most recently resolved hosting IP on selected date

Successful Responses

32

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 wtk-ns03.usen.ad.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
32 2026-08-27 10:24 639234222943951923
258 ms 61.122.112.97
31 2026-08-27 10:06 639234212558002823
250 ms 61.122.112.97
30 2026-08-27 09:49 639234202117531850
250 ms 61.122.112.97
29 2026-08-27 09:32 639234191649612722
495 ms 61.122.112.97
28 2026-08-27 09:14 639234181105879568
249 ms 61.122.112.97
27 2026-08-27 08:57 639234170713214496
245 ms 61.122.112.97
26 2026-08-27 08:39 639234160341037652
245 ms 61.122.112.97
25 2026-08-27 08:22 639234149799404224
31 ms 61.122.112.97
24 2026-08-27 08:04 639234139553286469
248 ms 61.122.112.97
23 2026-08-27 07:11 639234107183588293
240 ms 61.122.112.97
22 2026-08-27 06:54 639234096905435724
248 ms 61.122.112.97
21 2026-08-27 06:36 639234086579410775
240 ms 61.122.112.97
20 2026-08-27 06:19 639234076291157956
259 ms 61.122.112.97
19 2026-08-27 06:02 639234065981939454
2329 ms 61.122.112.97
18 2026-08-27 05:45 639234055548642997
256 ms 61.122.112.97
17 2026-08-27 05:27 639234045267979603
286 ms 61.122.112.97
16 2026-08-27 05:10 639234034999717463
3 ms 61.122.112.97
15 2026-08-27 04:53 639234024739225358
248 ms 61.122.112.97
14 2026-08-27 04:36 639234014311170162
259 ms 61.122.112.97
13 2026-08-27 04:19 639234003806017640
503 ms 61.122.112.97
12 2026-08-27 04:01 639233993356203030
522 ms 61.122.112.97
11 2026-08-27 03:08 639233961301716608
266 ms 61.122.112.97
10 2026-08-27 02:50 639233950834200647
246 ms 61.122.112.97
9 2026-08-27 02:33 639233940431849026
239 ms 61.122.112.97
8 2026-08-27 02:16 639233930110596398
256 ms 61.122.112.97
7 2026-08-27 01:58 639233919705434540
7 ms 61.122.112.97
6 2026-08-27 01:41 639233909452807845
490 ms 61.122.112.97
5 2026-08-27 01:24 639233899096420820
520 ms 61.122.112.97
4 2026-08-27 01:07 639233888707824939
252 ms 61.122.112.97
3 2026-08-27 00:49 639233878461203802
251 ms 61.122.112.97
2 2026-08-27 00:32 639233868060868209
251 ms 61.122.112.97
1 2026-08-27 00:15 639233857450922991
244 ms 61.122.112.97