bgpreport

Network · data from 2026-11-12

AS33359 COWEN

Registry name: COWEN-AS-3 - COWEN EXECUTION SERVICES LLC., US · PeeringDB

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

Announced routes

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

67.43.82.0/23 No ROA None 673 100% 67
67.43.84.0/23 No ROA None 673 100% 67
67.43.88.0/23 No ROA None 673 100% 67
67.43.82.0/24 Valid None 673 100% 67
67.43.89.0/24 Valid None 673 100% 67
208.89.28.0/24 Valid None 673 100% 67
208.89.29.0/24 Valid None 673 100% 67
67.43.93.0/24 Valid None 671 100% 67
67.43.80.0/24 Valid Other IRR onlyRADB 673 100% 67
67.43.85.0/24 Valid Other IRR onlyRADB 673 100% 67
67.43.83.0/24 Valid RIR databaseARIN, RADB 672 100% 67
67.43.84.0/24 Valid RIR databaseARIN, RADB 672 100% 67
67.43.88.0/24 Valid RIR databaseARIN, RADB 672 100% 67
67.43.91.0/24 Valid RIR databaseARIN 670 100% 67

AS-SET

PeeringDB's irr_as_set for AS33359: ARIN::RS-COWEN-US. 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 (AS33359 isn't in the set, or no route object for AS33359 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.

NameDatabaseASNsSets Route objectsAS33359 in itNot covered
ARIN::RS-COWEN-US A route-set, not an AS-SET; route-sets aren't expanded.

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

  • ROA: none3
  • Route object: none8
  • Route object: RIR2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none67.43.82.0/23No ROA covers it. Add a ROA for AS33359, maxLength 23.673 of 673
Route object: none67.43.82.0/23No route object for it. Add a route object with origin AS33359 in the RIR database for the space.673 of 673
ROA: none67.43.84.0/23No ROA covers it. Add a ROA for AS33359, maxLength 23.673 of 673
Route object: none67.43.84.0/23No route object for it. Add a route object with origin AS33359 in the RIR database for the space.673 of 673
ROA: none67.43.88.0/23No ROA covers it. Add a ROA for AS33359, maxLength 23.673 of 673
Route object: none67.43.88.0/23No route object for it. Add a route object with origin AS33359 in the RIR database for the space.673 of 673
Route object: none67.43.82.0/24No route object for it. Add a route object with origin AS33359 in the RIR database for the space.673 of 673
Route object: none67.43.89.0/24No route object for it. Add a route object with origin AS33359 in the RIR database for the space.673 of 673
Route object: none208.89.28.0/24No route object for it. Add a route object with origin AS33359 in the RIR database for the space.673 of 673
Route object: none208.89.29.0/24No route object for it. Add a route object with origin AS33359 in the RIR database for the space.673 of 673
Route object: none67.43.93.0/24No route object for it. Add a route object with origin AS33359 in the RIR database for the space.671 of 673
Route object: RIR67.43.80.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR67.43.85.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 AS33359 whose prefix no peer sees AS33359 announce. Many are kept on purpose (backup routes, space announced only in some places).

67.43.95.0/24ARIN, RADBValid
74.118.109.0/24RADBNo ROA
74.118.110.0/24RADBNo 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.