DNS response history for ns02.diehl.com

ns02.diehl.com 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 28 DNS check records, 26 successful responses, 2 failed responses, and 186 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 ns02.diehl.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

186 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:35

All timestamps shown in UTC

Latest Resolved IP on Selected Date

193.201.238.242

Most recently resolved hosting IP on selected date

Successful Responses

26

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

7%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns02.diehl.com

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
28 2026-08-25 09:35 639232471861770303
11 ms 193.201.238.242
27 2026-08-25 09:18 639232461630217327
23 ms 193.201.238.242
26 2026-08-25 09:00 639232451282965990
9 ms 193.201.238.242
25 2026-08-25 08:43 639232440814614938
29 ms 193.201.238.242
24 2026-08-25 08:26 639232430410720425
12 ms 193.201.238.242
23 2026-08-25 08:08 639232420003096185
18 ms 193.201.238.242
22 2026-08-25 07:51 639232409467287444
-
21 2026-08-25 07:33 639232399077195997
120 ms 193.201.238.242
20 2026-08-25 07:16 639232388731528337
34 ms 193.201.238.242
19 2026-08-25 06:59 639232378288598612
13 ms 193.201.238.242
18 2026-08-25 06:05 639232346196373643
67 ms 193.201.238.242
17 2026-08-25 05:48 639232336112370741
40 ms 193.201.238.242
16 2026-08-25 05:32 639232326146508970
-
15 2026-08-25 05:15 639232316189381720
2026 ms 193.201.238.242
14 2026-08-25 04:59 639232306217998913
13 ms 193.201.238.242
13 2026-08-25 04:42 639232296255744174
12 ms 193.201.238.242
12 2026-08-25 04:25 639232286095760789
58 ms 193.201.238.242
11 2026-08-25 04:08 639232276086186273
13 ms 193.201.238.242
10 2026-08-25 03:52 639232265900986425
40 ms 193.201.238.242
9 2026-08-25 03:35 639232255723518075
16 ms 193.201.238.242
8 2026-08-25 03:17 639232245484452890
39 ms 193.201.238.242
7 2026-08-25 03:00 639232235157175331
2034 ms 193.201.238.242
6 2026-08-25 02:07 639232203197189095
30 ms 193.201.238.242
5 2026-08-25 01:50 639232192844564298
11 ms 193.201.238.242
4 2026-08-25 01:33 639232182496008942
83 ms 193.201.238.242
3 2026-08-25 01:15 639232172197053132
46 ms 193.201.238.242
2 2026-08-25 00:22 639232140250307418
35 ms 193.201.238.242
1 2026-08-25 00:05 639232129927860324
13 ms 193.201.238.242