Network · data from 2026-11-12
AS10255 Cambridge Bandwidth Consortium
Registry name: SINISTER - Sinister and Solitary, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS10255, 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.31.227.0/24 | No ROA | Other IRR onlyALTDB | 666 99% |
| 198.49.250.0/24 | No ROA | Other IRR onlyALTDB, RIPE-NONAUTH | 666 99% |
| 199.201.145.0/24 | No ROA | Other IRR onlyALTDB, RIPE-NONAUTH | 666 99% |
| 199.204.152.0/22 | No ROA | Other IRR onlyALTDB, RADB | 666 99% |
| 204.69.206.0/24 | No ROA | Other IRR onlyALTDB, RIPE-NONAUTH | 666 99% |
| 204.107.200.0/24 | No ROA | Other IRR onlyALTDB, RIPE-NONAUTH | 666 99% |
| 2620:131:f000::/40 | No ROA | Other IRR onlyALTDB, RIPE-NONAUTH | 629 99% |
| 199.74.249.0/24 | Valid | RIR databaseARIN, RIPE-NONAUTH | 666 99% |
| 2605:6c00:9::/48 | Valid | RIR databaseARIN, RADB | 630 99% |
AS-SET
PeeringDB's irr_as_set for AS10255: AS-CAMBANDCONS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS10255 isn't in the set, or no route object for AS10255 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS10255 in it | Not covered |
|---|---|---|---|---|---|
| AS-CAMBANDCONS | ALTDB | 2 | 1 | Yes | 0 |
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 19 are in fix.csv.
- ROA: none7
- Route object: RIR7
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.31.227.0/24 | No ROA covers it. Add a ROA for AS10255, maxLength 24. |
| Route object: RIR | 192.31.227.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 198.49.250.0/24 | No ROA covers it. Add a ROA for AS10255, maxLength 24. |
| Route object: RIR | 198.49.250.0/24 | Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 199.201.145.0/24 | No ROA covers it. Add a ROA for AS10255, maxLength 24. |
| Route object: RIR | 199.201.145.0/24 | Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 199.204.152.0/22 | No ROA covers it. Add a ROA for AS10255, maxLength 22. |
| Route object: RIR | 199.204.152.0/22 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| ROA: none | 204.69.206.0/24 | No ROA covers it. Add a ROA for AS10255, maxLength 24. |
| Route object: RIR | 204.69.206.0/24 | Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 204.107.200.0/24 | No ROA covers it. Add a ROA for AS10255, maxLength 24. |
| Route object: RIR | 204.107.200.0/24 | Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 2620:131:f000::/40 | No ROA covers it. Add a ROA for AS10255, maxLength 40. |
| Route object: RIR | 2620:131:f000::/40 | Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS10255 whose prefix no peer sees AS10255 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.156.180.0/24 | ALTDB | No ROA |
| 192.251.193.0/24 | ALTDB | No ROA |
| 198.5.5.0/24 | ALTDB | No ROA |
| 199.164.139.0/24 | ALTDB | No ROA |
| 205.159.169.0/24 | ALTDB | 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.