DNS response history for la1.completehub.com

la1.completehub.com 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 34 DNS check records, 34 successful responses, 0 failed responses, and 154 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 la1.completehub.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

154 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:58

All timestamps shown in UTC

Latest Resolved IP on Selected Date

206.168.149.66

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 la1.completehub.com

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
34 2026-08-24 13:58 639231765923559455
18 ms 206.168.149.66
33 2026-08-24 13:41 639231755868832964
36 ms 206.168.149.66
32 2026-08-24 13:24 639231745628278877
36 ms 206.168.149.66
31 2026-08-24 13:07 639231735407682062
39 ms 206.168.149.66
30 2026-08-24 12:15 639231703815441688
2023 ms 206.168.149.66
29 2026-08-24 11:58 639231693747052549
26 ms 206.168.149.66
28 2026-08-24 11:41 639231683712487276
30 ms 206.168.149.66
27 2026-08-24 11:24 639231673513573868
7 ms 206.168.149.66
26 2026-08-24 10:31 639231641791249939
2052 ms 206.168.149.66
25 2026-08-24 10:15 639231631866211033
12 ms 206.168.149.66
24 2026-08-24 09:58 639231621644955316
57 ms 206.168.149.66
23 2026-08-24 09:41 639231611478799259
35 ms 206.168.149.66
22 2026-08-24 08:48 639231579923718211
84 ms 206.168.149.66
21 2026-08-24 08:31 639231569810702936
207 ms 206.168.149.66
20 2026-08-24 08:14 639231559762411619
40 ms 206.168.149.66
19 2026-08-24 07:58 639231549663595407
23 ms 206.168.149.66
18 2026-08-24 07:05 639231518076817246
58 ms 206.168.149.66
17 2026-08-24 06:48 639231508078650885
32 ms 206.168.149.66
16 2026-08-24 06:32 639231498210697093
7 ms 206.168.149.66
15 2026-08-24 06:15 639231488109699360
16 ms 206.168.149.66
14 2026-08-24 05:23 639231456772510692
16 ms 206.168.149.66
13 2026-08-24 05:07 639231447084631185
23 ms 206.168.149.66
12 2026-08-24 04:50 639231437208519473
20 ms 206.168.149.66
11 2026-08-24 04:34 639231427209627490
56 ms 206.168.149.66
10 2026-08-24 03:41 639231395791246644
44 ms 206.168.149.66
9 2026-08-24 03:25 639231386075551458
41 ms 206.168.149.66
8 2026-08-24 03:09 639231376208713791
27 ms 206.168.149.66
7 2026-08-24 02:52 639231366170589276
25 ms 206.168.149.66
6 2026-08-24 02:00 639231334732159368
11 ms 206.168.149.66
5 2026-08-24 01:43 639231325035670078
10 ms 206.168.149.66
4 2026-08-24 01:27 639231315132253837
46 ms 206.168.149.66
3 2026-08-24 01:10 639231305014280808
36 ms 206.168.149.66
2 2026-08-24 00:18 639231273779380675
42 ms 206.168.149.66
1 2026-08-24 00:02 639231264180839154
16 ms 206.168.149.66