Network · data from 2026-11-12

AS266302 RENOVENET PROVEDOR INTERNET LTDA - ME

Registry name: AS266302 - RENOVENET TELECOMUNICACOES LTDA - ME, BR · PeeringDB

5IPv4 routes 100.0% RPKI valid · 20.0% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

0No ROA 4 with no route object for this origin

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

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

Announced routes

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


170.79.170.0/24	Valid	Nonecovered by 170.79.168.0/22	157 23%	52
170.79.168.0/24	Valid	Nonecovered by 170.79.168.0/22	154 23%	51
170.79.169.0/24	Valid	Nonecovered by 170.79.168.0/22	154 23%	51
170.79.171.0/24	Valid	Nonecovered by 170.79.168.0/22	154 23%	51
170.79.168.0/22	Valid	Other IRR onlyTC	672 100%	66
2804:35b8::/32	Valid	Other IRR onlyTC	634 100%	67

AS-SET

AS266302'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: none4
Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
Route object: none	170.79.170.0/24	No route object for it. A route object for 170.79.168.0/22 with origin AS266302 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266302 in the RIR database for the space.	157 of 673
Route object: none	170.79.168.0/24	No route object for it. A route object for 170.79.168.0/22 with origin AS266302 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266302 in the RIR database for the space.	154 of 673
Route object: none	170.79.169.0/24	No route object for it. A route object for 170.79.168.0/22 with origin AS266302 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266302 in the RIR database for the space.	154 of 673
Route object: none	170.79.171.0/24	No route object for it. A route object for 170.79.168.0/22 with origin AS266302 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266302 in the RIR database for the space.	154 of 673
Route object: RIR	170.79.168.0/22	Route object only in TC. Add it in the RIR database for the space.	672 of 673
Route object: RIR	2804:35b8::/32	Route object only in TC. Add it in the RIR database for the space.	634 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

170.79.170.0/24

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

157 of 673

Route object: none

170.79.168.0/24

154 of 673

Route object: none

170.79.169.0/24

154 of 673

Route object: none

170.79.171.0/24

154 of 673

Route object: RIR

170.79.168.0/22

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

672 of 673

Route object: RIR

2804:35b8::/32

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

634 of 636

Route objects not announced

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