Network · data from 2026-11-12
AS3606 CONNCOLL-AS - Connecticut College
Registry name: CONNCOLL-AS - Connecticut College, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS3606, 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.
| 136.244.242.0/24 | No ROA | Nonecovered by 136.244.240.0/20 | 670 100% |
| 136.244.128.0/17 | No ROA | Other IRR onlyRADB | 670 100% |
| 136.244.128.0/19 | No ROA | Other IRR onlyRADB | 670 100% |
| 136.244.176.0/21 | No ROA | Other IRR onlyRADB | 670 100% |
| 136.244.176.0/22 | No ROA | Other IRR onlyRADB | 670 100% |
| 136.244.192.0/20 | No ROA | Other IRR onlyRADB | 670 100% |
| 136.244.208.0/20 | No ROA | Other IRR onlyRADB | 670 100% |
| 136.244.224.0/22 | No ROA | Other IRR onlyRADB | 670 100% |
| 136.244.228.0/22 | No ROA | Other IRR onlyRADB | 670 100% |
| 136.244.244.0/22 | No ROA | Other IRR onlyRADB | 670 100% |
AS-SET
AS3606 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 26 are in fix.csv.
- ROA: none10
- Route object: none1
- Route object: RIR9
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 136.244.242.0/24 | No ROA covers it. Add a ROA for AS3606, maxLength 24. |
| Route object: none | 136.244.242.0/24 | No route object for it. A route object for 136.244.240.0/20 with origin AS3606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3606 in the RIR database for the space. |
| ROA: none | 136.244.128.0/17 | No ROA covers it. Add a ROA for AS3606, maxLength 17. |
| Route object: RIR | 136.244.128.0/17 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 136.244.128.0/19 | No ROA covers it. Add a ROA for AS3606, maxLength 19. |
| Route object: RIR | 136.244.128.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 136.244.176.0/21 | No ROA covers it. Add a ROA for AS3606, maxLength 21. |
| Route object: RIR | 136.244.176.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 136.244.176.0/22 | No ROA covers it. Add a ROA for AS3606, maxLength 22. |
| Route object: RIR | 136.244.176.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 136.244.192.0/20 | No ROA covers it. Add a ROA for AS3606, maxLength 20. |
| Route object: RIR | 136.244.192.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 136.244.208.0/20 | No ROA covers it. Add a ROA for AS3606, maxLength 20. |
| Route object: RIR | 136.244.208.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 136.244.224.0/22 | No ROA covers it. Add a ROA for AS3606, maxLength 22. |
| Route object: RIR | 136.244.224.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 136.244.228.0/22 | No ROA covers it. Add a ROA for AS3606, maxLength 22. |
| Route object: RIR | 136.244.228.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 136.244.244.0/22 | No ROA covers it. Add a ROA for AS3606, maxLength 22. |
| Route object: RIR | 136.244.244.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS3606 whose prefix no peer sees AS3606 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 136.244.160.0/19 | RADB | No ROA |
| 136.244.181.0/24 | RADB | No ROA |
| 136.244.183.0/24 | RADB | No ROA |
| 136.244.232.0/21 | RADB | No ROA |
| 136.244.240.0/20 | RADB | No ROA |
| 136.244.240.0/24 | 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.