bgpreport

Network · data from 2026-11-12

AS267404 Vero Internet AS267404

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

7IPv4 routes 100.0% RPKI valid · 57.1% with a route object
2IPv6 routes 100.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 5 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS267404, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS267404, 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.
45.234.240.0/22 Valid None 667 99% 67
2804:4cf8::/32 Valid None 631 99% 67
2804:4cf8:1800::/37 Valid None 332 52% 65
45.234.240.0/23 Valid None 127 19% 44
45.234.242.0/23 Valid None 127 19% 44
45.234.240.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3
45.234.241.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3
45.234.242.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3
45.234.243.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3

AS-SET

AS267404'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 10 are in fix.csv.

  • Route object: none5
  • Route object: RIR4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none45.234.240.0/22No route object for it. Add a route object with origin AS267404 in the RIR database for the space.667 of 673
Route object: none2804:4cf8::/32No route object for it. Add a route object with origin AS267404 in the RIR database for the space.631 of 636
Route object: none2804:4cf8:1800::/37No route object for it. Add a route object with origin AS267404 in the RIR database for the space.332 of 636
Route object: none45.234.240.0/23No route object for it. Add a route object with origin AS267404 in the RIR database for the space.127 of 673
Route object: none45.234.242.0/23No route object for it. Add a route object with origin AS267404 in the RIR database for the space.127 of 673
Route object: RIR45.234.240.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR45.234.241.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR45.234.242.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR45.234.243.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673

Route objects not announced

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

2804:4cf8:1000::/37RADBValid

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.