DNS response history for ns2.centurytel.net

ns2.centurytel.net 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 36 DNS check records, 36 successful responses, 0 failed responses, and 294 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.centurytel.net.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

294 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.44.130.120

Most recently resolved hosting IP on selected date

Successful Responses

36

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.centurytel.net

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
36 2026-08-24 15:14 639231807961539652
107 ms 208.44.130.120
35 2026-08-24 14:57 639231797631669865
103 ms 208.44.130.120
34 2026-08-24 14:04 639231765923559455
162 ms 208.44.130.120
33 2026-08-24 13:47 639231755868832964
104 ms 208.44.130.120
32 2026-08-24 13:30 639231745628278877
8 ms 208.44.130.120
31 2026-08-24 13:13 639231735407682062
123 ms 208.44.130.120
30 2026-08-24 12:20 639231703815441688
205 ms 208.44.130.120
29 2026-08-24 12:04 639231693747052549
202 ms 208.44.130.120
28 2026-08-24 11:47 639231683712487276
106 ms 208.44.130.120
27 2026-08-24 11:30 639231673513573868
95 ms 208.44.130.120
26 2026-08-24 10:37 639231641791249939
2104 ms 208.44.130.120
25 2026-08-24 10:21 639231631866211033
166 ms 208.44.130.120
24 2026-08-24 10:04 639231621644955316
119 ms 208.44.130.120
23 2026-08-24 09:47 639231611478799259
113 ms 208.44.130.120
22 2026-08-24 08:54 639231579923718211
2286 ms 208.44.130.120
21 2026-08-24 08:37 639231569810702936
102 ms 208.44.130.120
20 2026-08-24 08:20 639231559762411619
98 ms 208.44.130.120
19 2026-08-24 08:04 639231549663595407
105 ms 208.44.130.120
18 2026-08-24 07:11 639231518076817246
153 ms 208.44.130.120
17 2026-08-24 06:55 639231508078650885
103 ms 208.44.130.120
16 2026-08-24 06:38 639231498210697093
102 ms 208.44.130.120
15 2026-08-24 06:21 639231488109699360
322 ms 208.44.130.120
14 2026-08-24 05:29 639231456772510692
113 ms 208.44.130.120
13 2026-08-24 05:13 639231447084631185
217 ms 208.44.130.120
12 2026-08-24 04:56 639231437208519473
141 ms 208.44.130.120
11 2026-08-24 04:40 639231427209627490
102 ms 208.44.130.120
10 2026-08-24 03:47 639231395791246644
126 ms 208.44.130.120
9 2026-08-24 03:31 639231386075551458
99 ms 208.44.130.120
8 2026-08-24 03:15 639231376208713791
9 ms 208.44.130.120
7 2026-08-24 02:58 639231366170589276
111 ms 208.44.130.120
6 2026-08-24 02:06 639231334732159368
101 ms 208.44.130.120
5 2026-08-24 01:49 639231325035670078
137 ms 208.44.130.120
4 2026-08-24 01:33 639231315132253837
111 ms 208.44.130.120
3 2026-08-24 01:16 639231305014280808
2106 ms 208.44.130.120
2 2026-08-24 00:24 639231273779380675
124 ms 208.44.130.120
1 2026-08-24 00:08 639231264180839154
110 ms 208.44.130.120