Network · data from 2026-11-12

AS61880 AS61880 - Hospital de Clinicas de Porto Alegre

Registry name: AS61880 - Hospital de Clinicas de Porto Alegre, BR · not in PeeringDB

3IPv4 routes 0.0% RPKI valid · 33.3% with a route object

1IPv6 routes 0.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

4No ROA 2 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS61880, seen from no peer

Announced routes

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


131.0.16.0/23	No ROA	Nonecovered by 131.0.16.0/22	671 100%	66
131.0.18.0/23	No ROA	Nonecovered by 131.0.16.0/22	671 100%	66
131.0.16.0/22	No ROA	Other IRR onlyRADB	671 100%	67
2801:80:c10::/48	No ROA	Other IRR onlyRADB	636 100%	70

AS-SET

AS61880 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 8 are in fix.csv.

ROA: none4
Route object: none2
Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
ROA: none	131.0.16.0/23	No ROA covers it. Add a ROA for AS61880, maxLength 23.	671 of 673
Route object: none	131.0.16.0/23	No route object for it. A route object for 131.0.16.0/22 with origin AS61880 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61880 in the RIR database for the space.	671 of 673
ROA: none	131.0.18.0/23	No ROA covers it. Add a ROA for AS61880, maxLength 23.	671 of 673
Route object: none	131.0.18.0/23	No route object for it. A route object for 131.0.16.0/22 with origin AS61880 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61880 in the RIR database for the space.	671 of 673
ROA: none	131.0.16.0/22	No ROA covers it. Add a ROA for AS61880, maxLength 22.	671 of 673
Route object: RIR	131.0.16.0/22	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
ROA: none	2801:80:c10::/48	No ROA covers it. Add a ROA for AS61880, maxLength 48.	636 of 636
Route object: RIR	2801:80:c10::/48	Route object only in RADB. Add it in the RIR database for the space.	636 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

131.0.16.0/23

No ROA covers it. Add a ROA for AS61880, maxLength 23.

671 of 673

Route object: none

131.0.16.0/23

No route object for it. A route object for 131.0.16.0/22 with origin AS61880 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61880 in the RIR database for the space.

671 of 673

ROA: none

131.0.18.0/23

No ROA covers it. Add a ROA for AS61880, maxLength 23.

671 of 673

Route object: none

131.0.18.0/23

671 of 673

ROA: none

131.0.16.0/22

No ROA covers it. Add a ROA for AS61880, maxLength 22.

671 of 673

Route object: RIR

131.0.16.0/22

Route object only in RADB. Add it in the RIR database for the space.

671 of 673

ROA: none

2801:80:c10::/48

No ROA covers it. Add a ROA for AS61880, maxLength 48.

636 of 636

Route object: RIR

2801:80:c10::/48

Route object only in RADB. Add it in the RIR database for the space.

636 of 636

Route objects not announced

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