Network · data from 2026-11-12
AS33545 BARDCOLLEGE - Bard College
Registry name: BARDCOLLEGE - Bard College, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS33545, 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.
| 192.246.230.0/24 | No ROA | Other origin onlycovered by 192.246.224.0/21 | 670 100% |
| 173.46.96.0/19 | No ROA | Other IRR onlyALTDB | 673 100% |
| 192.76.239.0/24 | No ROA | Other IRR onlyALTDB | 673 100% |
| 192.83.253.0/24 | No ROA | Other IRR onlyALTDB | 673 100% |
| 192.246.224.0/22 | No ROA | Other IRR onlyALTDB | 673 100% |
| 192.246.228.0/23 | No ROA | Other IRR onlyALTDB | 673 100% |
| 192.246.231.0/24 | No ROA | Other IRR onlyALTDB | 673 100% |
| 192.246.232.0/22 | No ROA | Other IRR onlyALTDB | 673 100% |
| 192.246.235.0/24 | No ROA | Other IRR onlyALTDB | 673 100% |
| 2620:12d:2000::/40 | No ROA | Other IRR onlyRADB | 635 100% |
AS-SET
AS33545 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 24 are in fix.csv.
- ROA: none10
- Route object: none1
- Route object: RIR9
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.246.230.0/24 | No ROA covers it. Add a ROA for AS33545, maxLength 24. |
| Route object: none | 192.246.230.0/24 | Route objects for it name AS7029, AS13536. A route object for 192.246.224.0/21 with origin AS33545 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33545 in the RIR database for the space. |
| ROA: none | 173.46.96.0/19 | No ROA covers it. Add a ROA for AS33545, maxLength 19. |
| Route object: RIR | 173.46.96.0/19 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 192.76.239.0/24 | No ROA covers it. Add a ROA for AS33545, maxLength 24. |
| Route object: RIR | 192.76.239.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 192.83.253.0/24 | No ROA covers it. Add a ROA for AS33545, maxLength 24. |
| Route object: RIR | 192.83.253.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 192.246.224.0/22 | No ROA covers it. Add a ROA for AS33545, maxLength 22. |
| Route object: RIR | 192.246.224.0/22 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 192.246.228.0/23 | No ROA covers it. Add a ROA for AS33545, maxLength 23. |
| Route object: RIR | 192.246.228.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 192.246.231.0/24 | No ROA covers it. Add a ROA for AS33545, maxLength 24. |
| Route object: RIR | 192.246.231.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 192.246.232.0/22 | No ROA covers it. Add a ROA for AS33545, maxLength 22. |
| Route object: RIR | 192.246.232.0/22 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 192.246.235.0/24 | No ROA covers it. Add a ROA for AS33545, maxLength 24. |
| Route object: RIR | 192.246.235.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 2620:12d:2000::/40 | No ROA covers it. Add a ROA for AS33545, maxLength 40. |
| Route object: RIR | 2620:12d:2000::/40 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS33545 whose prefix no peer sees AS33545 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 72.22.177.0/24 | RADB | No ROA |
| 72.22.178.0/23 | RADB | No ROA |
| 72.22.180.0/24 | RADB | No ROA |
| 192.246.224.0/21 | 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.