bgpreport

Network · data from 2026-11-12

AS26792 CSS Communications

Registry name: CSSNW - CSS Integration, Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS26792, 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.
2604:3c80:47:192::180/123 No ROA Nonecovered by 2604:3c80::/32 2 0%low visibility 2
2604:3c80:48:192::180/123 No ROA Nonecovered by 2604:3c80::/32 2 0%low visibility 2
2604:3c80:1000::a/128 No ROA Nonecovered by 2604:3c80::/32 2 0%low visibility 2
69.7.32.0/19 No ROA RIR databaseARIN, RIPE-NONAUTH 673 100% 67
2604:3c80::/32 No ROA RIR databaseARIN, RIPE-NONAUTH 359 56% 65

AS-SET

PeeringDB's irr_as_set for AS26792: as26792. 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 (AS26792 isn't in the set, or no route object for AS26792 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 objectsAS26792 in itNot covered
as26792 A single AS number, not a set: AS26792 (this network), 2 route objects.

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

  • ROA: none5
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: none2604:3c80:47:192::180/123No ROA covers it. Add a ROA for AS26792, maxLength 123.2 of 636
Route object: none2604:3c80:47:192::180/123No route object for it. A route object for 2604:3c80::/32 with origin AS26792 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS26792 in the RIR database for the space.2 of 636
ROA: none2604:3c80:48:192::180/123No ROA covers it. Add a ROA for AS26792, maxLength 123.2 of 636
Route object: none2604:3c80:48:192::180/123No route object for it. A route object for 2604:3c80::/32 with origin AS26792 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS26792 in the RIR database for the space.2 of 636
ROA: none2604:3c80:1000::a/128No ROA covers it. Add a ROA for AS26792, maxLength 128.2 of 636
Route object: none2604:3c80:1000::a/128No route object for it. A route object for 2604:3c80::/32 with origin AS26792 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS26792 in the RIR database for the space.2 of 636
ROA: none69.7.32.0/19No ROA covers it. Add a ROA for AS26792, maxLength 19.673 of 673
ROA: none2604:3c80::/32No ROA covers it. Add a ROA for AS26792, maxLength 32.359 of 636

Route objects not announced

Every route object with origin AS26792 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.