DNS response history for ns2.teleyos.com.br

ns2.teleyos.com.br 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 34 DNS check records, 34 successful responses, 0 failed responses, and 307 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.teleyos.com.br.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

307 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.240.3.127

Most recently resolved hosting IP on selected date

Successful Responses

34

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.teleyos.com.br

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
34 2026-08-26 10:42 639233370841350248
305 ms 162.240.3.127
33 2026-08-26 10:25 639233360361507238
309 ms 162.240.3.127
32 2026-08-26 10:08 639233350067824371
146 ms 162.240.3.127
31 2026-08-26 09:51 639233339545274518
304 ms 162.240.3.127
30 2026-08-26 09:33 639233329214918079
148 ms 162.240.3.127
29 2026-08-26 09:16 639233318749762337
345 ms 162.240.3.127
28 2026-08-26 08:58 639233308387917838
156 ms 162.240.3.127
27 2026-08-26 08:41 639233297961740122
327 ms 162.240.3.127
26 2026-08-26 08:24 639233287487159094
329 ms 162.240.3.127
25 2026-08-26 08:06 639233276995531707
160 ms 162.240.3.127
24 2026-08-26 07:49 639233266521568229
308 ms 162.240.3.127
23 2026-08-26 07:31 639233256081047431
308 ms 162.240.3.127
22 2026-08-26 06:37 639233223620132921
309 ms 162.240.3.127
21 2026-08-26 06:20 639233213287814244
2147 ms 162.240.3.127
20 2026-08-26 06:03 639233202925983161
308 ms 162.240.3.127
19 2026-08-26 05:45 639233192644780696
301 ms 162.240.3.127
18 2026-08-26 05:28 639233182401183833
303 ms 162.240.3.127
17 2026-08-26 05:11 639233172074181051
147 ms 162.240.3.127
16 2026-08-26 04:54 639233161808421455
145 ms 162.240.3.127
15 2026-08-26 04:37 639233151357344052
455 ms 162.240.3.127
14 2026-08-26 04:19 639233141034116946
145 ms 162.240.3.127
13 2026-08-26 04:02 639233130828334142
297 ms 162.240.3.127
12 2026-08-26 03:45 639233120373450007
298 ms 162.240.3.127
11 2026-08-26 03:28 639233110066216193
299 ms 162.240.3.127
10 2026-08-26 02:34 639233078065410564
155 ms 162.240.3.127
9 2026-08-26 02:17 639233067787457832
150 ms 162.240.3.127
8 2026-08-26 02:00 639233057501801162
344 ms 162.240.3.127
7 2026-08-26 01:43 639233047089431703
145 ms 162.240.3.127
6 2026-08-26 01:26 639233036754790688
20 ms 162.240.3.127
5 2026-08-26 01:09 639233026412602472
307 ms 162.240.3.127
4 2026-08-26 00:51 639233016064066127
144 ms 162.240.3.127
3 2026-08-26 00:34 639233005922655772
148 ms 162.240.3.127
2 2026-08-26 00:17 639232995672256907
292 ms 162.240.3.127
1 2026-08-26 00:00 639232985300872416
426 ms 162.240.3.127