Network · data from 2026-11-12
AS63009 FIBERCASTNET - Fibercast Corporation
Registry name: FIBERCASTNET - Fibercast Corporation, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS63009, 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.
| 216.177.20.0/22 | No ROA | Nonecovered by 216.177.0.0/19 | 672 100% |
| 216.177.4.0/23 | No ROA | Nonecovered by 216.177.0.0/19 | 671 100% |
| 216.177.8.0/23 | No ROA | Nonecovered by 216.177.0.0/19 | 671 100% |
| 216.177.2.0/24 | No ROA | Other origin onlycovered by 216.177.0.0/19 | 353 52% |
| 216.177.9.0/24 | No ROA | Other origin onlycovered by 216.177.0.0/19 | 353 52% |
| 216.177.1.0/24 | No ROA | Other origin onlycovered by 216.177.0.0/19 | 352 52% |
| 216.177.24.0/24 | No ROA | Other origin onlycovered by 216.177.0.0/19 | 352 52% |
| 216.177.27.0/24 | No ROA | Other origin onlycovered by 216.177.0.0/19 | 352 52% |
| 216.177.30.0/24 | No ROA | Other origin onlycovered by 216.177.0.0/19 | 352 52% |
| 216.177.0.0/19 | No ROA | Other IRR onlyALTDB | 355 53% |
AS-SET
AS63009 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 22 are in fix.csv.
- ROA: none10
- Route object: none9
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 216.177.20.0/22 | No ROA covers it. Add a ROA for AS63009, maxLength 22. |
| Route object: none | 216.177.20.0/22 | No route object for it. A route object for 216.177.0.0/19 with origin AS63009 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63009 in the RIR database for the space. |
| ROA: none | 216.177.4.0/23 | No ROA covers it. Add a ROA for AS63009, maxLength 23. |
| Route object: none | 216.177.4.0/23 | No route object for it. A route object for 216.177.0.0/19 with origin AS63009 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63009 in the RIR database for the space. |
| ROA: none | 216.177.8.0/23 | No ROA covers it. Add a ROA for AS63009, maxLength 23. |
| Route object: none | 216.177.8.0/23 | No route object for it. A route object for 216.177.0.0/19 with origin AS63009 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63009 in the RIR database for the space. |
| ROA: none | 216.177.2.0/24 | No ROA covers it. Add a ROA for AS63009, maxLength 24. |
| Route object: none | 216.177.2.0/24 | Route objects for it name AS10367. A route object for 216.177.0.0/19 with origin AS63009 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63009 in the RIR database for the space. |
| ROA: none | 216.177.9.0/24 | No ROA covers it. Add a ROA for AS63009, maxLength 24. |
| Route object: none | 216.177.9.0/24 | Route objects for it name AS10367. A route object for 216.177.0.0/19 with origin AS63009 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63009 in the RIR database for the space. |
| ROA: none | 216.177.1.0/24 | No ROA covers it. Add a ROA for AS63009, maxLength 24. |
| Route object: none | 216.177.1.0/24 | Route objects for it name AS10367. A route object for 216.177.0.0/19 with origin AS63009 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63009 in the RIR database for the space. |
| ROA: none | 216.177.24.0/24 | No ROA covers it. Add a ROA for AS63009, maxLength 24. |
| Route object: none | 216.177.24.0/24 | Route objects for it name AS10367. A route object for 216.177.0.0/19 with origin AS63009 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63009 in the RIR database for the space. |
| ROA: none | 216.177.27.0/24 | No ROA covers it. Add a ROA for AS63009, maxLength 24. |
| Route object: none | 216.177.27.0/24 | Route objects for it name AS10367. A route object for 216.177.0.0/19 with origin AS63009 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63009 in the RIR database for the space. |
| ROA: none | 216.177.30.0/24 | No ROA covers it. Add a ROA for AS63009, maxLength 24. |
| Route object: none | 216.177.30.0/24 | Route objects for it name AS10367. A route object for 216.177.0.0/19 with origin AS63009 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63009 in the RIR database for the space. |
| ROA: none | 216.177.0.0/19 | No ROA covers it. Add a ROA for AS63009, maxLength 19. |
| Route object: RIR | 216.177.0.0/19 | Route object only in ALTDB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS63009 whose prefix no peer sees AS63009 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 199.204.192.0/21 | ALTDB | No ROA |
| 216.177.12.0/24 | ARIN | 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.