Network · data from 2026-11-12

AS265974 Vero Internet AS265974

Registry name: AS265974 - VERO S.A, 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 AS265974, seen from no peer

Announced routes

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


164.163.212.0/24	Valid	Nonecovered by 164.163.212.0/22	667 99%	67
164.163.213.0/24	Valid	Nonecovered by 164.163.212.0/22	667 99%	67
164.163.215.0/24	Valid	Nonecovered by 164.163.212.0/22	667 99%	67
164.163.214.0/24	Valid	Nonecovered by 164.163.212.0/22	666 99%	67
164.163.212.0/22	Valid	Other IRR onlyALTDB, TC	667 99%	67
2804:40ac::/32	Valid	Other IRR onlyALTDB, RADB, TC	631 99%	67

AS-SET

AS265974'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	164.163.212.0/24	No route object for it. A route object for 164.163.212.0/22 with origin AS265974 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265974 in the RIR database for the space.	667 of 673
Route object: none	164.163.213.0/24	No route object for it. A route object for 164.163.212.0/22 with origin AS265974 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265974 in the RIR database for the space.	667 of 673
Route object: none	164.163.215.0/24	No route object for it. A route object for 164.163.212.0/22 with origin AS265974 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265974 in the RIR database for the space.	667 of 673
Route object: none	164.163.214.0/24	No route object for it. A route object for 164.163.212.0/22 with origin AS265974 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265974 in the RIR database for the space.	666 of 673
Route object: RIR	164.163.212.0/22	Route object only in ALTDB, TC. Add it in the RIR database for the space.	667 of 673
Route object: RIR	2804:40ac::/32	Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.	631 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

164.163.212.0/24

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

667 of 673

Route object: none

164.163.213.0/24

667 of 673

Route object: none

164.163.215.0/24

667 of 673

Route object: none

164.163.214.0/24

666 of 673

Route object: RIR

164.163.212.0/22

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

667 of 673

Route object: RIR

2804:40ac::/32

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

631 of 636

Route objects not announced

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