DNS response history for ns2.alorve.com.mx

ns2.alorve.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 34 DNS check records, 34 successful responses, 0 failed responses, and 413 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.alorve.com.mx.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

413 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

207.210.229.247

Most recently resolved hosting IP on selected date

Successful Responses

34

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.alorve.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
34 2026-08-26 10:44 639233370841350248
329 ms 207.210.229.247
33 2026-08-26 10:27 639233360361507238
285 ms 207.210.229.247
32 2026-08-26 10:09 639233350067824371
141 ms 207.210.229.247
31 2026-08-26 09:52 639233339545274518
568 ms 207.210.229.247
30 2026-08-26 09:35 639233329214918079
4 ms 207.210.229.247
29 2026-08-26 09:17 639233318749762337
10 ms 207.210.229.247
28 2026-08-26 09:00 639233308387917838
618 ms 207.210.229.247
27 2026-08-26 08:43 639233297961740122
571 ms 207.210.229.247
26 2026-08-26 08:25 639233287487159094
260 ms 207.210.229.247
25 2026-08-26 08:08 639233276995531707
4 ms 207.210.229.247
24 2026-08-26 07:50 639233266521568229
630 ms 207.210.229.247
23 2026-08-26 07:33 639233256081047431
300 ms 207.210.229.247
22 2026-08-26 06:39 639233223620132921
3 ms 207.210.229.247
21 2026-08-26 06:21 639233213287814244
542 ms 207.210.229.247
20 2026-08-26 06:04 639233202925983161
2542 ms 207.210.229.247
19 2026-08-26 05:47 639233192644780696
571 ms 207.210.229.247
18 2026-08-26 05:30 639233182401183833
580 ms 207.210.229.247
17 2026-08-26 05:13 639233172074181051
569 ms 207.210.229.247
16 2026-08-26 04:55 639233161808421455
658 ms 207.210.229.247
15 2026-08-26 04:38 639233151357344052
136 ms 207.210.229.247
14 2026-08-26 04:21 639233141034116946
134 ms 207.210.229.247
13 2026-08-26 04:04 639233130828334142
282 ms 207.210.229.247
12 2026-08-26 03:47 639233120373450007
724 ms 207.210.229.247
11 2026-08-26 03:29 639233110066216193
274 ms 207.210.229.247
10 2026-08-26 02:36 639233078065410564
358 ms 207.210.229.247
9 2026-08-26 02:19 639233067787457832
141 ms 207.210.229.247
8 2026-08-26 02:02 639233057501801162
578 ms 207.210.229.247
7 2026-08-26 01:45 639233047089431703
277 ms 207.210.229.247
6 2026-08-26 01:27 639233036754790688
285 ms 207.210.229.247
5 2026-08-26 01:10 639233026412602472
274 ms 207.210.229.247
4 2026-08-26 00:53 639233016064066127
690 ms 207.210.229.247
3 2026-08-26 00:36 639233005922655772
2 ms 207.210.229.247
2 2026-08-26 00:19 639232995672256907
144 ms 207.210.229.247
1 2026-08-26 00:02 639232985300872416
572 ms 207.210.229.247