DNS response history for ns2.hardcored.com

ns2.hardcored.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 37 DNS check records, 36 successful responses, 1 failed responses, and 106 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.hardcored.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

106 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

83.149.125.150

Most recently resolved hosting IP on selected date

Successful Responses

36

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.hardcored.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
37 2026-08-26 12:20 639233434974187439
44 ms 83.149.125.150
36 2026-08-26 12:03 639233424567558554
79 ms 83.149.125.150
35 2026-08-26 11:45 639233414056832719
34 ms 83.149.125.150
34 2026-08-26 11:28 639233403515141099
99 ms 83.149.125.150
33 2026-08-26 10:33 639233370841350248
-
32 2026-08-26 10:16 639233360361507238
43 ms 83.149.125.150
31 2026-08-26 09:59 639233350067824371
61 ms 83.149.125.150
30 2026-08-26 09:41 639233339545274518
48 ms 83.149.125.150
29 2026-08-26 09:24 639233329214918079
37 ms 83.149.125.150
28 2026-08-26 09:07 639233318749762337
41 ms 83.149.125.150
27 2026-08-26 08:49 639233308387917838
21 ms 83.149.125.150
26 2026-08-26 08:32 639233297961740122
50 ms 83.149.125.150
25 2026-08-26 08:14 639233287487159094
2029 ms 83.149.125.150
24 2026-08-26 07:57 639233276995531707
46 ms 83.149.125.150
23 2026-08-26 07:39 639233266521568229
41 ms 83.149.125.150
22 2026-08-26 07:22 639233256081047431
54 ms 83.149.125.150
21 2026-08-26 06:28 639233223620132921
52 ms 83.149.125.150
20 2026-08-26 06:11 639233213287814244
57 ms 83.149.125.150
19 2026-08-26 05:53 639233202925983161
26 ms 83.149.125.150
18 2026-08-26 05:36 639233192644780696
43 ms 83.149.125.150
17 2026-08-26 05:19 639233182401183833
74 ms 83.149.125.150
16 2026-08-26 05:02 639233172074181051
44 ms 83.149.125.150
15 2026-08-26 04:45 639233161808421455
102 ms 83.149.125.150
14 2026-08-26 04:27 639233151357344052
37 ms 83.149.125.150
13 2026-08-26 04:10 639233141034116946
32 ms 83.149.125.150
12 2026-08-26 03:53 639233130828334142
47 ms 83.149.125.150
11 2026-08-26 03:36 639233120373450007
46 ms 83.149.125.150
10 2026-08-26 03:19 639233110066216193
44 ms 83.149.125.150
9 2026-08-26 02:25 639233078065410564
45 ms 83.149.125.150
8 2026-08-26 02:08 639233067787457832
86 ms 83.149.125.150
7 2026-08-26 01:51 639233057501801162
61 ms 83.149.125.150
6 2026-08-26 01:34 639233047089431703
41 ms 83.149.125.150
5 2026-08-26 01:16 639233036754790688
44 ms 83.149.125.150
4 2026-08-26 00:59 639233026412602472
89 ms 83.149.125.150
3 2026-08-26 00:42 639233016064066127
39 ms 83.149.125.150
2 2026-08-26 00:25 639233005922655772
64 ms 83.149.125.150
1 2026-08-26 00:08 639232995672256907
2 ms 83.149.125.150