DNS response history for ns1.elota.gob.mx

ns1.elota.gob.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 54 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 ns1.elota.gob.mx.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

54 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.240.170.116

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 ns1.elota.gob.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 11:59 639233414056832719
279 ms 162.240.170.116
35 2026-08-26 11:41 639233403515141099
21 ms 162.240.170.116
34 2026-08-26 10:47 639233370841350248
156 ms 162.240.170.116
33 2026-08-26 10:29 639233360361507238
4 ms 162.240.170.116
32 2026-08-26 10:12 639233350067824371
3 ms 162.240.170.116
31 2026-08-26 09:55 639233339545274518
15 ms 162.240.170.116
30 2026-08-26 09:37 639233329214918079
18 ms 162.240.170.116
29 2026-08-26 09:20 639233318749762337
30 ms 162.240.170.116
28 2026-08-26 09:03 639233308387917838
29 ms 162.240.170.116
27 2026-08-26 08:45 639233297961740122
50 ms 162.240.170.116
26 2026-08-26 08:28 639233287487159094
21 ms 162.240.170.116
25 2026-08-26 08:10 639233276995531707
15 ms 162.240.170.116
24 2026-08-26 07:53 639233266521568229
27 ms 162.240.170.116
23 2026-08-26 07:35 639233256081047431
34 ms 162.240.170.116
22 2026-08-26 06:41 639233223620132921
30 ms 162.240.170.116
21 2026-08-26 06:24 639233213287814244
19 ms 162.240.170.116
20 2026-08-26 06:07 639233202925983161
22 ms 162.240.170.116
19 2026-08-26 05:50 639233192644780696
19 ms 162.240.170.116
18 2026-08-26 05:32 639233182401183833
300 ms 162.240.170.116
17 2026-08-26 05:15 639233172074181051
15 ms 162.240.170.116
16 2026-08-26 04:58 639233161808421455
27 ms 162.240.170.116
15 2026-08-26 04:41 639233151357344052
285 ms 162.240.170.116
14 2026-08-26 04:24 639233141034116946
13 ms 162.240.170.116
13 2026-08-26 04:06 639233130828334142
13 ms 162.240.170.116
12 2026-08-26 03:49 639233120373450007
23 ms 162.240.170.116
11 2026-08-26 03:32 639233110066216193
176 ms 162.240.170.116
10 2026-08-26 02:39 639233078065410564
156 ms 162.240.170.116
9 2026-08-26 02:22 639233067787457832
22 ms 162.240.170.116
8 2026-08-26 02:04 639233057501801162
4 ms 162.240.170.116
7 2026-08-26 01:47 639233047089431703
14 ms 162.240.170.116
6 2026-08-26 01:30 639233036754790688
16 ms 162.240.170.116
5 2026-08-26 01:13 639233026412602472
24 ms 162.240.170.116
4 2026-08-26 00:55 639233016064066127
24 ms 162.240.170.116
3 2026-08-26 00:38 639233005922655772
26 ms 162.240.170.116
2 2026-08-26 00:21 639232995672256907
13 ms 162.240.170.116
1 2026-08-26 00:04 639232985300872416
5 ms 162.240.170.116