Network · data from 2026-11-12

AS275721 AS275721 - WN DA SILVA

Registry name: AS275721 - WN DA SILVA, BR · not in PeeringDB

0IPv4 routes

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

0RPKI invalid 0 origin · 0 maxLength

3No ROA 2 with no route object for this origin

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

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

Announced routes

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


2804:988c::/33	No ROA	Nonecovered by 2804:988c::/32	1 0%low visibility	1
2804:988c:8000::/33	No ROA	Nonecovered by 2804:988c::/32	1 0%low visibility	1
2804:988c::/32	No ROA	Other IRR onlyTC	1 0%low visibility	1

2804:988c::/33

No ROA

Nonecovered by 2804:988c::/32

1 0%low visibility

2804:988c:8000::/33

No ROA

Nonecovered by 2804:988c::/32

1 0%low visibility

2804:988c::/32

No ROA

Other IRR onlyTC

1 0%low visibility

AS-SET

AS275721 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 6 are in fix.csv.

ROA: none3
Route object: none2
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
ROA: none	2804:988c::/33	No ROA covers it. Add a ROA for AS275721, maxLength 33.	1 of 636
Route object: none	2804:988c::/33	No route object for it. A route object for 2804:988c::/32 with origin AS275721 covers it (filters allowing more-specifics accept it). Add a route object with origin AS275721 in the RIR database for the space.	1 of 636
ROA: none	2804:988c:8000::/33	No ROA covers it. Add a ROA for AS275721, maxLength 33.	1 of 636
Route object: none	2804:988c:8000::/33	No route object for it. A route object for 2804:988c::/32 with origin AS275721 covers it (filters allowing more-specifics accept it). Add a route object with origin AS275721 in the RIR database for the space.	1 of 636
ROA: none	2804:988c::/32	No ROA covers it. Add a ROA for AS275721, maxLength 32.	1 of 636
Route object: RIR	2804:988c::/32	Route object only in TC. Add it in the RIR database for the space.	1 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

2804:988c::/33

No ROA covers it. Add a ROA for AS275721, maxLength 33.

1 of 636

Route object: none

2804:988c::/33

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

1 of 636

ROA: none

2804:988c:8000::/33

No ROA covers it. Add a ROA for AS275721, maxLength 33.

1 of 636

Route object: none

2804:988c:8000::/33

1 of 636

ROA: none

2804:988c::/32

No ROA covers it. Add a ROA for AS275721, maxLength 32.

1 of 636

Route object: RIR

2804:988c::/32

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

1 of 636

Route objects not announced

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