DNS response history for ns2.nextvision.mx

ns2.nextvision.mx 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, 38 successful responses, 0 failed responses, and 310 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.nextvision.mx.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

310 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:48

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.10.39.131

Most recently resolved hosting IP on selected date

Successful Responses

38

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 ns2.nextvision.mx

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:48 639231828211839931
97 ms 69.10.39.131
37 2026-08-24 15:31 639231818080917481
149 ms 69.10.39.131
36 2026-08-24 15:14 639231807961539652
186 ms 69.10.39.131
35 2026-08-24 14:57 639231797631669865
97 ms 69.10.39.131
34 2026-08-24 14:04 639231765923559455
100 ms 69.10.39.131
33 2026-08-24 13:48 639231755868832964
120 ms 69.10.39.131
32 2026-08-24 13:31 639231745628278877
95 ms 69.10.39.131
31 2026-08-24 13:13 639231735407682062
98 ms 69.10.39.131
30 2026-08-24 12:21 639231703815441688
97 ms 69.10.39.131
29 2026-08-24 12:04 639231693747052549
204 ms 69.10.39.131
28 2026-08-24 11:47 639231683712487276
98 ms 69.10.39.131
27 2026-08-24 11:30 639231673513573868
190 ms 69.10.39.131
26 2026-08-24 10:37 639231641791249939
489 ms 69.10.39.131
25 2026-08-24 10:21 639231631866211033
2244 ms 69.10.39.131
24 2026-08-24 10:04 639231621644955316
95 ms 69.10.39.131
23 2026-08-24 09:47 639231611478799259
201 ms 69.10.39.131
22 2026-08-24 08:54 639231579923718211
364 ms 69.10.39.131
21 2026-08-24 08:38 639231569810702936
17 ms 69.10.39.131
20 2026-08-24 08:21 639231559762411619
95 ms 69.10.39.131
19 2026-08-24 08:04 639231549663595407
94 ms 69.10.39.131
18 2026-08-24 07:11 639231518076817246
97 ms 69.10.39.131
17 2026-08-24 06:55 639231508078650885
114 ms 69.10.39.131
16 2026-08-24 06:38 639231498210697093
2253 ms 69.10.39.131
15 2026-08-24 06:22 639231488109699360
94 ms 69.10.39.131
14 2026-08-24 05:29 639231456772510692
15 ms 69.10.39.131
13 2026-08-24 05:13 639231447084631185
2172 ms 69.10.39.131
12 2026-08-24 04:57 639231437208519473
23 ms 69.10.39.131
11 2026-08-24 04:40 639231427209627490
94 ms 69.10.39.131
10 2026-08-24 03:47 639231395791246644
364 ms 69.10.39.131
9 2026-08-24 03:31 639231386075551458
186 ms 69.10.39.131
8 2026-08-24 03:15 639231376208713791
227 ms 69.10.39.131
7 2026-08-24 02:58 639231366170589276
15 ms 69.10.39.131
6 2026-08-24 02:06 639231334732159368
96 ms 69.10.39.131
5 2026-08-24 01:50 639231325035670078
377 ms 69.10.39.131
4 2026-08-24 01:33 639231315132253837
11 ms 69.10.39.131
3 2026-08-24 01:16 639231305014280808
94 ms 69.10.39.131
2 2026-08-24 00:24 639231273779380675
3 ms 69.10.39.131
1 2026-08-24 00:08 639231264180839154
398 ms 69.10.39.131