bgpreport

Network · data from 2026-11-12

AS53191 Vero Internet AS53191

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

21IPv4 routes 100.0% RPKI valid · 71.4% with a route object
6IPv6 routes 100.0% RPKI valid · 66.7% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 8 with no route object for this origin
12Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS53191, seen from no peer

Announced routes

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

177.8.216.0/22 Valid None 668 99% 67
2804:f2c::/32 Valid None 631 99% 67
2804:f2c:1800::/37 Valid None 332 52% 65
177.8.216.0/23 Valid None 127 19% 44
186.232.128.0/23 Valid Nonecovered by 186.232.128.0/22 127 19% 44
186.232.130.0/23 Valid Nonecovered by 186.232.128.0/22 127 19% 44
186.232.132.0/23 Valid Nonecovered by 186.232.132.0/22 127 19% 44
186.232.134.0/23 Valid Nonecovered by 186.232.132.0/22 127 19% 44
186.232.128.0/21 Valid Other IRR onlyTC 668 99% 67
186.232.128.0/22 Valid Other IRR onlyRADB 668 99% 67
2804:f2c:2800::/37 Valid Other IRR onlyRADB 333 52% 65
2804:f2c:3000::/37 Valid Other IRR onlyRADB 333 52% 65
2804:f2c:4800::/37 Valid Other IRR onlyRADB 328 52% 65
2804:f2c:1000::/37 Valid Other IRR onlyRADB 327 51% 65
177.8.218.0/23 Valid Other IRR onlyRADB 127 19% 44
177.8.216.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3
177.8.217.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3
177.8.218.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3
177.8.219.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3
186.232.128.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3
186.232.129.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3
186.232.130.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3
186.232.131.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3
186.232.132.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3
186.232.133.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3
186.232.134.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3
186.232.135.0/24 Valid Other IRR onlyRADB 5 1%low visibility 3

AS-SET

PeeringDB's irr_as_set for AS53191: AS-VERO-INTERNET-CUSTOMER. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS53191 isn't in the set, or no route object for AS53191 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS53191 in itNot covered
AS-VERO-INTERNET-CUSTOMER In no IRR database read today.

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 31 are in fix.csv.

  • Route object: none8
  • Route object: RIR19
  • AS-SET: not found1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none177.8.216.0/22No route object for it. Add a route object with origin AS53191 in the RIR database for the space.668 of 673
Route object: none2804:f2c::/32No route object for it. Add a route object with origin AS53191 in the RIR database for the space.631 of 636
Route object: none2804:f2c:1800::/37No route object for it. Add a route object with origin AS53191 in the RIR database for the space.332 of 636
Route object: none177.8.216.0/23No route object for it. Add a route object with origin AS53191 in the RIR database for the space.127 of 673
Route object: none186.232.128.0/23No route object for it. A route object for 186.232.128.0/22 with origin AS53191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53191 in the RIR database for the space.127 of 673
Route object: none186.232.130.0/23No route object for it. A route object for 186.232.128.0/22 with origin AS53191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53191 in the RIR database for the space.127 of 673
Route object: none186.232.132.0/23No route object for it. A route object for 186.232.132.0/22 with origin AS53191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53191 in the RIR database for the space.127 of 673
Route object: none186.232.134.0/23No route object for it. A route object for 186.232.132.0/22 with origin AS53191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53191 in the RIR database for the space.127 of 673
Route object: RIR186.232.128.0/21Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR186.232.128.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:f2c:2800::/37Route object only in RADB. Add it in the RIR database for the space.333 of 636
Route object: RIR2804:f2c:3000::/37Route object only in RADB. Add it in the RIR database for the space.333 of 636
Route object: RIR2804:f2c:4800::/37Route object only in RADB. Add it in the RIR database for the space.328 of 636
Route object: RIR2804:f2c:1000::/37Route object only in RADB. Add it in the RIR database for the space.327 of 636
Route object: RIR177.8.218.0/23Route object only in RADB. Add it in the RIR database for the space.127 of 673
Route object: RIR177.8.216.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR177.8.217.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR177.8.218.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR177.8.219.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR186.232.128.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR186.232.129.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR186.232.130.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR186.232.131.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR186.232.132.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR186.232.133.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR186.232.134.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
Route object: RIR186.232.135.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
AS-SET: not foundAS-VERO-INTERNET-CUSTOMERPeeringDB names AS-VERO-INTERNET-CUSTOMER; no IRR database read has it.

Route objects not announced

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

186.232.132.0/22RADBValid
2804:f2c:4000::/37RADBValid
2804:f2c:5000::/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.