bgpreport

Network · data from 2026-11-12

AS264299 Vero Internet AS264299

Registry name: AS264299 - VERO S.A, BR · PeeringDB

14IPv4 routes 100.0% RPKI valid · 100.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 0 with no route object for this origin
8Low visibility seen by under 10% of full-table peers
21Route objects not announced registered with origin AS264299, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS264299, 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.
138.121.152.0/22 Valid Other IRR onlyRADB, TC 666 99% 67
170.254.20.0/22 Valid Other IRR onlyRADB, TC 665 99% 67
2804:25bc::/32 Valid Other IRR onlyRADB, TC 631 99% 67
138.121.152.0/23 Valid Other IRR onlyTC 121 18% 41
138.121.154.0/23 Valid Other IRR onlyTC 121 18% 41
170.254.20.0/23 Valid Other IRR onlyTC 121 18% 41
170.254.22.0/23 Valid Other IRR onlyTC 121 18% 41
138.121.152.0/24 Valid Other IRR onlyTC 3 0%low visibility 2
138.121.153.0/24 Valid Other IRR onlyTC 3 0%low visibility 2
138.121.154.0/24 Valid Other IRR onlyTC 3 0%low visibility 2
138.121.155.0/24 Valid Other IRR onlyTC 3 0%low visibility 2
170.254.20.0/24 Valid Other IRR onlyTC 3 0%low visibility 2
170.254.21.0/24 Valid Other IRR onlyTC 3 0%low visibility 2
170.254.22.0/24 Valid Other IRR onlyTC 3 0%low visibility 2
170.254.23.0/24 Valid Other IRR onlyTC 3 0%low visibility 2

AS-SET

AS264299'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 36 are in fix.csv.

  • Route object: RIR15
  • Route object: not announced21
ChangePrefix or setDetailFull-table peers
Route object: RIR138.121.152.0/22Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
Route object: RIR170.254.20.0/22Route object only in RADB, TC. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:25bc::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR138.121.152.0/23Route object only in TC. Add it in the RIR database for the space.121 of 673
Route object: RIR138.121.154.0/23Route object only in TC. Add it in the RIR database for the space.121 of 673
Route object: RIR170.254.20.0/23Route object only in TC. Add it in the RIR database for the space.121 of 673
Route object: RIR170.254.22.0/23Route object only in TC. Add it in the RIR database for the space.121 of 673
Route object: RIR138.121.152.0/24Route object only in TC. Add it in the RIR database for the space.3 of 673
Route object: RIR138.121.153.0/24Route object only in TC. Add it in the RIR database for the space.3 of 673
Route object: RIR138.121.154.0/24Route object only in TC. Add it in the RIR database for the space.3 of 673
Route object: RIR138.121.155.0/24Route object only in TC. Add it in the RIR database for the space.3 of 673
Route object: RIR170.254.20.0/24Route object only in TC. Add it in the RIR database for the space.3 of 673
Route object: RIR170.254.21.0/24Route object only in TC. Add it in the RIR database for the space.3 of 673
Route object: RIR170.254.22.0/24Route object only in TC. Add it in the RIR database for the space.3 of 673
Route object: RIR170.254.23.0/24Route object only in TC. Add it in the RIR database for the space.3 of 673

Route objects not announced

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

2804:25bc::/48TCValid
2804:25bc:1::/48TCValid
2804:25bc:2::/48TCValid
2804:25bc:3::/48TCValid
2804:25bc:4::/48TCValid
2804:25bc:5::/48TCValid
2804:25bc:6::/48TCValid
2804:25bc:7::/48TCValid
2804:25bc:8::/48TCValid
2804:25bc:9::/48TCValid
2804:25bc:10::/48TCValid
2804:25bc:11::/48TCValid
2804:25bc:12::/48TCValid
2804:25bc:13::/48TCValid
2804:25bc:14::/48TCValid
2804:25bc:15::/48TCValid
2804:25bc:16::/48TCValid
2804:25bc:17::/48TCValid
2804:25bc:18::/48TCValid
2804:25bc:19::/48TCValid
2804:25bc:20::/48TCValid

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.