bgpreport

Network · data from 2026-11-12

AS32145 OPENCAPE - OpenCape Corporation

Registry name: OPENCAPE - OpenCape Corporation, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS32145, 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.

104.249.184.0/22 Valid Other origin only 673 100% 67
104.249.187.0/24 Valid None 673 100% 67
131.109.134.0/24 Valid Nonecovered by 131.109.132.0/22 673 100% 67
131.109.128.0/21 Valid Other IRR onlyRADB 673 100% 67
131.109.130.0/24 Valid Other IRR onlyRADB 673 100% 67
170.39.220.0/22 Valid Other IRR onlyNTTCOM 673 100% 67
192.107.120.0/23 Valid Other IRR onlyRADB 673 100% 67
69.87.184.0/22 Valid RIR databaseARIN 673 100% 67

AS-SET

AS32145 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 10 are in fix.csv.

  • Route object: none3
  • Route object: RIR4
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none104.249.184.0/22Route objects for it name AS14325. Add a route object with origin AS32145 in the RIR database for the space.673 of 673
Route object: none104.249.187.0/24No route object for it. Add a route object with origin AS32145 in the RIR database for the space.673 of 673
Route object: none131.109.134.0/24No route object for it. A route object for 131.109.132.0/22 with origin AS32145 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32145 in the RIR database for the space.673 of 673
Route object: RIR131.109.128.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR131.109.130.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR170.39.220.0/22Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR192.107.120.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

131.109.128.0/23RADBValid
131.109.131.0/24RADBValid
131.109.132.0/22RADBValid

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.