DNS response history for ns2.hardynet.net

ns2.hardynet.net 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, 33 successful responses, 0 failed responses, and 257 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.hardynet.net.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

257 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

192.124.249.110

Most recently resolved hosting IP on selected date

Successful Responses

33

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.hardynet.net

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:40 639233370841350248
7 ms 192.124.249.110
32 2026-08-26 10:23 639233360361507238
153 ms 192.124.249.110
31 2026-08-26 10:05 639233350067824371
295 ms 192.124.249.110
30 2026-08-26 09:48 639233339545274518
25 ms 192.124.249.110
29 2026-08-26 09:31 639233329214918079
2013 ms 192.124.249.110
28 2026-08-26 09:13 639233318749762337
19 ms 192.124.249.110
27 2026-08-26 08:56 639233308387917838
178 ms 192.124.249.110
26 2026-08-26 08:39 639233297961740122
172 ms 192.124.249.110
25 2026-08-26 08:21 639233287487159094
166 ms 192.124.249.110
24 2026-08-26 08:04 639233276995531707
323 ms 192.124.249.110
23 2026-08-26 07:46 639233266521568229
404 ms 192.124.249.110
22 2026-08-26 07:29 639233256081047431
156 ms 192.124.249.110
21 2026-08-26 06:35 639233223620132921
106 ms 192.124.249.110
20 2026-08-26 06:18 639233213287814244
152 ms 192.124.249.110
19 2026-08-26 06:00 639233202925983161
183 ms 192.124.249.110
18 2026-08-26 05:43 639233192644780696
308 ms 192.124.249.110
17 2026-08-26 05:26 639233182401183833
420 ms 192.124.249.110
16 2026-08-26 05:09 639233172074181051
449 ms 192.124.249.110
15 2026-08-26 04:52 639233161808421455
16 ms 192.124.249.110
14 2026-08-26 04:34 639233151357344052
296 ms 192.124.249.110
13 2026-08-26 04:17 639233141034116946
295 ms 192.124.249.110
12 2026-08-26 04:00 639233130828334142
16 ms 192.124.249.110
11 2026-08-26 03:43 639233120373450007
448 ms 192.124.249.110
10 2026-08-26 03:25 639233110066216193
299 ms 192.124.249.110
9 2026-08-26 02:32 639233078065410564
49 ms 192.124.249.110
8 2026-08-26 02:15 639233067787457832
296 ms 192.124.249.110
7 2026-08-26 01:58 639233057501801162
9 ms 192.124.249.110
6 2026-08-26 01:41 639233047089431703
162 ms 192.124.249.110
5 2026-08-26 01:23 639233036754790688
13 ms 192.124.249.110
4 2026-08-26 01:06 639233026412602472
299 ms 192.124.249.110
3 2026-08-26 00:49 639233016064066127
150 ms 192.124.249.110
2 2026-08-26 00:32 639233005922655772
445 ms 192.124.249.110
1 2026-08-26 00:15 639232995672256907
147 ms 192.124.249.110