DNS response history for ns2.hardesex.net

ns2.hardesex.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 31 DNS check records, 31 successful responses, 0 failed responses, and 41 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.hardesex.net.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

41 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:01

All timestamps shown in UTC

Latest Resolved IP on Selected Date

145.239.244.131

Most recently resolved hosting IP on selected date

Successful Responses

31

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.hardesex.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
31 2026-08-26 10:01 639233350067824371
21 ms 145.239.244.131
30 2026-08-26 09:44 639233339545274518
31 ms 145.239.244.131
29 2026-08-26 09:26 639233329214918079
20 ms 145.239.244.131
28 2026-08-26 09:09 639233318749762337
26 ms 145.239.244.131
27 2026-08-26 08:52 639233308387917838
22 ms 145.239.244.131
26 2026-08-26 08:34 639233297961740122
33 ms 145.239.244.131
25 2026-08-26 08:17 639233287487159094
39 ms 145.239.244.131
24 2026-08-26 07:59 639233276995531707
22 ms 145.239.244.131
23 2026-08-26 07:42 639233266521568229
10 ms 145.239.244.131
22 2026-08-26 07:24 639233256081047431
32 ms 145.239.244.131
21 2026-08-26 06:30 639233223620132921
18 ms 145.239.244.131
20 2026-08-26 06:13 639233213287814244
29 ms 145.239.244.131
19 2026-08-26 05:56 639233202925983161
35 ms 145.239.244.131
18 2026-08-26 05:39 639233192644780696
30 ms 145.239.244.131
17 2026-08-26 05:22 639233182401183833
44 ms 145.239.244.131
16 2026-08-26 05:05 639233172074181051
20 ms 145.239.244.131
15 2026-08-26 04:47 639233161808421455
134 ms 145.239.244.131
14 2026-08-26 04:30 639233151357344052
120 ms 145.239.244.131
13 2026-08-26 04:13 639233141034116946
25 ms 145.239.244.131
12 2026-08-26 03:56 639233130828334142
87 ms 145.239.244.131
11 2026-08-26 03:38 639233120373450007
47 ms 145.239.244.131
10 2026-08-26 03:21 639233110066216193
31 ms 145.239.244.131
9 2026-08-26 02:28 639233078065410564
50 ms 145.239.244.131
8 2026-08-26 02:11 639233067787457832
40 ms 145.239.244.131
7 2026-08-26 01:54 639233057501801162
33 ms 145.239.244.131
6 2026-08-26 01:36 639233047089431703
21 ms 145.239.244.131
5 2026-08-26 01:19 639233036754790688
21 ms 145.239.244.131
4 2026-08-26 01:02 639233026412602472
41 ms 145.239.244.131
3 2026-08-26 00:44 639233016064066127
30 ms 145.239.244.131
2 2026-08-26 00:27 639233005922655772
22 ms 145.239.244.131
1 2026-08-26 00:10 639232995672256907
144 ms 145.239.244.131