Network · data from 2026-11-12
AS201667 BreadCloud
Registry name: BreadCloud ASMBP LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS201667, 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.
| 76.9.111.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 87.76.190.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 143.20.196.0/24 | Invalid: origin | None | 2 0%low visibility |
| 178.214.214.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 2a06:9801:c5::/48 | Valid | None | 634 100% |
| 2a06:9801:1e::/48 | Valid | None | 632 99% |
| 109.65.66.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 194.61.239.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 217.217.45.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 217.217.47.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 141.140.31.0/24 | Valid | RIR databaseARIN, RADB | 669 99% |
| 2a13:9500:15f::/48 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
AS201667's PeeringDB record names no 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 10 are in fix.csv.
- ROA: origin4
- Route object: none6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 76.9.111.0/24 | ROAs covering it name AS834, AS11059, not AS201667. If AS201667 should announce it, add a ROA for AS201667. |
| Route object: none | 76.9.111.0/24 | Route objects for it name AS834. Add a route object with origin AS201667 in the RIR database for the space. |
| ROA: origin | 87.76.190.0/24 | ROAs covering it name AS152179, not AS201667. If AS201667 should announce it, add a ROA for AS201667. |
| Route object: none | 87.76.190.0/24 | Route objects for it name AS152179. Add a route object with origin AS201667 in the RIR database for the space. |
| ROA: origin | 143.20.196.0/24 | ROAs covering it name AS834, not AS201667. If AS201667 should announce it, add a ROA for AS201667. |
| Route object: none | 143.20.196.0/24 | No route object for it. Add a route object with origin AS201667 in the RIR database for the space. |
| ROA: origin | 178.214.214.0/24 | ROAs covering it name AS20473, not AS201667. If AS201667 should announce it, add a ROA for AS201667. |
| Route object: none | 178.214.214.0/24 | Route objects for it name AS20473. Add a route object with origin AS201667 in the RIR database for the space. |
| Route object: none | 2a06:9801:c5::/48 | No route object for it. Add a route object with origin AS201667 in the RIR database for the space. |
| Route object: none | 2a06:9801:1e::/48 | No route object for it. Add a route object with origin AS201667 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS201667 is announced.
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.