DNS response history for ns2.overcode.com.mx

ns2.overcode.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 452 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.overcode.com.mx.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

452 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

108.179.194.32

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.overcode.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
309 ms 108.179.194.32
33 2026-08-26 10:27 639233360361507238
765 ms 108.179.194.32
32 2026-08-26 10:10 639233350067824371
759 ms 108.179.194.32
31 2026-08-26 09:53 639233339545274518
893 ms 108.179.194.32
30 2026-08-26 09:35 639233329214918079
179 ms 108.179.194.32
29 2026-08-26 09:18 639233318749762337
197 ms 108.179.194.32
28 2026-08-26 09:00 639233308387917838
315 ms 108.179.194.32
27 2026-08-26 08:43 639233297961740122
311 ms 108.179.194.32
26 2026-08-26 08:26 639233287487159094
310 ms 108.179.194.32
25 2026-08-26 08:08 639233276995531707
753 ms 108.179.194.32
24 2026-08-26 07:51 639233266521568229
760 ms 108.179.194.32
23 2026-08-26 07:33 639233256081047431
305 ms 108.179.194.32
22 2026-08-26 06:39 639233223620132921
306 ms 108.179.194.32
21 2026-08-26 06:22 639233213287814244
306 ms 108.179.194.32
20 2026-08-26 06:05 639233202925983161
309 ms 108.179.194.32
19 2026-08-26 05:47 639233192644780696
302 ms 108.179.194.32
18 2026-08-26 05:30 639233182401183833
434 ms 108.179.194.32
17 2026-08-26 05:13 639233172074181051
740 ms 108.179.194.32
16 2026-08-26 04:56 639233161808421455
307 ms 108.179.194.32
15 2026-08-26 04:39 639233151357344052
743 ms 108.179.194.32
14 2026-08-26 04:21 639233141034116946
311 ms 108.179.194.32
13 2026-08-26 04:04 639233130828334142
309 ms 108.179.194.32
12 2026-08-26 03:47 639233120373450007
755 ms 108.179.194.32
11 2026-08-26 03:30 639233110066216193
450 ms 108.179.194.32
10 2026-08-26 02:36 639233078065410564
309 ms 108.179.194.32
9 2026-08-26 02:19 639233067787457832
752 ms 108.179.194.32
8 2026-08-26 02:02 639233057501801162
306 ms 108.179.194.32
7 2026-08-26 01:45 639233047089431703
154 ms 108.179.194.32
6 2026-08-26 01:28 639233036754790688
282 ms 108.179.194.32
5 2026-08-26 01:10 639233026412602472
312 ms 108.179.194.32
4 2026-08-26 00:53 639233016064066127
752 ms 108.179.194.32
3 2026-08-26 00:36 639233005922655772
310 ms 108.179.194.32
2 2026-08-26 00:19 639232995672256907
308 ms 108.179.194.32
1 2026-08-26 00:02 639232985300872416
757 ms 108.179.194.32