bgpreport

Network · data from 2026-11-12

AS2680 CDAGOVN - Shared Services Canada

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS2680, 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.
132.156.10.0/23 No ROA Other IRR onlyCANARIE 20 3%low visibility 18

AS-SET

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

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none132.156.10.0/23No ROA covers it. Add a ROA for AS2680, maxLength 23.20 of 673
Route object: RIR132.156.10.0/23Route object only in CANARIE. Add it in the RIR database for the space.20 of 673

Route objects not announced

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

192.197.81.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.