DNS response history for ns2.brcentraltelecom.com.br

ns2.brcentraltelecom.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-25. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 784 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.brcentraltelecom.com.br.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

784 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

177.107.191.13

Most recently resolved hosting IP on selected date

Successful Responses

30

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

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:07 639232482235303141
949 ms 177.107.191.13
29 2026-08-25 09:49 639232471861770303
6 ms 177.107.191.13
28 2026-08-25 09:32 639232461630217327
947 ms 177.107.191.13
27 2026-08-25 09:15 639232451282965990
3 ms 177.107.191.13
26 2026-08-25 08:58 639232440814614938
1109 ms 177.107.191.13
25 2026-08-25 08:40 639232430410720425
945 ms 177.107.191.13
24 2026-08-25 08:23 639232420003096185
4 ms 177.107.191.13
23 2026-08-25 08:06 639232409467287444
971 ms 177.107.191.13
22 2026-08-25 07:48 639232399077195997
965 ms 177.107.191.13
21 2026-08-25 07:31 639232388731528337
973 ms 177.107.191.13
20 2026-08-25 07:14 639232378288598612
969 ms 177.107.191.13
19 2026-08-25 06:19 639232346196373643
3 ms 177.107.191.13
18 2026-08-25 06:03 639232336112370741
3 ms 177.107.191.13
17 2026-08-25 05:46 639232326146508970
969 ms 177.107.191.13
16 2026-08-25 05:29 639232316189381720
966 ms 177.107.191.13
15 2026-08-25 05:13 639232306217998913
1187 ms 177.107.191.13
14 2026-08-25 04:56 639232296255744174
963 ms 177.107.191.13
13 2026-08-25 04:39 639232286095760789
955 ms 177.107.191.13
12 2026-08-25 04:22 639232276086186273
961 ms 177.107.191.13
11 2026-08-25 04:06 639232265900986425
969 ms 177.107.191.13
10 2026-08-25 03:49 639232255723518075
969 ms 177.107.191.13
9 2026-08-25 03:32 639232245484452890
966 ms 177.107.191.13
8 2026-08-25 03:15 639232235157175331
962 ms 177.107.191.13
7 2026-08-25 02:21 639232203197189095
956 ms 177.107.191.13
6 2026-08-25 02:04 639232192844564298
4 ms 177.107.191.13
5 2026-08-25 01:47 639232182496008942
972 ms 177.107.191.13
4 2026-08-25 01:30 639232172197053132
983 ms 177.107.191.13
3 2026-08-25 00:36 639232140250307418
966 ms 177.107.191.13
2 2026-08-25 00:19 639232129927860324
972 ms 177.107.191.13
1 2026-08-25 00:02 639232119551972438
968 ms 177.107.191.13