DNS response history for ns2.hilokune.com

ns2.hilokune.com 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 33 DNS check records, 32 successful responses, 1 failed responses, and 218 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.hilokune.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

218 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

78.46.202.173

Most recently resolved hosting IP on selected date

Successful Responses

32

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 ns2.hilokune.com

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
33 2026-08-26 10:32 639233370841350248
43 ms 78.46.202.173
32 2026-08-26 10:14 639233360361507238
8 ms 78.46.202.173
31 2026-08-26 09:57 639233350067824371
7 ms 78.46.202.173
30 2026-08-26 09:39 639233339545274518
32 ms 78.46.202.173
29 2026-08-26 09:22 639233329214918079
12 ms 78.46.202.173
28 2026-08-26 09:05 639233318749762337
2033 ms 78.46.202.173
27 2026-08-26 08:48 639233308387917838
9 ms 78.46.202.173
26 2026-08-26 08:30 639233297961740122
111 ms 78.46.202.173
25 2026-08-26 08:13 639233287487159094
35 ms 78.46.202.173
24 2026-08-26 07:55 639233276995531707
4 ms 78.46.202.173
23 2026-08-26 07:38 639233266521568229
2075 ms 78.46.202.173
22 2026-08-26 07:20 639233256081047431
52 ms 78.46.202.173
21 2026-08-26 06:26 639233223620132921
40 ms 78.46.202.173
20 2026-08-26 06:09 639233213287814244
31 ms 78.46.202.173
19 2026-08-26 05:52 639233202925983161
42 ms 78.46.202.173
18 2026-08-26 05:35 639233192644780696
2027 ms 78.46.202.173
17 2026-08-26 05:18 639233182401183833
25 ms 78.46.202.173
16 2026-08-26 05:00 639233172074181051
4 ms 78.46.202.173
15 2026-08-26 04:43 639233161808421455
3 ms 78.46.202.173
14 2026-08-26 04:26 639233151357344052
-
13 2026-08-26 04:09 639233141034116946
9 ms 78.46.202.173
12 2026-08-26 03:52 639233130828334142
16 ms 78.46.202.173
11 2026-08-26 03:34 639233120373450007
32 ms 78.46.202.173
10 2026-08-26 03:17 639233110066216193
37 ms 78.46.202.173
9 2026-08-26 02:24 639233078065410564
86 ms 78.46.202.173
8 2026-08-26 02:06 639233067787457832
43 ms 78.46.202.173
7 2026-08-26 01:49 639233057501801162
3 ms 78.46.202.173
6 2026-08-26 01:32 639233047089431703
36 ms 78.46.202.173
5 2026-08-26 01:15 639233036754790688
20 ms 78.46.202.173
4 2026-08-26 00:57 639233026412602472
3 ms 78.46.202.173
3 2026-08-26 00:40 639233016064066127
74 ms 78.46.202.173
2 2026-08-26 00:23 639233005922655772
30 ms 78.46.202.173
1 2026-08-26 00:06 639232995672256907
3 ms 78.46.202.173