DNS response history for ns1.hardloco.com

ns1.hardloco.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 30 DNS check records, 30 successful responses, 0 failed responses, and 413 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.hardloco.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

413 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.101.22.170

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns1.hardloco.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
30 2026-08-26 09:44 639233339545274518
101 ms 185.101.22.170
29 2026-08-26 09:27 639233329214918079
468 ms 185.101.22.170
28 2026-08-26 09:09 639233318749762337
101 ms 185.101.22.170
27 2026-08-26 08:52 639233308387917838
85 ms 185.101.22.170
26 2026-08-26 08:35 639233297961740122
2516 ms 185.101.22.170
25 2026-08-26 08:17 639233287487159094
2476 ms 185.101.22.170
24 2026-08-26 08:00 639233276995531707
2473 ms 185.101.22.170
23 2026-08-26 07:42 639233266521568229
514 ms 185.101.22.170
22 2026-08-26 07:25 639233256081047431
84 ms 185.101.22.170
21 2026-08-26 06:31 639233223620132921
91 ms 185.101.22.170
20 2026-08-26 06:14 639233213287814244
527 ms 185.101.22.170
19 2026-08-26 05:56 639233202925983161
117 ms 185.101.22.170
18 2026-08-26 05:39 639233192644780696
100 ms 185.101.22.170
17 2026-08-26 05:22 639233182401183833
517 ms 185.101.22.170
16 2026-08-26 05:05 639233172074181051
86 ms 185.101.22.170
15 2026-08-26 04:48 639233161808421455
79 ms 185.101.22.170
14 2026-08-26 04:30 639233151357344052
89 ms 185.101.22.170
13 2026-08-26 04:13 639233141034116946
506 ms 185.101.22.170
12 2026-08-26 03:56 639233130828334142
111 ms 185.101.22.170
11 2026-08-26 03:39 639233120373450007
457 ms 185.101.22.170
10 2026-08-26 03:22 639233110066216193
88 ms 185.101.22.170
9 2026-08-26 02:28 639233078065410564
82 ms 185.101.22.170
8 2026-08-26 02:11 639233067787457832
78 ms 185.101.22.170
7 2026-08-26 01:54 639233057501801162
88 ms 185.101.22.170
6 2026-08-26 01:37 639233047089431703
108 ms 185.101.22.170
5 2026-08-26 01:19 639233036754790688
91 ms 185.101.22.170
4 2026-08-26 01:02 639233026412602472
97 ms 185.101.22.170
3 2026-08-26 00:45 639233016064066127
92 ms 185.101.22.170
2 2026-08-26 00:28 639233005922655772
92 ms 185.101.22.170
1 2026-08-26 00:11 639232995672256907
83 ms 185.101.22.170