Network · data from 2026-11-12

AS271489 C V DE MELO FNET

Registry name: AS271489 - C V DE MELO FNET, BR · PeeringDB

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

2IPv6 routes 100.0% RPKI valid · 50.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 3 with no route object for this origin

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

1Route objects not announced registered with origin AS271489, seen from no peer

Announced routes

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


181.232.202.0/24	Valid	Nonecovered by 181.232.200.0/22	672 100%	67
181.232.203.0/24	Valid	Nonecovered by 181.232.200.0/22	671 100%	67
2804:7c54:8000::/33	Valid	Nonecovered by 2804:7c54::/32	636 100%	67
181.232.200.0/22	Valid	Other IRR onlyRADB, TC	672 100%	67
2804:7c54::/32	Valid	Other IRR onlyALTDB, RADB, TC	636 100%	67

AS-SET

AS271489's PeeringDB record names no 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 6 are in fix.csv.

Route object: none3
Route object: RIR2
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
Route object: none	181.232.202.0/24	No route object for it. A route object for 181.232.200.0/22 with origin AS271489 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271489 in the RIR database for the space.	672 of 673
Route object: none	181.232.203.0/24	No route object for it. A route object for 181.232.200.0/22 with origin AS271489 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271489 in the RIR database for the space.	671 of 673
Route object: none	2804:7c54:8000::/33	No route object for it. A route object for 2804:7c54::/32 with origin AS271489 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271489 in the RIR database for the space.	636 of 636
Route object: RIR	181.232.200.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	2804:7c54::/32	Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.	636 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

181.232.202.0/24

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

672 of 673

Route object: none

181.232.203.0/24

671 of 673

Route object: none

2804:7c54:8000::/33

No route object for it. A route object for 2804:7c54::/32 with origin AS271489 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271489 in the RIR database for the space.

636 of 636

Route object: RIR

181.232.200.0/22

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

672 of 673

Route object: RIR

2804:7c54::/32

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

636 of 636

Route objects not announced

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


2804:7c48::/32	ALTDB	No ROA

2804:7c48::/32

ALTDB

No 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.