DNS response history for ns3.inetdienst.de

ns3.inetdienst.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 34 DNS check records, 34 successful responses, 0 failed responses, and 208 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 ns3.inetdienst.de.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

208 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:00

All timestamps shown in UTC

Latest Resolved IP on Selected Date

109.237.143.8

Most recently resolved hosting IP on selected date

Successful Responses

34

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 ns3.inetdienst.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
34 2026-08-25 12:00 639232556111768563
21 ms 109.237.143.8
33 2026-08-25 11:43 639232545839529039
28 ms 109.237.143.8
32 2026-08-25 11:25 639232535349285207
24 ms 109.237.143.8
31 2026-08-25 11:08 639232524938080723
17 ms 109.237.143.8
30 2026-08-25 10:14 639232492740373468
2038 ms 109.237.143.8
29 2026-08-25 09:57 639232482235303141
21 ms 109.237.143.8
28 2026-08-25 09:39 639232471861770303
24 ms 109.237.143.8
27 2026-08-25 09:22 639232461630217327
21 ms 109.237.143.8
26 2026-08-25 09:05 639232451282965990
49 ms 109.237.143.8
25 2026-08-25 08:48 639232440814614938
2015 ms 109.237.143.8
24 2026-08-25 08:30 639232430410720425
27 ms 109.237.143.8
23 2026-08-25 08:13 639232420003096185
5 ms 109.237.143.8
22 2026-08-25 07:56 639232409467287444
105 ms 109.237.143.8
21 2026-08-25 07:38 639232399077195997
33 ms 109.237.143.8
20 2026-08-25 07:21 639232388731528337
21 ms 109.237.143.8
19 2026-08-25 07:04 639232378288598612
25 ms 109.237.143.8
18 2026-08-25 06:10 639232346196373643
31 ms 109.237.143.8
17 2026-08-25 05:53 639232336112370741
38 ms 109.237.143.8
16 2026-08-25 05:37 639232326146508970
27 ms 109.237.143.8
15 2026-08-25 05:20 639232316189381720
23 ms 109.237.143.8
14 2026-08-25 05:04 639232306217998913
24 ms 109.237.143.8
13 2026-08-25 04:47 639232296255744174
78 ms 109.237.143.8
12 2026-08-25 04:30 639232286095760789
2034 ms 109.237.143.8
11 2026-08-25 04:13 639232276086186273
27 ms 109.237.143.8
10 2026-08-25 03:56 639232265900986425
52 ms 109.237.143.8
9 2026-08-25 03:39 639232255723518075
37 ms 109.237.143.8
8 2026-08-25 03:22 639232245484452890
29 ms 109.237.143.8
7 2026-08-25 03:05 639232235157175331
23 ms 109.237.143.8
6 2026-08-25 02:12 639232203197189095
52 ms 109.237.143.8
5 2026-08-25 01:55 639232192844564298
21 ms 109.237.143.8
4 2026-08-25 01:37 639232182496008942
24 ms 109.237.143.8
3 2026-08-25 01:20 639232172197053132
22 ms 109.237.143.8
2 2026-08-25 00:27 639232140250307418
20 ms 109.237.143.8
1 2026-08-25 00:10 639232129927860324
53 ms 109.237.143.8