DNS response history for hopper2.itam.mx

hopper2.itam.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 28 DNS check records, 28 successful responses, 0 failed responses, and 242 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 hopper2.itam.mx.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

242 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

148.205.104.102

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 hopper2.itam.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
28 2026-08-25 09:44 639232471861770303
160 ms 148.205.104.102
27 2026-08-25 09:27 639232461630217327
163 ms 148.205.104.102
26 2026-08-25 09:09 639232451282965990
163 ms 148.205.104.102
25 2026-08-25 08:52 639232440814614938
168 ms 148.205.104.102
24 2026-08-25 08:35 639232430410720425
163 ms 148.205.104.102
23 2026-08-25 08:17 639232420003096185
15 ms 148.205.104.102
22 2026-08-25 08:00 639232409467287444
166 ms 148.205.104.102
21 2026-08-25 07:42 639232399077195997
227 ms 148.205.104.102
20 2026-08-25 07:25 639232388731528337
166 ms 148.205.104.102
19 2026-08-25 07:08 639232378288598612
324 ms 148.205.104.102
18 2026-08-25 06:14 639232346196373643
292 ms 148.205.104.102
17 2026-08-25 05:57 639232336112370741
165 ms 148.205.104.102
16 2026-08-25 05:41 639232326146508970
346 ms 148.205.104.102
15 2026-08-25 05:24 639232316189381720
164 ms 148.205.104.102
14 2026-08-25 05:07 639232306217998913
2 ms 148.205.104.102
13 2026-08-25 04:51 639232296255744174
164 ms 148.205.104.102
12 2026-08-25 04:34 639232286095760789
2 ms 148.205.104.102
11 2026-08-25 04:17 639232276086186273
158 ms 148.205.104.102
10 2026-08-25 04:00 639232265900986425
321 ms 148.205.104.102
9 2026-08-25 03:43 639232255723518075
2155 ms 148.205.104.102
8 2026-08-25 03:26 639232245484452890
165 ms 148.205.104.102
7 2026-08-25 03:09 639232235157175331
2 ms 148.205.104.102
6 2026-08-25 02:16 639232203197189095
316 ms 148.205.104.102
5 2026-08-25 01:59 639232192844564298
160 ms 148.205.104.102
4 2026-08-25 01:41 639232182496008942
159 ms 148.205.104.102
3 2026-08-25 01:24 639232172197053132
164 ms 148.205.104.102
2 2026-08-25 00:31 639232140250307418
158 ms 148.205.104.102
1 2026-08-25 00:14 639232129927860324
158 ms 148.205.104.102