Network · data from 2026-11-12

AS270308 AS270308 - MUNICIPIO DE MACAE

Registry name: AS270308 - MUNICIPIO DE MACAE, 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 AS270308, seen from no peer

Announced routes

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


200.0.202.0/24	No ROA	Nonecovered by 200.0.202.0/23	670 100%	67
200.0.203.0/24	No ROA	Nonecovered by 200.0.202.0/23	670 100%	67
200.0.202.0/23	No ROA	Other IRR onlyRADB	670 100%	67
2801:80:3870::/48	No ROA	Other IRR onlyRADB	633 100%	67

AS-SET

AS270308 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	200.0.202.0/24	No ROA covers it. Add a ROA for AS270308, maxLength 24.	670 of 673
Route object: none	200.0.202.0/24	No route object for it. A route object for 200.0.202.0/23 with origin AS270308 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270308 in the RIR database for the space.	670 of 673
ROA: none	200.0.203.0/24	No ROA covers it. Add a ROA for AS270308, maxLength 24.	670 of 673
Route object: none	200.0.203.0/24	No route object for it. A route object for 200.0.202.0/23 with origin AS270308 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270308 in the RIR database for the space.	670 of 673
ROA: none	200.0.202.0/23	No ROA covers it. Add a ROA for AS270308, maxLength 23.	670 of 673
Route object: RIR	200.0.202.0/23	Route object only in RADB. Add it in the RIR database for the space.	670 of 673
ROA: none	2801:80:3870::/48	No ROA covers it. Add a ROA for AS270308, maxLength 48.	633 of 636
Route object: RIR	2801:80:3870::/48	Route object only in RADB. Add it in the RIR database for the space.	633 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

200.0.202.0/24

No ROA covers it. Add a ROA for AS270308, maxLength 24.

670 of 673

Route object: none

200.0.202.0/24

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

670 of 673

ROA: none

200.0.203.0/24

No ROA covers it. Add a ROA for AS270308, maxLength 24.

670 of 673

Route object: none

200.0.203.0/24

670 of 673

ROA: none

200.0.202.0/23

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

670 of 673

Route object: RIR

200.0.202.0/23

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

670 of 673

ROA: none

2801:80:3870::/48

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

633 of 636

Route object: RIR

2801:80:3870::/48

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

633 of 636

Route objects not announced

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