bgpreport

Network · data from 2026-11-12

AS35843 Source Cable Ltd.

Registry name: AS-RCC-SCL - Rogers Communications, CA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS35843, 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.215.128.0/20 No ROA Nonecovered by 67.215.128.0/19 673 100% 67
24.53.224.0/20 No ROA Other IRR onlyRADB 673 100% 67
67.215.128.0/19 No ROA Other IRR onlyRADB 673 100% 67
207.210.0.0/18 No ROA Other IRR onlyRADB 673 100% 67
2604:1500::/32 No ROA Other IRR onlyALTDB, RADB 635 100% 70

AS-SET

PeeringDB's irr_as_set for AS35843: AS-SCL. 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 (AS35843 isn't in the set, or no route object for AS35843 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 objectsAS35843 in itNot covered
AS-SCL In no IRR database read today.

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

  • ROA: none5
  • Route object: none1
  • Route object: RIR4
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: none67.215.128.0/20No ROA covers it. Add a ROA for AS35843, maxLength 20.673 of 673
Route object: none67.215.128.0/20No route object for it. A route object for 67.215.128.0/19 with origin AS35843 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35843 in the RIR database for the space.673 of 673
ROA: none24.53.224.0/20No ROA covers it. Add a ROA for AS35843, maxLength 20.673 of 673
Route object: RIR24.53.224.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none67.215.128.0/19No ROA covers it. Add a ROA for AS35843, maxLength 19.673 of 673
Route object: RIR67.215.128.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none207.210.0.0/18No ROA covers it. Add a ROA for AS35843, maxLength 18.673 of 673
Route object: RIR207.210.0.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2604:1500::/32No ROA covers it. Add a ROA for AS35843, maxLength 32.635 of 636
Route object: RIR2604:1500::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.635 of 636
AS-SET: not foundAS-SCLPeeringDB names AS-SCL; no IRR database read has it.

Route objects not announced

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