DNS response history for ns2.zalvis.com

ns2.zalvis.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-24. For this date, NameServerHistory found 40 DNS check records, 38 successful responses, 2 failed responses, and 242 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.zalvis.com.
Records on Selected Date

40

Historical checks stored for this nameserver on selected date

Average Latency

242 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 16:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

78.46.134.125

Most recently resolved hosting IP on selected date

Successful Responses

38

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

5%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.zalvis.com

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
40 2026-08-24 16:51 639231870418029045
42 ms 78.46.134.125
39 2026-08-24 16:34 639231860258429562
19 ms 78.46.134.125
38 2026-08-24 15:41 639231828211839931
12 ms 78.46.134.125
37 2026-08-24 15:24 639231818080917481
8 ms 78.46.134.125
36 2026-08-24 15:07 639231807961539652
48 ms 78.46.134.125
35 2026-08-24 14:50 639231797631669865
22 ms 78.46.134.125
34 2026-08-24 13:57 639231765923559455
38 ms 78.46.134.125
33 2026-08-24 13:40 639231755868832964
4029 ms 78.46.134.125
32 2026-08-24 13:23 639231745628278877
15 ms 78.46.134.125
31 2026-08-24 13:06 639231735407682062
31 ms 78.46.134.125
30 2026-08-24 12:14 639231703815441688
43 ms 78.46.134.125
29 2026-08-24 11:57 639231693747052549
49 ms 78.46.134.125
28 2026-08-24 11:40 639231683712487276
2043 ms 78.46.134.125
27 2026-08-24 11:23 639231673513573868
46 ms 78.46.134.125
26 2026-08-24 10:30 639231641791249939
16 ms 78.46.134.125
25 2026-08-24 10:14 639231631866211033
10 ms 78.46.134.125
24 2026-08-24 09:57 639231621644955316
25 ms 78.46.134.125
23 2026-08-24 09:40 639231611478799259
19 ms 78.46.134.125
22 2026-08-24 08:47 639231579923718211
14 ms 78.46.134.125
21 2026-08-24 08:30 639231569810702936
15 ms 78.46.134.125
20 2026-08-24 08:13 639231559762411619
13 ms 78.46.134.125
19 2026-08-24 07:57 639231549663595407
36 ms 78.46.134.125
18 2026-08-24 07:04 639231518076817246
2204 ms 78.46.134.125
17 2026-08-24 06:47 639231508078650885
-
16 2026-08-24 06:31 639231498210697093
31 ms 78.46.134.125
15 2026-08-24 06:14 639231488109699360
11 ms 78.46.134.125
14 2026-08-24 05:22 639231456772510692
55 ms 78.46.134.125
13 2026-08-24 05:06 639231447084631185
98 ms 78.46.134.125
12 2026-08-24 04:49 639231437208519473
32 ms 78.46.134.125
11 2026-08-24 04:33 639231427209627490
-
10 2026-08-24 03:40 639231395791246644
10 ms 78.46.134.125
9 2026-08-24 03:24 639231386075551458
7 ms 78.46.134.125
8 2026-08-24 03:08 639231376208713791
9 ms 78.46.134.125
7 2026-08-24 02:51 639231366170589276
56 ms 78.46.134.125
6 2026-08-24 01:58 639231334732159368
9 ms 78.46.134.125
5 2026-08-24 01:42 639231325035670078
6 ms 78.46.134.125
4 2026-08-24 01:26 639231315132253837
10 ms 78.46.134.125
3 2026-08-24 01:09 639231305014280808
7 ms 78.46.134.125
2 2026-08-24 00:17 639231273779380675
39 ms 78.46.134.125
1 2026-08-24 00:01 639231264180839154
4 ms 78.46.134.125