DNS response history for ns02.veotelecom.com.br

ns02.veotelecom.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-24. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 667 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 ns02.veotelecom.com.br.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

667 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:18

All timestamps shown in UTC

Latest Resolved IP on Selected Date

143.137.188.131

Most recently resolved hosting IP on selected date

Successful Responses

31

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 ns02.veotelecom.com.br

Showing DNS history for 2026-08-24 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
31 2026-08-24 13:18 639231735407682062
440 ms 143.137.188.131
30 2026-08-24 12:25 639231703815441688
430 ms 143.137.188.131
29 2026-08-24 12:09 639231693747052549
446 ms 143.137.188.131
28 2026-08-24 11:52 639231683712487276
2213 ms 143.137.188.131
27 2026-08-24 11:35 639231673513573868
233 ms 143.137.188.131
26 2026-08-24 10:42 639231641791249939
609 ms 143.137.188.131
25 2026-08-24 10:26 639231631866211033
430 ms 143.137.188.131
24 2026-08-24 10:09 639231621644955316
12 ms 143.137.188.131
23 2026-08-24 09:52 639231611478799259
236 ms 143.137.188.131
22 2026-08-24 08:59 639231579923718211
431 ms 143.137.188.131
21 2026-08-24 08:42 639231569810702936
2210 ms 143.137.188.131
20 2026-08-24 08:25 639231559762411619
473 ms 143.137.188.131
19 2026-08-24 08:09 639231549663595407
471 ms 143.137.188.131
18 2026-08-24 07:16 639231518076817246
439 ms 143.137.188.131
17 2026-08-24 06:59 639231508078650885
442 ms 143.137.188.131
16 2026-08-24 06:43 639231498210697093
439 ms 143.137.188.131
15 2026-08-24 06:26 639231488109699360
449 ms 143.137.188.131
14 2026-08-24 05:34 639231456772510692
430 ms 143.137.188.131
13 2026-08-24 05:17 639231447084631185
430 ms 143.137.188.131
12 2026-08-24 05:01 639231437208519473
447 ms 143.137.188.131
11 2026-08-24 04:44 639231427209627490
439 ms 143.137.188.131
10 2026-08-24 03:52 639231395791246644
223 ms 143.137.188.131
9 2026-08-24 03:36 639231386075551458
2282 ms 143.137.188.131
8 2026-08-24 03:20 639231376208713791
670 ms 143.137.188.131
7 2026-08-24 03:03 639231366170589276
440 ms 143.137.188.131
6 2026-08-24 02:10 639231334732159368
441 ms 143.137.188.131
5 2026-08-24 01:54 639231325035670078
2008 ms 143.137.188.131
4 2026-08-24 01:38 639231315132253837
218 ms 143.137.188.131
3 2026-08-24 01:21 639231305014280808
2008 ms 143.137.188.131
2 2026-08-24 00:29 639231273779380675
225 ms 143.137.188.131
1 2026-08-24 00:13 639231264180839154
3 ms 143.137.188.131