Network · data from 2026-11-12
AS397038 BROWARD-COLLEGE-01 - Broward College
Registry name: BROWARD-COLLEGE-01 - Broward College, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS397038, 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.
| 209.87.196.0/24 | No ROA | Nonecovered by 209.87.192.0/20 | 673 100% |
| 209.87.198.0/23 | No ROA | Nonecovered by 209.87.192.0/20 | 673 100% |
| 209.87.200.0/21 | No ROA | Nonecovered by 209.87.192.0/20 | 673 100% |
| 209.87.197.0/24 | No ROA | Other origin onlycovered by 209.87.192.0/20 | 649 96% |
| 207.189.183.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 209.87.192.0/22 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS397038 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 13 are in fix.csv.
- ROA: none6
- Route object: none4
- Route object: RIR2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 209.87.196.0/24 | No ROA covers it. Add a ROA for AS397038, maxLength 24. |
| Route object: none | 209.87.196.0/24 | No route object for it. A route object for 209.87.192.0/20 with origin AS397038 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397038 in the RIR database for the space. |
| ROA: none | 209.87.198.0/23 | No ROA covers it. Add a ROA for AS397038, maxLength 23. |
| Route object: none | 209.87.198.0/23 | No route object for it. A route object for 209.87.192.0/20 with origin AS397038 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397038 in the RIR database for the space. |
| ROA: none | 209.87.200.0/21 | No ROA covers it. Add a ROA for AS397038, maxLength 21. |
| Route object: none | 209.87.200.0/21 | No route object for it. A route object for 209.87.192.0/20 with origin AS397038 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397038 in the RIR database for the space. |
| ROA: none | 209.87.197.0/24 | No ROA covers it. Add a ROA for AS397038, maxLength 24. |
| Route object: none | 209.87.197.0/24 | Route objects for it name AS46887. A route object for 209.87.192.0/20 with origin AS397038 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397038 in the RIR database for the space. |
| ROA: none | 207.189.183.0/24 | No ROA covers it. Add a ROA for AS397038, maxLength 24. |
| Route object: RIR | 207.189.183.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 209.87.192.0/22 | No ROA covers it. Add a ROA for AS397038, maxLength 22. |
| Route object: RIR | 209.87.192.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS397038 whose prefix no peer sees AS397038 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 209.87.192.0/20 | 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.