DNS response history for ns2.infoteck.com.mx

ns2.infoteck.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 30 DNS check records, 27 successful responses, 3 failed responses, and 288 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.infoteck.com.mx.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

288 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

65.99.205.188

Most recently resolved hosting IP on selected date

Successful Responses

27

Checks that returned a measurable response

Failed Responses

3

Checks with no response or no returned latency

Failure Rate

10%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.infoteck.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
30 2026-08-25 10:17 639232492740373468
296 ms 65.99.205.188
29 2026-08-25 10:00 639232482235303141
277 ms 65.99.205.188
28 2026-08-25 09:42 639232471861770303
-
27 2026-08-25 09:25 639232461630217327
-
26 2026-08-25 09:08 639232451282965990
-
25 2026-08-25 08:51 639232440814614938
8 ms 65.99.205.188
24 2026-08-25 08:33 639232430410720425
4 ms 65.99.205.188
23 2026-08-25 08:16 639232420003096185
296 ms 65.99.205.188
22 2026-08-25 07:59 639232409467287444
163 ms 65.99.205.188
21 2026-08-25 07:41 639232399077195997
280 ms 65.99.205.188
20 2026-08-25 07:24 639232388731528337
150 ms 65.99.205.188
19 2026-08-25 07:06 639232378288598612
284 ms 65.99.205.188
18 2026-08-25 06:13 639232346196373643
292 ms 65.99.205.188
17 2026-08-25 05:56 639232336112370741
4 ms 65.99.205.188
16 2026-08-25 05:39 639232326146508970
298 ms 65.99.205.188
15 2026-08-25 05:23 639232316189381720
2277 ms 65.99.205.188
14 2026-08-25 05:06 639232306217998913
282 ms 65.99.205.188
13 2026-08-25 04:50 639232296255744174
145 ms 65.99.205.188
12 2026-08-25 04:33 639232286095760789
288 ms 65.99.205.188
11 2026-08-25 04:16 639232276086186273
2 ms 65.99.205.188
10 2026-08-25 03:59 639232265900986425
313 ms 65.99.205.188
9 2026-08-25 03:42 639232255723518075
279 ms 65.99.205.188
8 2026-08-25 03:25 639232245484452890
284 ms 65.99.205.188
7 2026-08-25 03:08 639232235157175331
142 ms 65.99.205.188
6 2026-08-25 02:15 639232203197189095
283 ms 65.99.205.188
5 2026-08-25 01:58 639232192844564298
554 ms 65.99.205.188
4 2026-08-25 01:40 639232182496008942
435 ms 65.99.205.188
3 2026-08-25 01:23 639232172197053132
131 ms 65.99.205.188
2 2026-08-25 00:30 639232140250307418
2 ms 65.99.205.188
1 2026-08-25 00:13 639232129927860324
3 ms 65.99.205.188