DNS response history for ns-do-ams2.valid.be

ns-do-ams2.valid.be 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 118 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 ns-do-ams2.valid.be.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

118 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

95.85.25.61

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 ns-do-ams2.valid.be

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:15 639231703815441688
294 ms 95.85.25.61
29 2026-08-24 11:58 639231693747052549
24 ms 95.85.25.61
28 2026-08-24 11:41 639231683712487276
2043 ms 95.85.25.61
27 2026-08-24 11:24 639231673513573868
64 ms 95.85.25.61
26 2026-08-24 10:31 639231641791249939
8 ms 95.85.25.61
25 2026-08-24 10:15 639231631866211033
44 ms 95.85.25.61
24 2026-08-24 09:58 639231621644955316
89 ms 95.85.25.61
23 2026-08-24 09:41 639231611478799259
41 ms 95.85.25.61
22 2026-08-24 08:49 639231579923718211
58 ms 95.85.25.61
21 2026-08-24 08:32 639231569810702936
56 ms 95.85.25.61
20 2026-08-24 08:15 639231559762411619
53 ms 95.85.25.61
19 2026-08-24 07:58 639231549663595407
58 ms 95.85.25.61
18 2026-08-24 07:05 639231518076817246
44 ms 95.85.25.61
17 2026-08-24 06:49 639231508078650885
52 ms 95.85.25.61
16 2026-08-24 06:32 639231498210697093
20 ms 95.85.25.61
15 2026-08-24 06:16 639231488109699360
48 ms 95.85.25.61
14 2026-08-24 05:23 639231456772510692
13 ms 95.85.25.61
13 2026-08-24 05:07 639231447084631185
7 ms 95.85.25.61
12 2026-08-24 04:51 639231437208519473
44 ms 95.85.25.61
11 2026-08-24 04:34 639231427209627490
43 ms 95.85.25.61
10 2026-08-24 03:42 639231395791246644
81 ms 95.85.25.61
9 2026-08-24 03:25 639231386075551458
37 ms 95.85.25.61
8 2026-08-24 03:09 639231376208713791
64 ms 95.85.25.61
7 2026-08-24 02:52 639231366170589276
3 ms 95.85.25.61
6 2026-08-24 02:00 639231334732159368
37 ms 95.85.25.61
5 2026-08-24 01:44 639231325035670078
45 ms 95.85.25.61
4 2026-08-24 01:27 639231315132253837
8 ms 95.85.25.61
3 2026-08-24 01:10 639231305014280808
68 ms 95.85.25.61
2 2026-08-24 00:18 639231273779380675
16 ms 95.85.25.61
1 2026-08-24 00:02 639231264180839154
64 ms 95.85.25.61