bgpreport

Network · data from 2026-11-12

AS33227 BlueBridge Networks

Registry name: BLUEBRIDGE-NETWORKS - Blue Bridge Networks, US · PeeringDB

8IPv4 routes 0.0% RPKI valid · 62.5% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
8No ROA 3 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS33227, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS33227, 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.
65.255.160.0/20 No ROA Other origin only 673 100% 67
66.218.176.0/20 No ROA None 673 100% 67
64.28.32.0/24 No ROA None 0 0%low visibility 1
74.214.16.0/20 No ROA Other IRR onlyRADB 673 100% 67
192.69.72.0/23 No ROA Other IRR onlyRADB 673 100% 67
206.216.144.0/22 No ROA Other IRR onlyRADB 673 100% 67
206.216.152.0/22 No ROA Other IRR onlyRADB 673 100% 67
207.93.98.0/24 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS33227'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 17 are in fix.csv.

  • ROA: none8
  • Route object: none3
  • Route object: RIR5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none65.255.160.0/20No ROA covers it. Add a ROA for AS33227, maxLength 20.673 of 673
Route object: none65.255.160.0/20Route objects for it name AS22958, AS26554. Add a route object with origin AS33227 in the RIR database for the space.673 of 673
ROA: none66.218.176.0/20No ROA covers it. Add a ROA for AS33227, maxLength 20.673 of 673
Route object: none66.218.176.0/20No route object for it. Add a route object with origin AS33227 in the RIR database for the space.673 of 673
ROA: none64.28.32.0/24No ROA covers it. Add a ROA for AS33227, maxLength 24.0 of 673
Route object: none64.28.32.0/24No route object for it. Add a route object with origin AS33227 in the RIR database for the space.0 of 673
ROA: none74.214.16.0/20No ROA covers it. Add a ROA for AS33227, maxLength 20.673 of 673
Route object: RIR74.214.16.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none192.69.72.0/23No ROA covers it. Add a ROA for AS33227, maxLength 23.673 of 673
Route object: RIR192.69.72.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none206.216.144.0/22No ROA covers it. Add a ROA for AS33227, maxLength 22.673 of 673
Route object: RIR206.216.144.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none206.216.152.0/22No ROA covers it. Add a ROA for AS33227, maxLength 22.673 of 673
Route object: RIR206.216.152.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none207.93.98.0/24No ROA covers it. Add a ROA for AS33227, maxLength 24.673 of 673
Route object: RIR207.93.98.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Route objects with origin AS33227 whose prefix no peer sees AS33227 announce. Many are kept on purpose (backup routes, space announced only in some places).

162.249.152.0/22RADBNo 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.