DNS response history for ns2.bergzand.net

ns2.bergzand.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-24. For this date, NameServerHistory found 32 DNS check records, 31 successful responses, 1 failed responses, and 169 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 ns2.bergzand.net.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

169 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:28

All timestamps shown in UTC

Latest Resolved IP on Selected Date

78.46.117.219

Most recently resolved hosting IP on selected date

Successful Responses

31

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.bergzand.net

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
32 2026-08-24 13:28 639231745628278877
2043 ms 78.46.117.219
31 2026-08-24 13:10 639231735407682062
22 ms 78.46.117.219
30 2026-08-24 12:18 639231703815441688
82 ms 78.46.117.219
29 2026-08-24 12:01 639231693747052549
13 ms 78.46.117.219
28 2026-08-24 11:44 639231683712487276
46 ms 78.46.117.219
27 2026-08-24 11:27 639231673513573868
23 ms 78.46.117.219
26 2026-08-24 10:34 639231641791249939
40 ms 78.46.117.219
25 2026-08-24 10:18 639231631866211033
19 ms 78.46.117.219
24 2026-08-24 10:01 639231621644955316
25 ms 78.46.117.219
23 2026-08-24 09:44 639231611478799259
23 ms 78.46.117.219
22 2026-08-24 08:51 639231579923718211
2067 ms 78.46.117.219
21 2026-08-24 08:35 639231569810702936
25 ms 78.46.117.219
20 2026-08-24 08:18 639231559762411619
54 ms 78.46.117.219
19 2026-08-24 08:01 639231549663595407
31 ms 78.46.117.219
18 2026-08-24 07:08 639231518076817246
82 ms 78.46.117.219
17 2026-08-24 06:52 639231508078650885
38 ms 78.46.117.219
16 2026-08-24 06:35 639231498210697093
53 ms 78.46.117.219
15 2026-08-24 06:18 639231488109699360
9 ms 78.46.117.219
14 2026-08-24 05:26 639231456772510692
50 ms 78.46.117.219
13 2026-08-24 05:10 639231447084631185
55 ms 78.46.117.219
12 2026-08-24 04:53 639231437208519473
75 ms 78.46.117.219
11 2026-08-24 04:37 639231427209627490
15 ms 78.46.117.219
10 2026-08-24 03:44 639231395791246644
-
9 2026-08-24 03:28 639231386075551458
48 ms 78.46.117.219
8 2026-08-24 03:12 639231376208713791
59 ms 78.46.117.219
7 2026-08-24 02:55 639231366170589276
39 ms 78.46.117.219
6 2026-08-24 02:03 639231334732159368
42 ms 78.46.117.219
5 2026-08-24 01:46 639231325035670078
49 ms 78.46.117.219
4 2026-08-24 01:30 639231315132253837
26 ms 78.46.117.219
3 2026-08-24 01:13 639231305014280808
56 ms 78.46.117.219
2 2026-08-24 00:21 639231273779380675
33 ms 78.46.117.219
1 2026-08-24 00:05 639231264180839154
3 ms 78.46.117.219