bgpreport

Network · data from 2026-11-12

AS40479 AURORA-HEALTH-CARE - Aurora Health Care, Inc.

Registry name: AURORA-HEALTH-CARE - Aurora Health Care, Inc., US · not in PeeringDB

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

Announced routes

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

198.177.64.0/21 No ROA Nonecovered by 198.177.64.0/19 673 100% 67
198.177.64.0/23 No ROA Nonecovered by 198.177.64.0/19 673 100% 67
198.177.68.0/23 No ROA Nonecovered by 198.177.64.0/19 673 100% 67
198.177.70.0/24 No ROA Nonecovered by 198.177.64.0/19 673 100% 67
198.177.71.0/24 No ROA Nonecovered by 198.177.64.0/19 673 100% 67
198.177.76.0/23 No ROA Nonecovered by 198.177.72.0/21 673 100% 67
198.177.92.0/24 No ROA Nonecovered by 198.177.80.0/20 673 100% 67
198.177.94.0/23 No ROA Nonecovered by 198.177.80.0/20 673 100% 67
198.177.67.0/24 No ROA Nonecovered by 198.177.64.0/19 668 99% 67
198.177.72.0/21 No ROA Other IRR onlyRADB 673 100% 67
198.177.80.0/20 No ROA Other IRR onlyRADB 673 100% 67
198.177.93.0/24 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS40479 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 27 are in fix.csv.

  • ROA: none12
  • Route object: none9
  • Route object: RIR3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none198.177.64.0/21No ROA covers it. Add a ROA for AS40479, maxLength 21.673 of 673
Route object: none198.177.64.0/21No route object for it. A route object for 198.177.64.0/19 with origin AS40479 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40479 in the RIR database for the space.673 of 673
ROA: none198.177.64.0/23No ROA covers it. Add a ROA for AS40479, maxLength 23.673 of 673
Route object: none198.177.64.0/23No route object for it. A route object for 198.177.64.0/19 with origin AS40479 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40479 in the RIR database for the space.673 of 673
ROA: none198.177.68.0/23No ROA covers it. Add a ROA for AS40479, maxLength 23.673 of 673
Route object: none198.177.68.0/23No route object for it. A route object for 198.177.64.0/19 with origin AS40479 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40479 in the RIR database for the space.673 of 673
ROA: none198.177.70.0/24No ROA covers it. Add a ROA for AS40479, maxLength 24.673 of 673
Route object: none198.177.70.0/24No route object for it. A route object for 198.177.64.0/19 with origin AS40479 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40479 in the RIR database for the space.673 of 673
ROA: none198.177.71.0/24No ROA covers it. Add a ROA for AS40479, maxLength 24.673 of 673
Route object: none198.177.71.0/24No route object for it. A route object for 198.177.64.0/19 with origin AS40479 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40479 in the RIR database for the space.673 of 673
ROA: none198.177.76.0/23No ROA covers it. Add a ROA for AS40479, maxLength 23.673 of 673
Route object: none198.177.76.0/23No route object for it. A route object for 198.177.72.0/21 with origin AS40479 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40479 in the RIR database for the space.673 of 673
ROA: none198.177.92.0/24No ROA covers it. Add a ROA for AS40479, maxLength 24.673 of 673
Route object: none198.177.92.0/24No route object for it. A route object for 198.177.80.0/20 with origin AS40479 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40479 in the RIR database for the space.673 of 673
ROA: none198.177.94.0/23No ROA covers it. Add a ROA for AS40479, maxLength 23.673 of 673
Route object: none198.177.94.0/23No route object for it. A route object for 198.177.80.0/20 with origin AS40479 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40479 in the RIR database for the space.673 of 673
ROA: none198.177.67.0/24No ROA covers it. Add a ROA for AS40479, maxLength 24.668 of 673
Route object: none198.177.67.0/24No route object for it. A route object for 198.177.64.0/19 with origin AS40479 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40479 in the RIR database for the space.668 of 673
ROA: none198.177.72.0/21No ROA covers it. Add a ROA for AS40479, maxLength 21.673 of 673
Route object: RIR198.177.72.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none198.177.80.0/20No ROA covers it. Add a ROA for AS40479, maxLength 20.673 of 673
Route object: RIR198.177.80.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none198.177.93.0/24No ROA covers it. Add a ROA for AS40479, maxLength 24.673 of 673
Route object: RIR198.177.93.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

198.177.64.0/19RADBNo ROA
198.177.96.0/20RADBNo ROA
198.177.112.0/23RADBNo 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.