DNS response history for ns2.c3telecom.com.br

ns2.c3telecom.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 337 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.c3telecom.com.br.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

337 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

177.23.71.167

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 ns2.c3telecom.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:17 639231735407682062
443 ms 177.23.71.167
30 2026-08-24 12:25 639231703815441688
436 ms 177.23.71.167
29 2026-08-24 12:08 639231693747052549
210 ms 177.23.71.167
28 2026-08-24 11:51 639231683712487276
220 ms 177.23.71.167
27 2026-08-24 11:34 639231673513573868
447 ms 177.23.71.167
26 2026-08-24 10:41 639231641791249939
2280 ms 177.23.71.167
25 2026-08-24 10:25 639231631866211033
437 ms 177.23.71.167
24 2026-08-24 10:08 639231621644955316
453 ms 177.23.71.167
23 2026-08-24 09:51 639231611478799259
5 ms 177.23.71.167
22 2026-08-24 08:58 639231579923718211
4 ms 177.23.71.167
21 2026-08-24 08:42 639231569810702936
220 ms 177.23.71.167
20 2026-08-24 08:24 639231559762411619
421 ms 177.23.71.167
19 2026-08-24 08:08 639231549663595407
440 ms 177.23.71.167
18 2026-08-24 07:15 639231518076817246
8 ms 177.23.71.167
17 2026-08-24 06:59 639231508078650885
437 ms 177.23.71.167
16 2026-08-24 06:42 639231498210697093
441 ms 177.23.71.167
15 2026-08-24 06:25 639231488109699360
441 ms 177.23.71.167
14 2026-08-24 05:33 639231456772510692
432 ms 177.23.71.167
13 2026-08-24 05:17 639231447084631185
4 ms 177.23.71.167
12 2026-08-24 05:00 639231437208519473
441 ms 177.23.71.167
11 2026-08-24 04:44 639231427209627490
439 ms 177.23.71.167
10 2026-08-24 03:51 639231395791246644
7 ms 177.23.71.167
9 2026-08-24 03:35 639231386075551458
9 ms 177.23.71.167
8 2026-08-24 03:19 639231376208713791
439 ms 177.23.71.167
7 2026-08-24 03:02 639231366170589276
11 ms 177.23.71.167
6 2026-08-24 02:10 639231334732159368
10 ms 177.23.71.167
5 2026-08-24 01:53 639231325035670078
236 ms 177.23.71.167
4 2026-08-24 01:37 639231315132253837
207 ms 177.23.71.167
3 2026-08-24 01:20 639231305014280808
433 ms 177.23.71.167
2 2026-08-24 00:28 639231273779380675
437 ms 177.23.71.167
1 2026-08-24 00:12 639231264180839154
3 ms 177.23.71.167