DNS response history for ns2.termapolis.com.mx

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

37

Historical checks stored for this nameserver on selected date

Average Latency

331 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:12

All timestamps shown in UTC

Latest Resolved IP on Selected Date

132.148.89.105

Most recently resolved hosting IP on selected date

Successful Responses

37

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.termapolis.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
37 2026-08-26 12:12 639233424567558554
475 ms 132.148.89.105
36 2026-08-26 11:55 639233414056832719
726 ms 132.148.89.105
35 2026-08-26 11:37 639233403515141099
314 ms 132.148.89.105
34 2026-08-26 10:43 639233370841350248
625 ms 132.148.89.105
33 2026-08-26 10:26 639233360361507238
325 ms 132.148.89.105
32 2026-08-26 10:08 639233350067824371
455 ms 132.148.89.105
31 2026-08-26 09:51 639233339545274518
310 ms 132.148.89.105
30 2026-08-26 09:33 639233329214918079
312 ms 132.148.89.105
29 2026-08-26 09:16 639233318749762337
793 ms 132.148.89.105
28 2026-08-26 08:59 639233308387917838
315 ms 132.148.89.105
27 2026-08-26 08:42 639233297961740122
2454 ms 132.148.89.105
26 2026-08-26 08:24 639233287487159094
381 ms 132.148.89.105
25 2026-08-26 08:07 639233276995531707
156 ms 132.148.89.105
24 2026-08-26 07:49 639233266521568229
311 ms 132.148.89.105
23 2026-08-26 07:32 639233256081047431
313 ms 132.148.89.105
22 2026-08-26 06:38 639233223620132921
348 ms 132.148.89.105
21 2026-08-26 06:20 639233213287814244
623 ms 132.148.89.105
20 2026-08-26 06:03 639233202925983161
3 ms 132.148.89.105
19 2026-08-26 05:46 639233192644780696
5 ms 132.148.89.105
18 2026-08-26 05:29 639233182401183833
5 ms 132.148.89.105
17 2026-08-26 05:12 639233172074181051
3 ms 132.148.89.105
16 2026-08-26 04:54 639233161808421455
621 ms 132.148.89.105
15 2026-08-26 04:37 639233151357344052
4 ms 132.148.89.105
14 2026-08-26 04:20 639233141034116946
3 ms 132.148.89.105
13 2026-08-26 04:03 639233130828334142
4 ms 132.148.89.105
12 2026-08-26 03:46 639233120373450007
312 ms 132.148.89.105
11 2026-08-26 03:28 639233110066216193
311 ms 132.148.89.105
10 2026-08-26 02:35 639233078065410564
309 ms 132.148.89.105
9 2026-08-26 02:18 639233067787457832
157 ms 132.148.89.105
8 2026-08-26 02:01 639233057501801162
305 ms 132.148.89.105
7 2026-08-26 01:44 639233047089431703
159 ms 132.148.89.105
6 2026-08-26 01:26 639233036754790688
312 ms 132.148.89.105
5 2026-08-26 01:09 639233026412602472
3 ms 132.148.89.105
4 2026-08-26 00:52 639233016064066127
4 ms 132.148.89.105
3 2026-08-26 00:35 639233005922655772
2 ms 132.148.89.105
2 2026-08-26 00:18 639232995672256907
159 ms 132.148.89.105
1 2026-08-26 00:00 639232985300872416
314 ms 132.148.89.105