DNS response history for ns1.cepe.com.mx

ns1.cepe.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 28 DNS check records, 28 successful responses, 0 failed responses, and 248 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.cepe.com.mx.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

248 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

65.99.252.245

Most recently resolved hosting IP on selected date

Successful Responses

28

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.cepe.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
28 2026-08-26 08:59 639233308387917838
286 ms 65.99.252.245
27 2026-08-26 08:42 639233297961740122
291 ms 65.99.252.245
26 2026-08-26 08:24 639233287487159094
136 ms 65.99.252.245
25 2026-08-26 08:07 639233276995531707
135 ms 65.99.252.245
24 2026-08-26 07:49 639233266521568229
292 ms 65.99.252.245
23 2026-08-26 07:32 639233256081047431
142 ms 65.99.252.245
22 2026-08-26 06:38 639233223620132921
148 ms 65.99.252.245
21 2026-08-26 06:20 639233213287814244
274 ms 65.99.252.245
20 2026-08-26 06:03 639233202925983161
140 ms 65.99.252.245
19 2026-08-26 05:46 639233192644780696
269 ms 65.99.252.245
18 2026-08-26 05:29 639233182401183833
283 ms 65.99.252.245
17 2026-08-26 05:12 639233172074181051
139 ms 65.99.252.245
16 2026-08-26 04:55 639233161808421455
148 ms 65.99.252.245
15 2026-08-26 04:37 639233151357344052
141 ms 65.99.252.245
14 2026-08-26 04:20 639233141034116946
274 ms 65.99.252.245
13 2026-08-26 04:03 639233130828334142
141 ms 65.99.252.245
12 2026-08-26 03:46 639233120373450007
272 ms 65.99.252.245
11 2026-08-26 03:28 639233110066216193
138 ms 65.99.252.245
10 2026-08-26 02:35 639233078065410564
142 ms 65.99.252.245
9 2026-08-26 02:18 639233067787457832
279 ms 65.99.252.245
8 2026-08-26 02:01 639233057501801162
133 ms 65.99.252.245
7 2026-08-26 01:44 639233047089431703
295 ms 65.99.252.245
6 2026-08-26 01:26 639233036754790688
293 ms 65.99.252.245
5 2026-08-26 01:09 639233026412602472
144 ms 65.99.252.245
4 2026-08-26 00:52 639233016064066127
287 ms 65.99.252.245
3 2026-08-26 00:35 639233005922655772
286 ms 65.99.252.245
2 2026-08-26 00:18 639232995672256907
1134 ms 65.99.252.245
1 2026-08-26 00:01 639232985300872416
288 ms 65.99.252.245