DNS response history for ns2.tresesenta.mx

ns2.tresesenta.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-25. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 424 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.tresesenta.mx.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

424 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

15.235.42.59

Most recently resolved hosting IP on selected date

Successful Responses

31

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.tresesenta.mx

Showing DNS history for 2026-08-25 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
31 2026-08-25 11:10 639232524938080723
9 ms 15.235.42.59
30 2026-08-25 10:16 639232492740373468
113 ms 15.235.42.59
29 2026-08-25 09:59 639232482235303141
2032 ms 15.235.42.59
28 2026-08-25 09:41 639232471861770303
38 ms 15.235.42.59
27 2026-08-25 09:24 639232461630217327
270 ms 15.235.42.59
26 2026-08-25 09:07 639232451282965990
217 ms 15.235.42.59
25 2026-08-25 08:50 639232440814614938
17 ms 15.235.42.59
24 2026-08-25 08:32 639232430410720425
115 ms 15.235.42.59
23 2026-08-25 08:15 639232420003096185
2233 ms 15.235.42.59
22 2026-08-25 07:58 639232409467287444
217 ms 15.235.42.59
21 2026-08-25 07:40 639232399077195997
366 ms 15.235.42.59
20 2026-08-25 07:23 639232388731528337
214 ms 15.235.42.59
19 2026-08-25 07:06 639232378288598612
8 ms 15.235.42.59
18 2026-08-25 06:12 639232346196373643
3 ms 15.235.42.59
17 2026-08-25 05:55 639232336112370741
4 ms 15.235.42.59
16 2026-08-25 05:39 639232326146508970
4 ms 15.235.42.59
15 2026-08-25 05:22 639232316189381720
3 ms 15.235.42.59
14 2026-08-25 05:05 639232306217998913
108 ms 15.235.42.59
13 2026-08-25 04:49 639232296255744174
448 ms 15.235.42.59
12 2026-08-25 04:32 639232286095760789
485 ms 15.235.42.59
11 2026-08-25 04:15 639232276086186273
222 ms 15.235.42.59
10 2026-08-25 03:58 639232265900986425
222 ms 15.235.42.59
9 2026-08-25 03:41 639232255723518075
107 ms 15.235.42.59
8 2026-08-25 03:24 639232245484452890
2216 ms 15.235.42.59
7 2026-08-25 03:07 639232235157175331
363 ms 15.235.42.59
6 2026-08-25 02:14 639232203197189095
30 ms 15.235.42.59
5 2026-08-25 01:57 639232192844564298
382 ms 15.235.42.59
4 2026-08-25 01:39 639232182496008942
219 ms 15.235.42.59
3 2026-08-25 01:22 639232172197053132
110 ms 15.235.42.59
2 2026-08-25 00:29 639232140250307418
219 ms 15.235.42.59
1 2026-08-25 00:12 639232129927860324
2149 ms 15.235.42.59