bgpreport

Network · data from 2026-11-12

AS7741 CIBC World Markets

Registry name: CIBC-WORLD-MARKETS - CIBC World Markets, US · PeeringDB

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

Announced routes

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

159.231.95.0/24 No ROA Other IRR onlyRADB 672 100% 67
199.198.251.0/24 No ROA Other IRR onlyRADB 672 100% 67
199.198.238.0/24 No ROA RIR databaseARIN 673 100% 67

AS-SET

PeeringDB's irr_as_set for AS7741: ARIN::AS-CIBC. 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 (AS7741 isn't in the set, or no route object for AS7741 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 objectsAS7741 in itNot covered
ARIN::AS-CIBC ARIN 2111 Yes 0

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

  • ROA: none3
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none159.231.95.0/24No ROA covers it. Add a ROA for AS7741, maxLength 24.672 of 673
Route object: RIR159.231.95.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none199.198.251.0/24No ROA covers it. Add a ROA for AS7741, maxLength 24.672 of 673
Route object: RIR199.198.251.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none199.198.238.0/24No ROA covers it. Add a ROA for AS7741, maxLength 24.673 of 673

Route objects not announced

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

159.231.63.0/24RADBNo ROA
199.198.223.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.