bgpreport

Network · data from 2026-11-12

AS2682 Shared Services Canada (AS2682)

Registry name: CDAGOVN - Shared Services Canada, CA · PeeringDB

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

Announced routes

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

142.98.254.0/24 No ROA Other IRR onlyRADB 671 100% 68
205.194.26.0/23 No ROA Other IRR onlyCANARIE, RADB 671 100% 68
205.194.30.0/23 No ROA Other IRR onlyCANARIE, RADB 671 100% 68
205.194.32.0/23 No ROA Other IRR onlyCANARIE, RADB 671 100% 68
142.98.224.0/24 No ROA Other IRR onlyRADB 670 100% 68
142.98.227.0/24 No ROA Other IRR onlyRADB 670 100% 68
142.98.230.0/23 No ROA Other IRR onlyRADB 670 100% 68

AS-SET

AS2682's PeeringDB record names no 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 45 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced31
ChangePrefix or setDetailFull-table peers
ROA: none142.98.254.0/24No ROA covers it. Add a ROA for AS2682, maxLength 24.671 of 673
Route object: RIR142.98.254.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none205.194.26.0/23No ROA covers it. Add a ROA for AS2682, maxLength 23.671 of 673
Route object: RIR205.194.26.0/23Route object only in CANARIE, RADB. Add it in the RIR database for the space.671 of 673
ROA: none205.194.30.0/23No ROA covers it. Add a ROA for AS2682, maxLength 23.671 of 673
Route object: RIR205.194.30.0/23Route object only in CANARIE, RADB. Add it in the RIR database for the space.671 of 673
ROA: none205.194.32.0/23No ROA covers it. Add a ROA for AS2682, maxLength 23.671 of 673
Route object: RIR205.194.32.0/23Route object only in CANARIE, RADB. Add it in the RIR database for the space.671 of 673
ROA: none142.98.224.0/24No ROA covers it. Add a ROA for AS2682, maxLength 24.670 of 673
Route object: RIR142.98.224.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none142.98.227.0/24No ROA covers it. Add a ROA for AS2682, maxLength 24.670 of 673
Route object: RIR142.98.227.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none142.98.230.0/23No ROA covers it. Add a ROA for AS2682, maxLength 23.670 of 673
Route object: RIR142.98.230.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

131.136.0.0/16RADBNo ROA
132.156.10.0/23RADBNo ROA
132.156.12.0/23RADBNo ROA
132.156.16.0/23RADBNo ROA
132.156.20.0/22RADBNo ROA
132.156.46.0/23RADBNo ROA
132.156.120.0/23RADBNo ROA
132.246.0.0/16RADBNo ROA
132.246.0.0/17RADBNo ROA
132.246.128.0/18RADBNo ROA
132.246.172.0/23RADBNo ROA
132.246.192.0/19RADBNo ROA
132.246.224.0/19RADBNo ROA
142.92.0.0/16RADBNo ROA
167.37.244.0/24RADBNo ROA
167.37.245.0/24RADBNo ROA
167.37.246.0/24RADBNo ROA
167.37.247.0/24RADBNo ROA
167.37.249.0/26RADBNo ROA
167.37.249.64/26RADBNo ROA
167.37.249.128/26RADBNo ROA
192.70.172.0/24RADBNo ROA
192.75.14.0/24RADBNo ROA
192.75.72.0/24RADBNo ROA
192.139.21.0/24RADBNo ROA
192.139.116.0/23RADBNo ROA
199.212.212.0/24CANARIEInvalid: origin
204.174.103.0/24RADBNo ROA
205.189.8.0/24RADBNo ROA
205.194.34.0/24CANARIENo ROA
205.194.35.0/24CANARIENo 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.