DNS response history for ns5.hayler.de

ns5.hayler.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 27 DNS check records, 27 successful responses, 0 failed responses, and 425 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 ns5.hayler.de.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

425 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

192.241.202.223

Most recently resolved hosting IP on selected date

Successful Responses

27

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 ns5.hayler.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
27 2026-08-25 09:23 639232461630217327
2178 ms 192.241.202.223
26 2026-08-25 09:06 639232451282965990
57 ms 192.241.202.223
25 2026-08-25 08:49 639232440814614938
190 ms 192.241.202.223
24 2026-08-25 08:31 639232430410720425
89 ms 192.241.202.223
23 2026-08-25 08:14 639232420003096185
2049 ms 192.241.202.223
22 2026-08-25 07:57 639232409467287444
27 ms 192.241.202.223
21 2026-08-25 07:39 639232399077195997
22 ms 192.241.202.223
20 2026-08-25 07:22 639232388731528337
41 ms 192.241.202.223
19 2026-08-25 07:04 639232378288598612
42 ms 192.241.202.223
18 2026-08-25 06:11 639232346196373643
40 ms 192.241.202.223
17 2026-08-25 05:54 639232336112370741
2497 ms 192.241.202.223
16 2026-08-25 05:37 639232326146508970
172 ms 192.241.202.223
15 2026-08-25 05:21 639232316189381720
43 ms 192.241.202.223
14 2026-08-25 05:04 639232306217998913
29 ms 192.241.202.223
13 2026-08-25 04:48 639232296255744174
42 ms 192.241.202.223
12 2026-08-25 04:31 639232286095760789
48 ms 192.241.202.223
11 2026-08-25 04:14 639232276086186273
56 ms 192.241.202.223
10 2026-08-25 03:57 639232265900986425
79 ms 192.241.202.223
9 2026-08-25 03:40 639232255723518075
73 ms 192.241.202.223
8 2026-08-25 03:23 639232245484452890
57 ms 192.241.202.223
7 2026-08-25 03:06 639232235157175331
247 ms 192.241.202.223
6 2026-08-25 02:13 639232203197189095
477 ms 192.241.202.223
5 2026-08-25 01:55 639232192844564298
56 ms 192.241.202.223
4 2026-08-25 01:38 639232182496008942
43 ms 192.241.202.223
3 2026-08-25 01:21 639232172197053132
2725 ms 192.241.202.223
2 2026-08-25 00:28 639232140250307418
41 ms 192.241.202.223
1 2026-08-25 00:11 639232129927860324
53 ms 192.241.202.223