Network · data from 2026-11-12
AS16941 CENTURYLINK-LEGACY-FUSEPOINT-CTS-CANADA-POP - CenturyLink Communications, LLC
Registry name: CENTURYLINK-LEGACY-FUSEPOINT-CTS-CANADA-POP - CenturyLink Communications, LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS16941, 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.
| 64.254.144.0/21 | No ROA | Nonecovered by 64.254.144.0/20 | 673 100% |
| 64.254.152.0/23 | No ROA | Nonecovered by 64.254.144.0/20 | 673 100% |
| 64.254.154.0/23 | No ROA | Nonecovered by 64.254.144.0/20 | 673 100% |
| 64.254.156.0/22 | No ROA | Nonecovered by 64.254.144.0/20 | 673 100% |
| 68.71.200.0/22 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 68.71.205.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 72.35.8.0/21 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 206.150.96.0/20 | No ROA | Other IRR onlyBELL, NTTCOM | 673 100% |
| 206.150.112.0/20 | No ROA | Other IRR onlyBELL | 673 100% |
AS-SET
AS16941 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 38 are in fix.csv.
- ROA: none9
- Route object: none4
- Route object: RIR5
- Route object: not announced20
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 64.254.144.0/21 | No ROA covers it. Add a ROA for AS16941, maxLength 21. |
| Route object: none | 64.254.144.0/21 | No route object for it. A route object for 64.254.144.0/20 with origin AS16941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16941 in the RIR database for the space. |
| ROA: none | 64.254.152.0/23 | No ROA covers it. Add a ROA for AS16941, maxLength 23. |
| Route object: none | 64.254.152.0/23 | No route object for it. A route object for 64.254.144.0/20 with origin AS16941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16941 in the RIR database for the space. |
| ROA: none | 64.254.154.0/23 | No ROA covers it. Add a ROA for AS16941, maxLength 23. |
| Route object: none | 64.254.154.0/23 | No route object for it. A route object for 64.254.144.0/20 with origin AS16941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16941 in the RIR database for the space. |
| ROA: none | 64.254.156.0/22 | No ROA covers it. Add a ROA for AS16941, maxLength 22. |
| Route object: none | 64.254.156.0/22 | No route object for it. A route object for 64.254.144.0/20 with origin AS16941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS16941 in the RIR database for the space. |
| ROA: none | 68.71.200.0/22 | No ROA covers it. Add a ROA for AS16941, maxLength 22. |
| Route object: RIR | 68.71.200.0/22 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 68.71.205.0/24 | No ROA covers it. Add a ROA for AS16941, maxLength 24. |
| Route object: RIR | 68.71.205.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 72.35.8.0/21 | No ROA covers it. Add a ROA for AS16941, maxLength 21. |
| Route object: RIR | 72.35.8.0/21 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 206.150.96.0/20 | No ROA covers it. Add a ROA for AS16941, maxLength 20. |
| Route object: RIR | 206.150.96.0/20 | Route object only in BELL, NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 206.150.112.0/20 | No ROA covers it. Add a ROA for AS16941, maxLength 20. |
| Route object: RIR | 206.150.112.0/20 | Route object only in BELL. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS16941 whose prefix no peer sees AS16941 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.141.181.0/24 | RADB | No ROA |
| 64.254.144.0/20 | NTTCOM | No ROA |
| 66.244.220.0/24 | BELL | No ROA |
| 198.235.57.0/24 | RADB | No ROA |
| 198.235.58.0/23 | RADB | No ROA |
| 198.235.60.0/24 | RADB | No ROA |
| 204.94.104.0/24 | BELL | No ROA |
| 204.94.105.0/24 | BELL | No ROA |
| 204.94.106.0/24 | BELL | No ROA |
| 204.94.107.0/24 | BELL | No ROA |
| 206.25.64.0/19 | RADB | No ROA |
| 206.83.32.0/24 | BELL | No ROA |
| 206.83.33.0/24 | BELL | No ROA |
| 206.83.34.0/24 | BELL | No ROA |
| 206.83.35.0/24 | BELL | No ROA |
| 206.83.36.0/24 | BELL | No ROA |
| 206.83.37.0/24 | BELL | No ROA |
| 206.83.39.0/24 | BELL | No ROA |
| 208.70.128.0/24 | RADB | Valid |
| 2001:460:100::/46 | RADB | No 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.