bgpreport

Network · data from 2026-11-12

AS396402 MULTICARE-HEALTH-SYSTEM - MultiCare Health System

Registry name: MULTICARE-HEALTH-SYSTEM - MultiCare Health System, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS396402, 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.
199.79.97.0/24 No ROA None 673 100% 67
199.79.64.0/18 No ROA None 668 99% 67
199.79.88.0/24 No ROA Other origin only 668 99% 67
199.79.73.0/24 No ROA Other IRR onlyRADB 673 100% 67
199.79.98.0/24 No ROA Other IRR onlyRADB 673 100% 67
199.79.112.0/21 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS396402 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 12 are in fix.csv.

  • ROA: none6
  • Route object: none3
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none199.79.97.0/24No ROA covers it. Add a ROA for AS396402, maxLength 24.673 of 673
Route object: none199.79.97.0/24No route object for it. Add a route object with origin AS396402 in the RIR database for the space.673 of 673
ROA: none199.79.64.0/18No ROA covers it. Add a ROA for AS396402, maxLength 18.668 of 673
Route object: none199.79.64.0/18No route object for it. Add a route object with origin AS396402 in the RIR database for the space.668 of 673
ROA: none199.79.88.0/24No ROA covers it. Add a ROA for AS396402, maxLength 24.668 of 673
Route object: none199.79.88.0/24Route objects for it name AS14677. Add a route object with origin AS396402 in the RIR database for the space.668 of 673
ROA: none199.79.73.0/24No ROA covers it. Add a ROA for AS396402, maxLength 24.673 of 673
Route object: RIR199.79.73.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none199.79.98.0/24No ROA covers it. Add a ROA for AS396402, maxLength 24.673 of 673
Route object: RIR199.79.98.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none199.79.112.0/21No ROA covers it. Add a ROA for AS396402, maxLength 21.673 of 673
Route object: RIR199.79.112.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS396402 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.