DNS response history for ns2.hondamiramontes.com.mx

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

33

Historical checks stored for this nameserver on selected date

Average Latency

365 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

23.29.116.173

Most recently resolved hosting IP on selected date

Successful Responses

33

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.hondamiramontes.com.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
33 2026-08-25 11:47 639232545839529039
139 ms 23.29.116.173
32 2026-08-25 11:29 639232535349285207
126 ms 23.29.116.173
31 2026-08-25 11:12 639232524938080723
248 ms 23.29.116.173
30 2026-08-25 10:18 639232492740373468
118 ms 23.29.116.173
29 2026-08-25 10:01 639232482235303141
140 ms 23.29.116.173
28 2026-08-25 09:44 639232471861770303
185 ms 23.29.116.173
27 2026-08-25 09:26 639232461630217327
125 ms 23.29.116.173
26 2026-08-25 09:09 639232451282965990
245 ms 23.29.116.173
25 2026-08-25 08:52 639232440814614938
242 ms 23.29.116.173
24 2026-08-25 08:34 639232430410720425
244 ms 23.29.116.173
23 2026-08-25 08:17 639232420003096185
244 ms 23.29.116.173
22 2026-08-25 08:00 639232409467287444
243 ms 23.29.116.173
21 2026-08-25 07:42 639232399077195997
236 ms 23.29.116.173
20 2026-08-25 07:25 639232388731528337
238 ms 23.29.116.173
19 2026-08-25 07:08 639232378288598612
235 ms 23.29.116.173
18 2026-08-25 06:14 639232346196373643
250 ms 23.29.116.173
17 2026-08-25 05:57 639232336112370741
2415 ms 23.29.116.173
16 2026-08-25 05:41 639232326146508970
26 ms 23.29.116.173
15 2026-08-25 05:24 639232316189381720
9 ms 23.29.116.173
14 2026-08-25 05:07 639232306217998913
126 ms 23.29.116.173
13 2026-08-25 04:51 639232296255744174
2476 ms 23.29.116.173
12 2026-08-25 04:34 639232286095760789
3 ms 23.29.116.173
11 2026-08-25 04:17 639232276086186273
2 ms 23.29.116.173
10 2026-08-25 04:00 639232265900986425
2007 ms 23.29.116.173
9 2026-08-25 03:43 639232255723518075
247 ms 23.29.116.173
8 2026-08-25 03:26 639232245484452890
238 ms 23.29.116.173
7 2026-08-25 03:09 639232235157175331
267 ms 23.29.116.173
6 2026-08-25 02:16 639232203197189095
245 ms 23.29.116.173
5 2026-08-25 01:59 639232192844564298
237 ms 23.29.116.173
4 2026-08-25 01:41 639232182496008942
7 ms 23.29.116.173
3 2026-08-25 01:24 639232172197053132
246 ms 23.29.116.173
2 2026-08-25 00:31 639232140250307418
10 ms 23.29.116.173
1 2026-08-25 00:14 639232129927860324
240 ms 23.29.116.173