DNS response history for dns2.nsk.ne.jp

dns2.nsk.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-25. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 422 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 dns2.nsk.ne.jp.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

422 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

61.213.209.162

Most recently resolved hosting IP on selected date

Successful Responses

36

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 dns2.nsk.ne.jp

Showing DNS history for 2026-08-25 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
36 2026-08-25 12:41 639232576780683689
903 ms 61.213.209.162
35 2026-08-25 12:24 639232566381512620
276 ms 61.213.209.162
34 2026-08-25 12:06 639232556111768563
265 ms 61.213.209.162
33 2026-08-25 11:49 639232545839529039
262 ms 61.213.209.162
32 2026-08-25 11:32 639232535349285207
248 ms 61.213.209.162
31 2026-08-25 11:14 639232524938080723
248 ms 61.213.209.162
30 2026-08-25 10:21 639232492740373468
253 ms 61.213.209.162
29 2026-08-25 10:04 639232482235303141
354 ms 61.213.209.162
28 2026-08-25 09:46 639232471861770303
263 ms 61.213.209.162
27 2026-08-25 09:29 639232461630217327
271 ms 61.213.209.162
26 2026-08-25 09:12 639232451282965990
251 ms 61.213.209.162
25 2026-08-25 08:54 639232440814614938
250 ms 61.213.209.162
24 2026-08-25 08:37 639232430410720425
268 ms 61.213.209.162
23 2026-08-25 08:20 639232420003096185
335 ms 61.213.209.162
22 2026-08-25 08:02 639232409467287444
251 ms 61.213.209.162
21 2026-08-25 07:45 639232399077195997
272 ms 61.213.209.162
20 2026-08-25 07:27 639232388731528337
255 ms 61.213.209.162
19 2026-08-25 07:10 639232378288598612
258 ms 61.213.209.162
18 2026-08-25 06:16 639232346196373643
250 ms 61.213.209.162
17 2026-08-25 05:59 639232336112370741
253 ms 61.213.209.162
16 2026-08-25 05:43 639232326146508970
250 ms 61.213.209.162
15 2026-08-25 05:26 639232316189381720
252 ms 61.213.209.162
14 2026-08-25 05:10 639232306217998913
519 ms 61.213.209.162
13 2026-08-25 04:53 639232296255744174
2268 ms 61.213.209.162
12 2026-08-25 04:36 639232286095760789
263 ms 61.213.209.162
11 2026-08-25 04:19 639232276086186273
256 ms 61.213.209.162
10 2026-08-25 04:03 639232265900986425
491 ms 61.213.209.162
9 2026-08-25 03:46 639232255723518075
552 ms 61.213.209.162
8 2026-08-25 03:29 639232245484452890
250 ms 61.213.209.162
7 2026-08-25 03:11 639232235157175331
2286 ms 61.213.209.162
6 2026-08-25 02:18 639232203197189095
294 ms 61.213.209.162
5 2026-08-25 02:01 639232192844564298
256 ms 61.213.209.162
4 2026-08-25 01:44 639232182496008942
269 ms 61.213.209.162
3 2026-08-25 01:26 639232172197053132
250 ms 61.213.209.162
2 2026-08-25 00:33 639232140250307418
257 ms 61.213.209.162
1 2026-08-25 00:16 639232129927860324
509 ms 61.213.209.162