DNS response history for ns2.hoozt.de

ns2.hoozt.de 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-25. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 274 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.hoozt.de.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

274 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

81.169.245.50

Most recently resolved hosting IP on selected date

Successful Responses

37

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.hoozt.de

Showing DNS history for 2026-08-25 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-25 12:47 639232587225721862
40 ms 81.169.245.50
36 2026-08-25 12:30 639232576780683689
34 ms 81.169.245.50
35 2026-08-25 12:13 639232566381512620
48 ms 81.169.245.50
34 2026-08-25 11:55 639232556111768563
2203 ms 81.169.245.50
33 2026-08-25 11:38 639232545839529039
35 ms 81.169.245.50
32 2026-08-25 11:21 639232535349285207
40 ms 81.169.245.50
31 2026-08-25 11:04 639232524938080723
36 ms 81.169.245.50
30 2026-08-25 10:10 639232492740373468
37 ms 81.169.245.50
29 2026-08-25 09:52 639232482235303141
109 ms 81.169.245.50
28 2026-08-25 09:35 639232471861770303
39 ms 81.169.245.50
27 2026-08-25 09:18 639232461630217327
114 ms 81.169.245.50
26 2026-08-25 09:01 639232451282965990
2049 ms 81.169.245.50
25 2026-08-25 08:43 639232440814614938
33 ms 81.169.245.50
24 2026-08-25 08:26 639232430410720425
103 ms 81.169.245.50
23 2026-08-25 08:09 639232420003096185
34 ms 81.169.245.50
22 2026-08-25 07:51 639232409467287444
43 ms 81.169.245.50
21 2026-08-25 07:34 639232399077195997
32 ms 81.169.245.50
20 2026-08-25 07:17 639232388731528337
81 ms 81.169.245.50
19 2026-08-25 06:59 639232378288598612
54 ms 81.169.245.50
18 2026-08-25 06:06 639232346196373643
45 ms 81.169.245.50
17 2026-08-25 05:49 639232336112370741
2022 ms 81.169.245.50
16 2026-08-25 05:32 639232326146508970
37 ms 81.169.245.50
15 2026-08-25 05:16 639232316189381720
23 ms 81.169.245.50
14 2026-08-25 04:59 639232306217998913
33 ms 81.169.245.50
13 2026-08-25 04:43 639232296255744174
49 ms 81.169.245.50
12 2026-08-25 04:25 639232286095760789
108 ms 81.169.245.50
11 2026-08-25 04:09 639232276086186273
16 ms 81.169.245.50
10 2026-08-25 03:52 639232265900986425
2100 ms 81.169.245.50
9 2026-08-25 03:35 639232255723518075
34 ms 81.169.245.50
8 2026-08-25 03:18 639232245484452890
41 ms 81.169.245.50
7 2026-08-25 03:01 639232235157175331
47 ms 81.169.245.50
6 2026-08-25 02:07 639232203197189095
32 ms 81.169.245.50
5 2026-08-25 01:50 639232192844564298
149 ms 81.169.245.50
4 2026-08-25 01:33 639232182496008942
50 ms 81.169.245.50
3 2026-08-25 01:16 639232172197053132
16 ms 81.169.245.50
2 2026-08-25 00:22 639232140250307418
123 ms 81.169.245.50
1 2026-08-25 00:05 639232129927860324
36 ms 81.169.245.50