DNS response history for drie.nieuwedagnetwerk.net

drie.nieuwedagnetwerk.net 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 448 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 drie.nieuwedagnetwerk.net.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

448 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.98.111

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 drie.nieuwedagnetwerk.net

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
49 ms 185.136.98.111
28 2026-08-25 09:37 639232471861770303
82 ms 185.136.98.111
27 2026-08-25 09:20 639232461630217327
12 ms 185.136.98.111
26 2026-08-25 09:03 639232451282965990
28 ms 185.136.98.111
25 2026-08-25 08:45 639232440814614938
20 ms 185.136.98.111
24 2026-08-25 08:28 639232430410720425
22 ms 185.136.98.111
23 2026-08-25 08:11 639232420003096185
11 ms 185.136.98.111
22 2026-08-25 07:53 639232409467287444
23 ms 185.136.98.111
21 2026-08-25 07:36 639232399077195997
8 ms 185.136.98.111
20 2026-08-25 07:19 639232388731528337
36 ms 185.136.98.111
19 2026-08-25 07:01 639232378288598612
37 ms 185.136.98.111
18 2026-08-25 06:08 639232346196373643
9 ms 185.136.98.111
17 2026-08-25 05:51 639232336112370741
40 ms 185.136.98.111
16 2026-08-25 05:34 639232326146508970
103 ms 185.136.98.111
15 2026-08-25 05:18 639232316189381720
87 ms 185.136.98.111
14 2026-08-25 05:01 639232306217998913
37 ms 185.136.98.111
13 2026-08-25 04:45 639232296255744174
2023 ms 185.136.98.111
12 2026-08-25 04:28 639232286095760789
10 ms 185.136.98.111
11 2026-08-25 04:11 639232276086186273
2028 ms 185.136.98.111
10 2026-08-25 03:54 639232265900986425
3 ms 185.136.98.111
9 2026-08-25 03:37 639232255723518075
11 ms 185.136.98.111
8 2026-08-25 03:20 639232245484452890
70 ms 185.136.98.111
7 2026-08-25 03:03 639232235157175331
2058 ms 185.136.98.111
6 2026-08-25 02:09 639232203197189095
2019 ms 185.136.98.111
5 2026-08-25 01:52 639232192844564298
34 ms 185.136.98.111
4 2026-08-25 01:35 639232182496008942
8 ms 185.136.98.111
3 2026-08-25 01:18 639232172197053132
2043 ms 185.136.98.111
2 2026-08-25 00:24 639232140250307418
2026 ms 185.136.98.111
1 2026-08-25 00:07 639232129927860324
57 ms 185.136.98.111