DNS response history for ns2.h-s-k.jp

ns2.h-s-k.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 29 DNS check records, 29 successful responses, 0 failed responses, and 592 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 ns2.h-s-k.jp.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

592 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

203.137.115.95

Most recently resolved hosting IP on selected date

Successful Responses

29

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 ns2.h-s-k.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
29 2026-08-27 09:32 639234191649612722
537 ms 203.137.115.95
28 2026-08-27 09:15 639234181105879568
496 ms 203.137.115.95
27 2026-08-27 08:57 639234170713214496
502 ms 203.137.115.95
26 2026-08-27 08:40 639234160341037652
251 ms 203.137.115.95
25 2026-08-27 08:22 639234149799404224
495 ms 203.137.115.95
24 2026-08-27 08:05 639234139553286469
500 ms 203.137.115.95
23 2026-08-27 07:11 639234107183588293
496 ms 203.137.115.95
22 2026-08-27 06:54 639234096905435724
302 ms 203.137.115.95
21 2026-08-27 06:37 639234086579410775
495 ms 203.137.115.95
20 2026-08-27 06:20 639234076291157956
502 ms 203.137.115.95
19 2026-08-27 06:03 639234065981939454
261 ms 203.137.115.95
18 2026-08-27 05:45 639234055548642997
2047 ms 203.137.115.95
17 2026-08-27 05:28 639234045267979603
496 ms 203.137.115.95
16 2026-08-27 05:11 639234034999717463
32 ms 203.137.115.95
15 2026-08-27 04:54 639234024739225358
2502 ms 203.137.115.95
14 2026-08-27 04:37 639234014311170162
508 ms 203.137.115.95
13 2026-08-27 04:19 639234003806017640
486 ms 203.137.115.95
12 2026-08-27 04:02 639233993356203030
2032 ms 203.137.115.95
11 2026-08-27 03:08 639233961301716608
501 ms 203.137.115.95
10 2026-08-27 02:51 639233950834200647
490 ms 203.137.115.95
9 2026-08-27 02:33 639233940431849026
254 ms 203.137.115.95
8 2026-08-27 02:16 639233930110596398
3 ms 203.137.115.95
7 2026-08-27 01:59 639233919705434540
486 ms 203.137.115.95
6 2026-08-27 01:42 639233909452807845
501 ms 203.137.115.95
5 2026-08-27 01:24 639233899096420820
4 ms 203.137.115.95
4 2026-08-27 01:07 639233888707824939
501 ms 203.137.115.95
3 2026-08-27 00:50 639233878461203802
505 ms 203.137.115.95
2 2026-08-27 00:33 639233868060868209
497 ms 203.137.115.95
1 2026-08-27 00:15 639233857450922991
495 ms 203.137.115.95