bgpreport

Network · data from 2026-11-12

AS22213 SALK-AS - Salk Institute

Registry name: SALK-AS - Salk Institute, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22213, 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.
153.105.81.0/24 No ROA Other IRR onlyRADB 669 99% 68
192.31.153.0/24 No ROA Other IRR onlyRADB 669 99% 68
198.186.182.0/24 No ROA Other IRR onlyRADB 669 99% 68
198.202.65.0/24 No ROA Other IRR onlyRADB 669 99% 68
198.202.66.0/24 No ROA Other IRR onlyRADB 669 99% 68
198.202.67.0/24 No ROA Other IRR onlyRADB 669 99% 68
198.202.68.0/24 No ROA Other IRR onlyRADB 669 99% 68
198.202.69.0/24 No ROA Other IRR onlyRADB 669 99% 68
198.202.70.0/24 No ROA Other IRR onlyRADB 669 99% 68

AS-SET

AS22213 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 18 are in fix.csv.

  • ROA: none9
  • Route object: RIR9
ChangePrefix or setDetailFull-table peers
ROA: none153.105.81.0/24No ROA covers it. Add a ROA for AS22213, maxLength 24.669 of 673
Route object: RIR153.105.81.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none192.31.153.0/24No ROA covers it. Add a ROA for AS22213, maxLength 24.669 of 673
Route object: RIR192.31.153.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none198.186.182.0/24No ROA covers it. Add a ROA for AS22213, maxLength 24.669 of 673
Route object: RIR198.186.182.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none198.202.65.0/24No ROA covers it. Add a ROA for AS22213, maxLength 24.669 of 673
Route object: RIR198.202.65.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none198.202.66.0/24No ROA covers it. Add a ROA for AS22213, maxLength 24.669 of 673
Route object: RIR198.202.66.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none198.202.67.0/24No ROA covers it. Add a ROA for AS22213, maxLength 24.669 of 673
Route object: RIR198.202.67.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none198.202.68.0/24No ROA covers it. Add a ROA for AS22213, maxLength 24.669 of 673
Route object: RIR198.202.68.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none198.202.69.0/24No ROA covers it. Add a ROA for AS22213, maxLength 24.669 of 673
Route object: RIR198.202.69.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none198.202.70.0/24No ROA covers it. Add a ROA for AS22213, maxLength 24.669 of 673
Route object: RIR198.202.70.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

Every route object with origin AS22213 is announced.

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.