DNS response history for ns2.telmexla.net.co

ns2.telmexla.net.co 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-26. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 259 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.telmexla.net.co.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

259 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:29

All timestamps shown in UTC

Latest Resolved IP on Selected Date

190.157.8.71

Most recently resolved hosting IP on selected date

Successful Responses

38

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.telmexla.net.co

Showing DNS history for 2026-08-26 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
38 2026-08-26 12:29 639233434974187439
182 ms 190.157.8.71
37 2026-08-26 12:12 639233424567558554
353 ms 190.157.8.71
36 2026-08-26 11:55 639233414056832719
363 ms 190.157.8.71
35 2026-08-26 11:37 639233403515141099
176 ms 190.157.8.71
34 2026-08-26 10:42 639233370841350248
183 ms 190.157.8.71
33 2026-08-26 10:25 639233360361507238
5 ms 190.157.8.71
32 2026-08-26 10:08 639233350067824371
361 ms 190.157.8.71
31 2026-08-26 09:51 639233339545274518
189 ms 190.157.8.71
30 2026-08-26 09:33 639233329214918079
175 ms 190.157.8.71
29 2026-08-26 09:16 639233318749762337
349 ms 190.157.8.71
28 2026-08-26 08:58 639233308387917838
179 ms 190.157.8.71
27 2026-08-26 08:41 639233297961740122
3 ms 190.157.8.71
26 2026-08-26 08:24 639233287487159094
183 ms 190.157.8.71
25 2026-08-26 08:06 639233276995531707
357 ms 190.157.8.71
24 2026-08-26 07:49 639233266521568229
33 ms 190.157.8.71
23 2026-08-26 07:31 639233256081047431
359 ms 190.157.8.71
22 2026-08-26 06:37 639233223620132921
342 ms 190.157.8.71
21 2026-08-26 06:20 639233213287814244
10 ms 190.157.8.71
20 2026-08-26 06:03 639233202925983161
173 ms 190.157.8.71
19 2026-08-26 05:45 639233192644780696
342 ms 190.157.8.71
18 2026-08-26 05:28 639233182401183833
178 ms 190.157.8.71
17 2026-08-26 05:11 639233172074181051
334 ms 190.157.8.71
16 2026-08-26 04:54 639233161808421455
341 ms 190.157.8.71
15 2026-08-26 04:37 639233151357344052
168 ms 190.157.8.71
14 2026-08-26 04:19 639233141034116946
355 ms 190.157.8.71
13 2026-08-26 04:02 639233130828334142
346 ms 190.157.8.71
12 2026-08-26 03:45 639233120373450007
360 ms 190.157.8.71
11 2026-08-26 03:28 639233110066216193
353 ms 190.157.8.71
10 2026-08-26 02:34 639233078065410564
352 ms 190.157.8.71
9 2026-08-26 02:17 639233067787457832
348 ms 190.157.8.71
8 2026-08-26 02:00 639233057501801162
352 ms 190.157.8.71
7 2026-08-26 01:43 639233047089431703
367 ms 190.157.8.71
6 2026-08-26 01:26 639233036754790688
345 ms 190.157.8.71
5 2026-08-26 01:08 639233026412602472
539 ms 190.157.8.71
4 2026-08-26 00:51 639233016064066127
31 ms 190.157.8.71
3 2026-08-26 00:34 639233005922655772
358 ms 190.157.8.71
2 2026-08-26 00:17 639232995672256907
365 ms 190.157.8.71
1 2026-08-26 00:00 639232985300872416
50 ms 190.157.8.71