bgpreport

Network · data from 2026-11-12

AS21992 SSHA-ONE-ASN - Ontario Health

Registry name: SSHA-ONE-ASN - Ontario Health, CA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS21992, 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.42.176.0/20 No ROA Other origin only 673 100% 67
69.42.184.0/21 No ROA Other origin only 673 100% 67
76.75.128.0/19 No ROA Other origin only 673 100% 67
76.75.144.0/20 No ROA None 673 100% 67
76.75.160.0/19 No ROA Other origin only 673 100% 67
76.75.176.0/20 No ROA None 673 100% 67
199.212.118.0/24 No ROA Other IRR onlyRADB 671 100% 67
205.210.180.0/22 No ROA Other IRR onlyRADB 671 100% 67

AS-SET

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

  • ROA: none8
  • Route object: none6
  • Route object: RIR2
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none69.42.176.0/20No ROA covers it. Add a ROA for AS21992, maxLength 20.673 of 673
Route object: none69.42.176.0/20Route objects for it name AS19752. Add a route object with origin AS21992 in the RIR database for the space.673 of 673
ROA: none69.42.184.0/21No ROA covers it. Add a ROA for AS21992, maxLength 21.673 of 673
Route object: none69.42.184.0/21Route objects for it name AS19752. Add a route object with origin AS21992 in the RIR database for the space.673 of 673
ROA: none76.75.128.0/19No ROA covers it. Add a ROA for AS21992, maxLength 19.673 of 673
Route object: none76.75.128.0/19Route objects for it name AS19752. Add a route object with origin AS21992 in the RIR database for the space.673 of 673
ROA: none76.75.144.0/20No ROA covers it. Add a ROA for AS21992, maxLength 20.673 of 673
Route object: none76.75.144.0/20No route object for it. Add a route object with origin AS21992 in the RIR database for the space.673 of 673
ROA: none76.75.160.0/19No ROA covers it. Add a ROA for AS21992, maxLength 19.673 of 673
Route object: none76.75.160.0/19Route objects for it name AS19752. Add a route object with origin AS21992 in the RIR database for the space.673 of 673
ROA: none76.75.176.0/20No ROA covers it. Add a ROA for AS21992, maxLength 20.673 of 673
Route object: none76.75.176.0/20No route object for it. Add a route object with origin AS21992 in the RIR database for the space.673 of 673
ROA: none199.212.118.0/24No ROA covers it. Add a ROA for AS21992, maxLength 24.671 of 673
Route object: RIR199.212.118.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none205.210.180.0/22No ROA covers it. Add a ROA for AS21992, maxLength 22.671 of 673
Route object: RIR205.210.180.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

76.75.136.0/21RADBNo ROA
76.75.152.0/21RADBNo ROA
76.75.168.0/21RADBNo ROA
142.21.0.0/16RADBNo ROA
199.212.120.0/22RADBNo ROA
204.138.128.0/21RADBNo ROA
204.225.211.0/24RADBNo ROA
205.189.51.0/24RADBNo ROA
205.210.30.0/23RADBNo ROA
205.210.32.0/22RADBNo 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.