DNS response history for ns1.hiclub.jp

ns1.hiclub.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 30 DNS check records, 29 successful responses, 1 failed responses, and 184 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.hiclub.jp.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

184 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

119.63.197.30

Most recently resolved hosting IP on selected date

Successful Responses

29

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.hiclub.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
30 2026-08-26 09:43 639233339545274518
128 ms 119.63.197.30
29 2026-08-26 09:26 639233329214918079
31 ms 119.63.197.30
28 2026-08-26 09:08 639233318749762337
25 ms 119.63.197.30
27 2026-08-26 08:51 639233308387917838
44 ms 119.63.197.30
26 2026-08-26 08:33 639233297961740122
16 ms 119.63.197.30
25 2026-08-26 08:16 639233287487159094
-
24 2026-08-26 07:59 639233276995531707
28 ms 119.63.197.30
23 2026-08-26 07:41 639233266521568229
44 ms 119.63.197.30
22 2026-08-26 07:24 639233256081047431
49 ms 119.63.197.30
21 2026-08-26 06:30 639233223620132921
2019 ms 119.63.197.30
20 2026-08-26 06:12 639233213287814244
26 ms 119.63.197.30
19 2026-08-26 05:55 639233202925983161
52 ms 119.63.197.30
18 2026-08-26 05:38 639233192644780696
30 ms 119.63.197.30
17 2026-08-26 05:21 639233182401183833
34 ms 119.63.197.30
16 2026-08-26 05:04 639233172074181051
32 ms 119.63.197.30
15 2026-08-26 04:47 639233161808421455
315 ms 119.63.197.30
14 2026-08-26 04:29 639233151357344052
15 ms 119.63.197.30
13 2026-08-26 04:12 639233141034116946
9 ms 119.63.197.30
12 2026-08-26 03:55 639233130828334142
42 ms 119.63.197.30
11 2026-08-26 03:38 639233120373450007
38 ms 119.63.197.30
10 2026-08-26 03:20 639233110066216193
39 ms 119.63.197.30
9 2026-08-26 02:27 639233078065410564
17 ms 119.63.197.30
8 2026-08-26 02:10 639233067787457832
77 ms 119.63.197.30
7 2026-08-26 01:53 639233057501801162
2036 ms 119.63.197.30
6 2026-08-26 01:35 639233047089431703
28 ms 119.63.197.30
5 2026-08-26 01:18 639233036754790688
65 ms 119.63.197.30
4 2026-08-26 01:01 639233026412602472
44 ms 119.63.197.30
3 2026-08-26 00:44 639233016064066127
29 ms 119.63.197.30
2 2026-08-26 00:27 639233005922655772
24 ms 119.63.197.30
1 2026-08-26 00:10 639232995672256907
7 ms 119.63.197.30