DNS response history for ns2.hoerdtonline.info

ns2.hoerdtonline.info 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 463 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.hoerdtonline.info.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

463 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

8.8.8.84

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.hoerdtonline.info

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
472 ms 8.8.8.84
32 2026-08-26 10:23 639233360361507238
358 ms 8.8.8.84
31 2026-08-26 10:05 639233350067824371
450 ms 8.8.8.84
30 2026-08-26 09:48 639233339545274518
363 ms 8.8.8.84
29 2026-08-26 09:31 639233329214918079
179 ms 8.8.8.84
28 2026-08-26 09:13 639233318749762337
42 ms 8.8.8.84
27 2026-08-26 08:56 639233308387917838
470 ms 8.8.8.84
26 2026-08-26 08:39 639233297961740122
302 ms 8.8.8.84
25 2026-08-26 08:21 639233287487159094
238 ms 8.8.8.84
24 2026-08-26 08:04 639233276995531707
345 ms 8.8.8.84
23 2026-08-26 07:46 639233266521568229
451 ms 8.8.8.84
22 2026-08-26 07:29 639233256081047431
80 ms 8.8.8.84
21 2026-08-26 06:35 639233223620132921
429 ms 8.8.8.84
20 2026-08-26 06:18 639233213287814244
368 ms 8.8.8.84
19 2026-08-26 06:00 639233202925983161
8 ms 8.8.8.84
18 2026-08-26 05:43 639233192644780696
449 ms 8.8.8.84
17 2026-08-26 05:26 639233182401183833
79 ms 8.8.8.84
16 2026-08-26 05:09 639233172074181051
448 ms 8.8.8.84
15 2026-08-26 04:52 639233161808421455
446 ms 8.8.8.84
14 2026-08-26 04:34 639233151357344052
128 ms 8.8.8.84
13 2026-08-26 04:17 639233141034116946
-
12 2026-08-26 04:00 639233130828334142
501 ms 8.8.8.84
11 2026-08-26 03:43 639233120373450007
428 ms 8.8.8.84
10 2026-08-26 03:25 639233110066216193
216 ms 8.8.8.84
9 2026-08-26 02:32 639233078065410564
89 ms 8.8.8.84
8 2026-08-26 02:15 639233067787457832
44 ms 8.8.8.84
7 2026-08-26 01:58 639233057501801162
4146 ms 8.8.8.84
6 2026-08-26 01:41 639233047089431703
81 ms 8.8.8.84
5 2026-08-26 01:23 639233036754790688
447 ms 8.8.8.84
4 2026-08-26 01:06 639233026412602472
76 ms 8.8.8.84
3 2026-08-26 00:49 639233016064066127
331 ms 8.8.8.84
2 2026-08-26 00:32 639233005922655772
2237 ms 8.8.8.84
1 2026-08-26 00:15 639232995672256907
128 ms 8.8.8.84