Network · data from 2026-11-12

AS274359 Renan Quevedo Peres

Registry name: AS274359 - Renan Quevedo Peres, BR · PeeringDB

0IPv4 routes

3IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

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

12Route objects not announced registered with origin AS274359, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS274359, 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:96c8::/32	Valid	Other IRR onlyTC	634 100%	68
2804:96c8::/33	Valid	Other IRR onlyTC	10 2%low visibility	7
2804:96c8:8000::/33	Valid	Other IRR onlyTC	10 2%low visibility	7

2804:96c8::/32

Valid

Other IRR onlyTC

634 100%

2804:96c8::/33

Valid

Other IRR onlyTC

10 2%low visibility

2804:96c8:8000::/33

Valid

Other IRR onlyTC

10 2%low visibility

AS-SET

AS274359'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 15 are in fix.csv.

Route object: RIR3
Route object: not announced12

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	2804:96c8::/32	Route object only in TC. Add it in the RIR database for the space.	634 of 636
Route object: RIR	2804:96c8::/33	Route object only in TC. Add it in the RIR database for the space.	10 of 636
Route object: RIR	2804:96c8:8000::/33	Route object only in TC. Add it in the RIR database for the space.	10 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

2804:96c8::/32

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

634 of 636

Route object: RIR

2804:96c8::/33

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

10 of 636

Route object: RIR

2804:96c8:8000::/33

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

10 of 636

Route objects not announced

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


2804:96c8::/34	TC	Valid
2804:96c8::/35	TC	Valid
2804:96c8:2000::/35	TC	Valid
2804:96c8:4000::/34	TC	Valid
2804:96c8:4000::/35	TC	Valid
2804:96c8:6000::/35	TC	Valid
2804:96c8:8000::/34	TC	Valid
2804:96c8:8000::/35	TC	Valid
2804:96c8:a000::/35	TC	Valid
2804:96c8:c000::/34	TC	Valid
2804:96c8:c000::/35	TC	Valid
2804:96c8:e000::/35	TC	Valid

2804:96c8::/34

Valid

2804:96c8::/35

Valid

2804:96c8:2000::/35

Valid

2804:96c8:4000::/34

Valid

2804:96c8:4000::/35

Valid

2804:96c8:6000::/35

Valid

2804:96c8:8000::/34

Valid

2804:96c8:8000::/35

Valid

2804:96c8:a000::/35

Valid

2804:96c8:c000::/34

Valid

2804:96c8:c000::/35

Valid

2804:96c8:e000::/35

Valid

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.