DNS response history for ns2.xvedio.fun

ns2.xvedio.fun 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 38 DNS check records, 37 successful responses, 1 failed responses, and 264 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.xvedio.fun.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

264 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

109.206.175.133

Most recently resolved hosting IP on selected date

Successful Responses

37

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.xvedio.fun

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
38 2026-08-24 15:44 639231828211839931
50 ms 109.206.175.133
37 2026-08-24 15:27 639231818080917481
51 ms 109.206.175.133
36 2026-08-24 15:10 639231807961539652
75 ms 109.206.175.133
35 2026-08-24 14:53 639231797631669865
31 ms 109.206.175.133
34 2026-08-24 14:00 639231765923559455
18 ms 109.206.175.133
33 2026-08-24 13:43 639231755868832964
21 ms 109.206.175.133
32 2026-08-24 13:26 639231745628278877
4 ms 109.206.175.133
31 2026-08-24 13:09 639231735407682062
44 ms 109.206.175.133
30 2026-08-24 12:17 639231703815441688
42 ms 109.206.175.133
29 2026-08-24 12:00 639231693747052549
67 ms 109.206.175.133
28 2026-08-24 11:43 639231683712487276
46 ms 109.206.175.133
27 2026-08-24 11:26 639231673513573868
153 ms 109.206.175.133
26 2026-08-24 10:33 639231641791249939
40 ms 109.206.175.133
25 2026-08-24 10:17 639231631866211033
88 ms 109.206.175.133
24 2026-08-24 10:00 639231621644955316
2052 ms 109.206.175.133
23 2026-08-24 09:43 639231611478799259
2021 ms 109.206.175.133
22 2026-08-24 08:50 639231579923718211
10 ms 109.206.175.133
21 2026-08-24 08:33 639231569810702936
83 ms 109.206.175.133
20 2026-08-24 08:16 639231559762411619
117 ms 109.206.175.133
19 2026-08-24 08:00 639231549663595407
51 ms 109.206.175.133
18 2026-08-24 07:07 639231518076817246
19 ms 109.206.175.133
17 2026-08-24 06:51 639231508078650885
57 ms 109.206.175.133
16 2026-08-24 06:34 639231498210697093
40 ms 109.206.175.133
15 2026-08-24 06:17 639231488109699360
2071 ms 109.206.175.133
14 2026-08-24 05:25 639231456772510692
9 ms 109.206.175.133
13 2026-08-24 05:09 639231447084631185
16 ms 109.206.175.133
12 2026-08-24 04:52 639231437208519473
73 ms 109.206.175.133
11 2026-08-24 04:36 639231427209627490
-
10 2026-08-24 03:43 639231395791246644
38 ms 109.206.175.133
9 2026-08-24 03:27 639231386075551458
28 ms 109.206.175.133
8 2026-08-24 03:11 639231376208713791
47 ms 109.206.175.133
7 2026-08-24 02:54 639231366170589276
2046 ms 109.206.175.133
6 2026-08-24 02:02 639231334732159368
45 ms 109.206.175.133
5 2026-08-24 01:45 639231325035670078
39 ms 109.206.175.133
4 2026-08-24 01:29 639231315132253837
37 ms 109.206.175.133
3 2026-08-24 01:12 639231305014280808
74 ms 109.206.175.133
2 2026-08-24 00:20 639231273779380675
21 ms 109.206.175.133
1 2026-08-24 00:04 639231264180839154
60 ms 109.206.175.133