DNS response history for ns1.resalemexico.com

ns1.resalemexico.com 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 305 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 ns1.resalemexico.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

305 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.135.126.118

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 ns1.resalemexico.com

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
156 ms 148.135.126.118
27 2026-08-25 09:27 639232461630217327
4 ms 148.135.126.118
26 2026-08-25 09:10 639232451282965990
3 ms 148.135.126.118
25 2026-08-25 08:52 639232440814614938
224 ms 148.135.126.118
24 2026-08-25 08:35 639232430410720425
321 ms 148.135.126.118
23 2026-08-25 08:18 639232420003096185
313 ms 148.135.126.118
22 2026-08-25 08:00 639232409467287444
314 ms 148.135.126.118
21 2026-08-25 07:43 639232399077195997
348 ms 148.135.126.118
20 2026-08-25 07:25 639232388731528337
318 ms 148.135.126.118
19 2026-08-25 07:08 639232378288598612
315 ms 148.135.126.118
18 2026-08-25 06:14 639232346196373643
53 ms 148.135.126.118
17 2026-08-25 05:57 639232336112370741
15 ms 148.135.126.118
16 2026-08-25 05:41 639232326146508970
8 ms 148.135.126.118
15 2026-08-25 05:24 639232316189381720
314 ms 148.135.126.118
14 2026-08-25 05:08 639232306217998913
2158 ms 148.135.126.118
13 2026-08-25 04:51 639232296255744174
313 ms 148.135.126.118
12 2026-08-25 04:34 639232286095760789
313 ms 148.135.126.118
11 2026-08-25 04:17 639232276086186273
318 ms 148.135.126.118
10 2026-08-25 04:01 639232265900986425
318 ms 148.135.126.118
9 2026-08-25 03:44 639232255723518075
151 ms 148.135.126.118
8 2026-08-25 03:27 639232245484452890
316 ms 148.135.126.118
7 2026-08-25 03:09 639232235157175331
159 ms 148.135.126.118
6 2026-08-25 02:16 639232203197189095
160 ms 148.135.126.118
5 2026-08-25 01:59 639232192844564298
324 ms 148.135.126.118
4 2026-08-25 01:42 639232182496008942
318 ms 148.135.126.118
3 2026-08-25 01:24 639232172197053132
328 ms 148.135.126.118
2 2026-08-25 00:31 639232140250307418
323 ms 148.135.126.118
1 2026-08-25 00:14 639232129927860324
330 ms 148.135.126.118