bgpreport

Network · data from 2026-11-12

AS3909 CENTURYLINK-LEGACY-QWEST-VDOC - CenturyLink Communications, LLC

Registry name: CENTURYLINK-LEGACY-QWEST-VDOC - CenturyLink Communications, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS3909, 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.123.252.0/24 No ROA None 673 100% 67
65.123.253.0/24 No ROA None 673 100% 67
67.13.228.0/24 No ROA None 673 100% 67
204.193.208.0/20 No ROA None 673 100% 67
8.64.40.0/21 No ROA None 658 98% 67
2001:428:3801:9::/64 No ROA None 3 0%low visibility 1

AS-SET

AS3909 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 12 are in fix.csv.

  • ROA: none6
  • Route object: none6
ChangePrefix or setDetailFull-table peers
ROA: none65.123.252.0/24No ROA covers it. Add a ROA for AS3909, maxLength 24.673 of 673
Route object: none65.123.252.0/24No route object for it. Add a route object with origin AS3909 in the RIR database for the space.673 of 673
ROA: none65.123.253.0/24No ROA covers it. Add a ROA for AS3909, maxLength 24.673 of 673
Route object: none65.123.253.0/24No route object for it. Add a route object with origin AS3909 in the RIR database for the space.673 of 673
ROA: none67.13.228.0/24No ROA covers it. Add a ROA for AS3909, maxLength 24.673 of 673
Route object: none67.13.228.0/24No route object for it. Add a route object with origin AS3909 in the RIR database for the space.673 of 673
ROA: none204.193.208.0/20No ROA covers it. Add a ROA for AS3909, maxLength 20.673 of 673
Route object: none204.193.208.0/20No route object for it. Add a route object with origin AS3909 in the RIR database for the space.673 of 673
ROA: none8.64.40.0/21No ROA covers it. Add a ROA for AS3909, maxLength 21.658 of 673
Route object: none8.64.40.0/21No route object for it. Add a route object with origin AS3909 in the RIR database for the space.658 of 673
ROA: none2001:428:3801:9::/64No ROA covers it. Add a ROA for AS3909, maxLength 64.3 of 636
Route object: none2001:428:3801:9::/64No route object for it. Add a route object with origin AS3909 in the RIR database for the space.3 of 636

Route objects not announced

Every route object with origin AS3909 is announced.

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.