DNS response history for ns02.netility.de

ns02.netility.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 29 DNS check records, 29 successful responses, 0 failed responses, and 367 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.netility.de.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

367 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:55

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.136.99.139

Most recently resolved hosting IP on selected date

Successful Responses

29

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 ns02.netility.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
29 2026-08-25 09:55 639232482235303141
39 ms 185.136.99.139
28 2026-08-25 09:37 639232471861770303
50 ms 185.136.99.139
27 2026-08-25 09:20 639232461630217327
24 ms 185.136.99.139
26 2026-08-25 09:03 639232451282965990
35 ms 185.136.99.139
25 2026-08-25 08:46 639232440814614938
8 ms 185.136.99.139
24 2026-08-25 08:28 639232430410720425
48 ms 185.136.99.139
23 2026-08-25 08:11 639232420003096185
27 ms 185.136.99.139
22 2026-08-25 07:54 639232409467287444
7 ms 185.136.99.139
21 2026-08-25 07:36 639232399077195997
2036 ms 185.136.99.139
20 2026-08-25 07:19 639232388731528337
18 ms 185.136.99.139
19 2026-08-25 07:02 639232378288598612
6 ms 185.136.99.139
18 2026-08-25 06:08 639232346196373643
3 ms 185.136.99.139
17 2026-08-25 05:51 639232336112370741
15 ms 185.136.99.139
16 2026-08-25 05:35 639232326146508970
9 ms 185.136.99.139
15 2026-08-25 05:18 639232316189381720
53 ms 185.136.99.139
14 2026-08-25 05:01 639232306217998913
2028 ms 185.136.99.139
13 2026-08-25 04:45 639232296255744174
4 ms 185.136.99.139
12 2026-08-25 04:28 639232286095760789
32 ms 185.136.99.139
11 2026-08-25 04:11 639232276086186273
8 ms 185.136.99.139
10 2026-08-25 03:54 639232265900986425
2014 ms 185.136.99.139
9 2026-08-25 03:37 639232255723518075
29 ms 185.136.99.139
8 2026-08-25 03:20 639232245484452890
7 ms 185.136.99.139
7 2026-08-25 03:03 639232235157175331
11 ms 185.136.99.139
6 2026-08-25 02:10 639232203197189095
12 ms 185.136.99.139
5 2026-08-25 01:52 639232192844564298
30 ms 185.136.99.139
4 2026-08-25 01:35 639232182496008942
2016 ms 185.136.99.139
3 2026-08-25 01:18 639232172197053132
12 ms 185.136.99.139
2 2026-08-25 00:25 639232140250307418
2022 ms 185.136.99.139
1 2026-08-25 00:08 639232129927860324
35 ms 185.136.99.139