DNS response history for ns2.heiland-ohmden.de

ns2.heiland-ohmden.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-24. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 194 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.heiland-ohmden.de.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

194 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

95.173.103.11

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 ns2.heiland-ohmden.de

Showing DNS history for 2026-08-24 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-24 12:17 639231703815441688
59 ms 95.173.103.11
29 2026-08-24 12:00 639231693747052549
71 ms 95.173.103.11
28 2026-08-24 11:43 639231683712487276
71 ms 95.173.103.11
27 2026-08-24 11:26 639231673513573868
75 ms 95.173.103.11
26 2026-08-24 10:33 639231641791249939
51 ms 95.173.103.11
25 2026-08-24 10:17 639231631866211033
106 ms 95.173.103.11
24 2026-08-24 10:00 639231621644955316
47 ms 95.173.103.11
23 2026-08-24 09:43 639231611478799259
98 ms 95.173.103.11
22 2026-08-24 08:50 639231579923718211
10 ms 95.173.103.11
21 2026-08-24 08:34 639231569810702936
28 ms 95.173.103.11
20 2026-08-24 08:17 639231559762411619
57 ms 95.173.103.11
19 2026-08-24 08:00 639231549663595407
92 ms 95.173.103.11
18 2026-08-24 07:07 639231518076817246
79 ms 95.173.103.11
17 2026-08-24 06:51 639231508078650885
95 ms 95.173.103.11
16 2026-08-24 06:34 639231498210697093
68 ms 95.173.103.11
15 2026-08-24 06:17 639231488109699360
84 ms 95.173.103.11
14 2026-08-24 05:25 639231456772510692
17 ms 95.173.103.11
13 2026-08-24 05:09 639231447084631185
63 ms 95.173.103.11
12 2026-08-24 04:53 639231437208519473
29 ms 95.173.103.11
11 2026-08-24 04:36 639231427209627490
54 ms 95.173.103.11
10 2026-08-24 03:43 639231395791246644
62 ms 95.173.103.11
9 2026-08-24 03:27 639231386075551458
2034 ms 95.173.103.11
8 2026-08-24 03:11 639231376208713791
31 ms 95.173.103.11
7 2026-08-24 02:54 639231366170589276
63 ms 95.173.103.11
6 2026-08-24 02:02 639231334732159368
2137 ms 95.173.103.11
5 2026-08-24 01:46 639231325035670078
53 ms 95.173.103.11
4 2026-08-24 01:29 639231315132253837
73 ms 95.173.103.11
3 2026-08-24 01:12 639231305014280808
28 ms 95.173.103.11
2 2026-08-24 00:20 639231273779380675
49 ms 95.173.103.11
1 2026-08-24 00:04 639231264180839154
43 ms 95.173.103.11