bgpreport

Network · data from 2026-11-12

AS806 SSC-299-806 - Shared Services Canada

Registry name: SSC-299-806 - Shared Services Canada, CA · not in PeeringDB

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

Announced routes

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

192.75.68.0/24 No ROA Other IRR onlyRADB 18 3%low visibility 17
198.73.135.0/24 No ROA Other IRR onlyRADB 18 3%low visibility 17
198.73.136.0/24 No ROA Other IRR onlyRADB 18 3%low visibility 17
199.212.16.0/24 No ROA Other IRR onlyRADB 18 3%low visibility 17
199.212.17.0/24 No ROA Other IRR onlyRADB 18 3%low visibility 17
199.212.19.0/24 No ROA Other IRR onlyRADB 18 3%low visibility 17
199.212.20.0/24 No ROA Other IRR onlyRADB 18 3%low visibility 17
199.212.21.0/24 No ROA Other IRR onlyRADB 18 3%low visibility 17
205.189.5.0/24 No ROA Other IRR onlyRADB 18 3%low visibility 17
205.189.6.0/24 No ROA Other IRR onlyRADB 18 3%low visibility 17
205.189.7.0/24 No ROA Other IRR onlyRADB 18 3%low visibility 17
205.189.9.0/24 No ROA Other IRR onlyRADB 18 3%low visibility 17
205.211.132.0/24 No ROA Other IRR onlyRADB 18 3%low visibility 17
205.211.133.0/24 No ROA Other IRR onlyRADB 18 3%low visibility 17
205.211.134.0/24 No ROA Other IRR onlyRADB 18 3%low visibility 17

AS-SET

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

  • ROA: none15
  • Route object: RIR15
  • Route object: not announced29
ChangePrefix or setDetailFull-table peers
ROA: none192.75.68.0/24No ROA covers it. Add a ROA for AS806, maxLength 24.18 of 673
Route object: RIR192.75.68.0/24Route object only in RADB. Add it in the RIR database for the space.18 of 673
ROA: none198.73.135.0/24No ROA covers it. Add a ROA for AS806, maxLength 24.18 of 673
Route object: RIR198.73.135.0/24Route object only in RADB. Add it in the RIR database for the space.18 of 673
ROA: none198.73.136.0/24No ROA covers it. Add a ROA for AS806, maxLength 24.18 of 673
Route object: RIR198.73.136.0/24Route object only in RADB. Add it in the RIR database for the space.18 of 673
ROA: none199.212.16.0/24No ROA covers it. Add a ROA for AS806, maxLength 24.18 of 673
Route object: RIR199.212.16.0/24Route object only in RADB. Add it in the RIR database for the space.18 of 673
ROA: none199.212.17.0/24No ROA covers it. Add a ROA for AS806, maxLength 24.18 of 673
Route object: RIR199.212.17.0/24Route object only in RADB. Add it in the RIR database for the space.18 of 673
ROA: none199.212.19.0/24No ROA covers it. Add a ROA for AS806, maxLength 24.18 of 673
Route object: RIR199.212.19.0/24Route object only in RADB. Add it in the RIR database for the space.18 of 673
ROA: none199.212.20.0/24No ROA covers it. Add a ROA for AS806, maxLength 24.18 of 673
Route object: RIR199.212.20.0/24Route object only in RADB. Add it in the RIR database for the space.18 of 673
ROA: none199.212.21.0/24No ROA covers it. Add a ROA for AS806, maxLength 24.18 of 673
Route object: RIR199.212.21.0/24Route object only in RADB. Add it in the RIR database for the space.18 of 673
ROA: none205.189.5.0/24No ROA covers it. Add a ROA for AS806, maxLength 24.18 of 673
Route object: RIR205.189.5.0/24Route object only in RADB. Add it in the RIR database for the space.18 of 673
ROA: none205.189.6.0/24No ROA covers it. Add a ROA for AS806, maxLength 24.18 of 673
Route object: RIR205.189.6.0/24Route object only in RADB. Add it in the RIR database for the space.18 of 673
ROA: none205.189.7.0/24No ROA covers it. Add a ROA for AS806, maxLength 24.18 of 673
Route object: RIR205.189.7.0/24Route object only in RADB. Add it in the RIR database for the space.18 of 673
ROA: none205.189.9.0/24No ROA covers it. Add a ROA for AS806, maxLength 24.18 of 673
Route object: RIR205.189.9.0/24Route object only in RADB. Add it in the RIR database for the space.18 of 673
ROA: none205.211.132.0/24No ROA covers it. Add a ROA for AS806, maxLength 24.18 of 673
Route object: RIR205.211.132.0/24Route object only in RADB. Add it in the RIR database for the space.18 of 673
ROA: none205.211.133.0/24No ROA covers it. Add a ROA for AS806, maxLength 24.18 of 673
Route object: RIR205.211.133.0/24Route object only in RADB. Add it in the RIR database for the space.18 of 673
ROA: none205.211.134.0/24No ROA covers it. Add a ROA for AS806, maxLength 24.18 of 673
Route object: RIR205.211.134.0/24Route object only in RADB. Add it in the RIR database for the space.18 of 673

Route objects not announced

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

131.235.0.0/16RADBNo ROA
131.235.0.0/24RADBNo ROA
142.98.224.0/24CANARIE, RADBNo ROA
142.98.227.0/24CANARIENo ROA
142.98.230.0/23CANARIE, RADBNo ROA
142.98.254.0/24CANARIENo ROA
142.135.0.0/16RADBNo ROA
142.135.0.0/24RADBNo ROA
192.16.240.0/20RADBNo ROA
192.16.240.0/24RADBNo ROA
192.16.241.0/24RADBNo ROA
192.16.242.0/24RADBNo ROA
192.16.243.0/24RADBNo ROA
192.16.244.0/24RADBNo ROA
192.16.245.0/24RADBNo ROA
192.16.246.0/24RADBNo ROA
192.16.247.0/24RADBNo ROA
192.16.248.0/24RADBNo ROA
192.16.249.0/24RADBNo ROA
192.16.250.0/24RADBNo ROA
192.16.251.0/24RADBNo ROA
192.16.252.0/24RADBNo ROA
192.16.253.0/24RADBNo ROA
192.16.254.0/24RADBNo ROA
192.16.255.0/24RADBNo ROA
199.212.18.0/24BELL, RADBNo ROA
205.189.8.0/24CANARIE, RADBNo ROA
205.189.10.0/24RADBNo ROA
205.189.11.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.