DNS response history for ns2.terasys.com.mx

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

38

Historical checks stored for this nameserver on selected date

Average Latency

313 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:30

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.81.183.253

Most recently resolved hosting IP on selected date

Successful Responses

38

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.terasys.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
38 2026-08-26 12:30 639233434974187439
355 ms 51.81.183.253
37 2026-08-26 12:12 639233424567558554
353 ms 51.81.183.253
36 2026-08-26 11:55 639233414056832719
162 ms 51.81.183.253
35 2026-08-26 11:37 639233403515141099
344 ms 51.81.183.253
34 2026-08-26 10:43 639233370841350248
168 ms 51.81.183.253
33 2026-08-26 10:25 639233360361507238
2189 ms 51.81.183.253
32 2026-08-26 10:08 639233350067824371
170 ms 51.81.183.253
31 2026-08-26 09:51 639233339545274518
356 ms 51.81.183.253
30 2026-08-26 09:33 639233329214918079
371 ms 51.81.183.253
29 2026-08-26 09:16 639233318749762337
224 ms 51.81.183.253
28 2026-08-26 08:59 639233308387917838
177 ms 51.81.183.253
27 2026-08-26 08:41 639233297961740122
410 ms 51.81.183.253
26 2026-08-26 08:24 639233287487159094
4 ms 51.81.183.253
25 2026-08-26 08:07 639233276995531707
360 ms 51.81.183.253
24 2026-08-26 07:49 639233266521568229
344 ms 51.81.183.253
23 2026-08-26 07:31 639233256081047431
334 ms 51.81.183.253
22 2026-08-26 06:38 639233223620132921
462 ms 51.81.183.253
21 2026-08-26 06:20 639233213287814244
356 ms 51.81.183.253
20 2026-08-26 06:03 639233202925983161
337 ms 51.81.183.253
19 2026-08-26 05:46 639233192644780696
336 ms 51.81.183.253
18 2026-08-26 05:28 639233182401183833
328 ms 51.81.183.253
17 2026-08-26 05:11 639233172074181051
352 ms 51.81.183.253
16 2026-08-26 04:54 639233161808421455
477 ms 51.81.183.253
15 2026-08-26 04:37 639233151357344052
163 ms 51.81.183.253
14 2026-08-26 04:20 639233141034116946
165 ms 51.81.183.253
13 2026-08-26 04:03 639233130828334142
348 ms 51.81.183.253
12 2026-08-26 03:45 639233120373450007
350 ms 51.81.183.253
11 2026-08-26 03:28 639233110066216193
336 ms 51.81.183.253
10 2026-08-26 02:35 639233078065410564
340 ms 51.81.183.253
9 2026-08-26 02:18 639233067787457832
3 ms 51.81.183.253
8 2026-08-26 02:00 639233057501801162
177 ms 51.81.183.253
7 2026-08-26 01:43 639233047089431703
164 ms 51.81.183.253
6 2026-08-26 01:26 639233036754790688
178 ms 51.81.183.253
5 2026-08-26 01:09 639233026412602472
3 ms 51.81.183.253
4 2026-08-26 00:51 639233016064066127
3 ms 51.81.183.253
3 2026-08-26 00:34 639233005922655772
3 ms 51.81.183.253
2 2026-08-26 00:17 639232995672256907
349 ms 51.81.183.253
1 2026-08-26 00:00 639232985300872416
337 ms 51.81.183.253