DNS response history for ns2.server.travelviajes.com.mx

ns2.server.travelviajes.com.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-26. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 622 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.server.travelviajes.com.mx.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

622 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.6.230.42

Most recently resolved hosting IP on selected date

Successful Responses

36

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.server.travelviajes.com.mx

Showing DNS history for 2026-08-26 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
36 2026-08-26 12:10 639233424567558554
197 ms 50.6.230.42
35 2026-08-26 11:53 639233414056832719
10 ms 50.6.230.42
34 2026-08-26 11:35 639233403515141099
296 ms 50.6.230.42
33 2026-08-26 10:41 639233370841350248
196 ms 50.6.230.42
32 2026-08-26 10:23 639233360361507238
291 ms 50.6.230.42
31 2026-08-26 10:06 639233350067824371
32 ms 50.6.230.42
30 2026-08-26 09:49 639233339545274518
305 ms 50.6.230.42
29 2026-08-26 09:31 639233329214918079
427 ms 50.6.230.42
28 2026-08-26 09:14 639233318749762337
437 ms 50.6.230.42
27 2026-08-26 08:57 639233308387917838
292 ms 50.6.230.42
26 2026-08-26 08:39 639233297961740122
8 ms 50.6.230.42
25 2026-08-26 08:22 639233287487159094
429 ms 50.6.230.42
24 2026-08-26 08:05 639233276995531707
2100 ms 50.6.230.42
23 2026-08-26 07:47 639233266521568229
2504 ms 50.6.230.42
22 2026-08-26 07:29 639233256081047431
7 ms 50.6.230.42
21 2026-08-26 06:36 639233223620132921
2264 ms 50.6.230.42
20 2026-08-26 06:18 639233213287814244
293 ms 50.6.230.42
19 2026-08-26 06:01 639233202925983161
5 ms 50.6.230.42
18 2026-08-26 05:44 639233192644780696
294 ms 50.6.230.42
17 2026-08-26 05:27 639233182401183833
427 ms 50.6.230.42
16 2026-08-26 05:10 639233172074181051
338 ms 50.6.230.42
15 2026-08-26 04:52 639233161808421455
292 ms 50.6.230.42
14 2026-08-26 04:35 639233151357344052
2520 ms 50.6.230.42
13 2026-08-26 04:18 639233141034116946
290 ms 50.6.230.42
12 2026-08-26 04:01 639233130828334142
325 ms 50.6.230.42
11 2026-08-26 03:44 639233120373450007
4332 ms 50.6.230.42
10 2026-08-26 03:26 639233110066216193
97 ms 50.6.230.42
9 2026-08-26 02:33 639233078065410564
214 ms 50.6.230.42
8 2026-08-26 02:16 639233067787457832
234 ms 50.6.230.42
7 2026-08-26 01:59 639233057501801162
202 ms 50.6.230.42
6 2026-08-26 01:41 639233047089431703
105 ms 50.6.230.42
5 2026-08-26 01:24 639233036754790688
302 ms 50.6.230.42
4 2026-08-26 01:07 639233026412602472
2008 ms 50.6.230.42
3 2026-08-26 00:49 639233016064066127
8 ms 50.6.230.42
2 2026-08-26 00:32 639233005922655772
9 ms 50.6.230.42
1 2026-08-26 00:15 639232995672256907
296 ms 50.6.230.42