bgpreport

Network · data from 2026-11-12

AS54412 RCC-GRANITE-1 - Rogers Communications Canada Inc.

Registry name: RCC-GRANITE-1 - Rogers Communications Canada Inc., CA · not in PeeringDB

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

Announced routes

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

69.20.235.0/24 No ROA Nonecovered by 69.20.232.0/22 438 65% 62
2604:1f80::/32 No ROA Other IRR onlyALTDB, RADB 635 100% 70

AS-SET

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

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
ROA: none69.20.235.0/24No ROA covers it. Add a ROA for AS54412, maxLength 24.438 of 673
Route object: none69.20.235.0/24No route object for it. A route object for 69.20.232.0/22 with origin AS54412 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54412 in the RIR database for the space.438 of 673
ROA: none2604:1f80::/32No ROA covers it. Add a ROA for AS54412, maxLength 32.635 of 636
Route object: RIR2604:1f80::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

64.130.208.0/20RADBNo ROA
66.240.128.0/18RADBNo ROA
69.10.224.0/20RADBNo ROA
69.20.232.0/22RADBNo ROA
69.20.240.0/21RADBNo ROA
104.171.192.0/22RADBNo ROA
130.96.8.0/24RADBNo ROA
130.96.10.0/23RADBNo ROA
192.139.119.0/24RADBNo ROA
192.211.124.0/22ALTDBNo ROA
192.211.124.0/23ALTDBNo ROA
192.211.126.0/23ALTDBNo ROA
198.41.28.0/22ALTDBNo ROA
198.41.28.0/23ALTDBNo ROA
198.41.30.0/23ALTDBNo ROA
198.134.120.0/24RADBNo ROA
199.182.207.0/24RADBNo ROA
216.130.178.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.