bgpreport

Network · data from 2026-11-12

AS14905 CENTURYLINK-LEGACY-EMBARQ-VACHVL - CenturyLink Communications, LLC

Registry name: CENTURYLINK-LEGACY-EMBARQ-VACHVL - CenturyLink Communications, LLC, US · not in PeeringDB

10IPv4 routes 0.0% RPKI valid · 0.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
10No ROA 10 with no route object for this origin
10Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS14905, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS14905, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

65.40.216.0/22 No ROA None 2 0%low visibility 2
69.34.32.0/22 No ROA None 2 0%low visibility 2
69.68.184.0/21 No ROA None 2 0%low visibility 2
71.2.160.0/20 No ROA None 2 0%low visibility 2
76.4.64.0/19 No ROA None 2 0%low visibility 2
76.7.48.0/20 No ROA None 2 0%low visibility 2
184.2.80.0/20 No ROA None 2 0%low visibility 2
184.2.128.0/20 No ROA None 2 0%low visibility 2
184.6.160.0/20 No ROA None 2 0%low visibility 2
208.33.152.0/21 No ROA None 2 0%low visibility 2

AS-SET

AS14905 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 23 are in fix.csv.

  • ROA: none10
  • Route object: none10
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none65.40.216.0/22No ROA covers it. Add a ROA for AS14905, maxLength 22.2 of 673
Route object: none65.40.216.0/22No route object for it. Add a route object with origin AS14905 in the RIR database for the space.2 of 673
ROA: none69.34.32.0/22No ROA covers it. Add a ROA for AS14905, maxLength 22.2 of 673
Route object: none69.34.32.0/22No route object for it. Add a route object with origin AS14905 in the RIR database for the space.2 of 673
ROA: none69.68.184.0/21No ROA covers it. Add a ROA for AS14905, maxLength 21.2 of 673
Route object: none69.68.184.0/21No route object for it. Add a route object with origin AS14905 in the RIR database for the space.2 of 673
ROA: none71.2.160.0/20No ROA covers it. Add a ROA for AS14905, maxLength 20.2 of 673
Route object: none71.2.160.0/20No route object for it. Add a route object with origin AS14905 in the RIR database for the space.2 of 673
ROA: none76.4.64.0/19No ROA covers it. Add a ROA for AS14905, maxLength 19.2 of 673
Route object: none76.4.64.0/19No route object for it. Add a route object with origin AS14905 in the RIR database for the space.2 of 673
ROA: none76.7.48.0/20No ROA covers it. Add a ROA for AS14905, maxLength 20.2 of 673
Route object: none76.7.48.0/20No route object for it. Add a route object with origin AS14905 in the RIR database for the space.2 of 673
ROA: none184.2.80.0/20No ROA covers it. Add a ROA for AS14905, maxLength 20.2 of 673
Route object: none184.2.80.0/20No route object for it. Add a route object with origin AS14905 in the RIR database for the space.2 of 673
ROA: none184.2.128.0/20No ROA covers it. Add a ROA for AS14905, maxLength 20.2 of 673
Route object: none184.2.128.0/20No route object for it. Add a route object with origin AS14905 in the RIR database for the space.2 of 673
ROA: none184.6.160.0/20No ROA covers it. Add a ROA for AS14905, maxLength 20.2 of 673
Route object: none184.6.160.0/20No route object for it. Add a route object with origin AS14905 in the RIR database for the space.2 of 673
ROA: none208.33.152.0/21No ROA covers it. Add a ROA for AS14905, maxLength 21.2 of 673
Route object: none208.33.152.0/21No route object for it. Add a route object with origin AS14905 in the RIR database for the space.2 of 673

Route objects not announced

Route objects with origin AS14905 whose prefix no peer sees AS14905 announce. Many are kept on purpose (backup routes, space announced only in some places).

76.7.56.0/21RADBNo ROA
144.75.0.0/16RADBNo ROA
205.244.105.0/24RADBNo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.