bgpreport

Network · data from 2026-11-12

AS201667 BreadCloud

Registry name: BreadCloud ASMBP LLC, US · PeeringDB

9IPv4 routes 55.6% RPKI valid · 55.6% with a route object
3IPv6 routes 100.0% RPKI valid · 33.3% with a route object
4RPKI invalid 4 origin · 0 maxLength
0No ROA 6 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS201667, seen from no peer

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 2
87.76.190.0/24 Invalid: origin Other origin only 2 0%low visibility 2
143.20.196.0/24 Invalid: origin None 2 0%low visibility 2
178.214.214.0/24 Invalid: origin Other origin only 2 0%low visibility 2
2a06:9801:c5::/48 Valid None 634 100% 68
2a06:9801:1e::/48 Valid None 632 99% 68
109.65.66.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
194.61.239.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
217.217.45.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
217.217.47.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
141.140.31.0/24 Valid RIR databaseARIN, RADB 669 99% 66
2a13:9500:15f::/48 Valid RIR databaseRIPE 633 100% 68

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
ChangePrefix or setDetailFull-table peers
ROA: origin76.9.111.0/24ROAs covering it name AS834, AS11059, not AS201667. If AS201667 should announce it, add a ROA for AS201667.2 of 673
Route object: none76.9.111.0/24Route objects for it name AS834. Add a route object with origin AS201667 in the RIR database for the space.2 of 673
ROA: origin87.76.190.0/24ROAs covering it name AS152179, not AS201667. If AS201667 should announce it, add a ROA for AS201667.2 of 673
Route object: none87.76.190.0/24Route objects for it name AS152179. Add a route object with origin AS201667 in the RIR database for the space.2 of 673
ROA: origin143.20.196.0/24ROAs covering it name AS834, not AS201667. If AS201667 should announce it, add a ROA for AS201667.2 of 673
Route object: none143.20.196.0/24No route object for it. Add a route object with origin AS201667 in the RIR database for the space.2 of 673
ROA: origin178.214.214.0/24ROAs covering it name AS20473, not AS201667. If AS201667 should announce it, add a ROA for AS201667.2 of 673
Route object: none178.214.214.0/24Route objects for it name AS20473. Add a route object with origin AS201667 in the RIR database for the space.2 of 673
Route object: none2a06:9801:c5::/48No route object for it. Add a route object with origin AS201667 in the RIR database for the space.634 of 636
Route object: none2a06:9801:1e::/48No route object for it. Add a route object with origin AS201667 in the RIR database for the space.632 of 636

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.