bgpreport

Network · data from 2026-11-12

AS263072 Vero Internet AS263072

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

35IPv4 routes 100.0% RPKI valid · 5.7% with a route object
3IPv6 routes 100.0% RPKI valid · 33.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 35 with no route object for this origin
19Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS263072, seen from no peer

Announced routes

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

168.121.19.0/24 Valid Nonecovered by 168.121.16.0/22 668 99% 67
186.195.80.0/22 Valid Nonecovered by 186.195.80.0/20 668 99% 67
186.195.84.0/22 Valid Nonecovered by 186.195.80.0/20 668 99% 67
186.195.88.0/22 Valid Nonecovered by 186.195.80.0/20 668 99% 67
186.195.92.0/22 Valid Nonecovered by 186.195.80.0/20 668 99% 67
2804:950:8000::/44 Valid Nonecovered by 2804:950::/32 332 52% 65
2804:950:8100::/40 Valid Nonecovered by 2804:950::/32 332 52% 65
168.121.16.0/23 Valid Nonecovered by 168.121.16.0/22 127 19% 44
168.121.18.0/23 Valid Nonecovered by 168.121.16.0/22 127 19% 44
186.195.82.0/23 Valid Nonecovered by 186.195.80.0/20 127 19% 44
186.195.84.0/23 Valid Nonecovered by 186.195.80.0/20 127 19% 44
186.195.86.0/23 Valid Nonecovered by 186.195.80.0/20 127 19% 44
186.195.88.0/23 Valid Nonecovered by 186.195.80.0/20 127 19% 44
186.195.90.0/23 Valid Nonecovered by 186.195.80.0/20 127 19% 44
186.195.92.0/23 Valid Nonecovered by 186.195.80.0/20 127 19% 44
186.195.94.0/23 Valid Nonecovered by 186.195.80.0/20 127 19% 44
186.195.80.0/24 Valid Nonecovered by 186.195.80.0/20 5 1%low visibility 3
186.195.81.0/24 Valid Nonecovered by 186.195.80.0/20 5 1%low visibility 3
186.195.82.0/24 Valid Nonecovered by 186.195.80.0/20 5 1%low visibility 3
186.195.83.0/24 Valid Nonecovered by 186.195.80.0/20 5 1%low visibility 3
186.195.84.0/24 Valid Nonecovered by 186.195.80.0/20 5 1%low visibility 3
186.195.85.0/24 Valid Nonecovered by 186.195.80.0/20 5 1%low visibility 3
186.195.86.0/24 Valid Nonecovered by 186.195.80.0/20 5 1%low visibility 3
186.195.87.0/24 Valid Nonecovered by 186.195.80.0/20 5 1%low visibility 3
186.195.88.0/24 Valid Nonecovered by 186.195.80.0/20 5 1%low visibility 3
186.195.89.0/24 Valid Nonecovered by 186.195.80.0/20 5 1%low visibility 3
186.195.90.0/24 Valid Nonecovered by 186.195.80.0/20 5 1%low visibility 3
186.195.91.0/24 Valid Nonecovered by 186.195.80.0/20 5 1%low visibility 3
186.195.92.0/24 Valid Nonecovered by 186.195.80.0/20 5 1%low visibility 3
186.195.93.0/24 Valid Nonecovered by 186.195.80.0/20 5 1%low visibility 3
186.195.94.0/24 Valid Nonecovered by 186.195.80.0/20 5 1%low visibility 3
186.195.95.0/24 Valid Nonecovered by 186.195.80.0/20 5 1%low visibility 3
168.121.16.0/24 Valid Nonecovered by 168.121.16.0/22 4 1%low visibility 3
168.121.17.0/24 Valid Nonecovered by 168.121.16.0/22 4 1%low visibility 3
168.121.18.0/24 Valid Nonecovered by 168.121.16.0/22 4 1%low visibility 3
168.121.16.0/22 Valid Other IRR onlyTC 668 99% 67
186.195.80.0/20 Valid Other IRR onlyTC 668 99% 67
2804:950::/32 Valid Other IRR onlyTC 631 99% 67

AS-SET

PeeringDB's irr_as_set for AS263072: 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 (AS263072 isn't in the set, or no route object for AS263072 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 objectsAS263072 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 39 are in fix.csv.

  • Route object: none35
  • Route object: RIR3
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
Route object: none168.121.19.0/24No route object for it. A route object for 168.121.16.0/22 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.668 of 673
Route object: none186.195.80.0/22No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.668 of 673
Route object: none186.195.84.0/22No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.668 of 673
Route object: none186.195.88.0/22No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.668 of 673
Route object: none186.195.92.0/22No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.668 of 673
Route object: none2804:950:8000::/44No route object for it. A route object for 2804:950::/32 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.332 of 636
Route object: none2804:950:8100::/40No route object for it. A route object for 2804:950::/32 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.332 of 636
Route object: none168.121.16.0/23No route object for it. A route object for 168.121.16.0/22 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.127 of 673
Route object: none168.121.18.0/23No route object for it. A route object for 168.121.16.0/22 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.127 of 673
Route object: none186.195.82.0/23No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.127 of 673
Route object: none186.195.84.0/23No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.127 of 673
Route object: none186.195.86.0/23No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.127 of 673
Route object: none186.195.88.0/23No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.127 of 673
Route object: none186.195.90.0/23No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.127 of 673
Route object: none186.195.92.0/23No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.127 of 673
Route object: none186.195.94.0/23No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.127 of 673
Route object: none186.195.80.0/24No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.5 of 673
Route object: none186.195.81.0/24No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.5 of 673
Route object: none186.195.82.0/24No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.5 of 673
Route object: none186.195.83.0/24No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.5 of 673
Route object: none186.195.84.0/24No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.5 of 673
Route object: none186.195.85.0/24No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.5 of 673
Route object: none186.195.86.0/24No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.5 of 673
Route object: none186.195.87.0/24No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.5 of 673
Route object: none186.195.88.0/24No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.5 of 673
Route object: none186.195.89.0/24No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.5 of 673
Route object: none186.195.90.0/24No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.5 of 673
Route object: none186.195.91.0/24No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.5 of 673
Route object: none186.195.92.0/24No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.5 of 673
Route object: none186.195.93.0/24No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.5 of 673
Route object: none186.195.94.0/24No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.5 of 673
Route object: none186.195.95.0/24No route object for it. A route object for 186.195.80.0/20 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.5 of 673
Route object: none168.121.16.0/24No route object for it. A route object for 168.121.16.0/22 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.4 of 673
Route object: none168.121.17.0/24No route object for it. A route object for 168.121.16.0/22 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.4 of 673
Route object: none168.121.18.0/24No route object for it. A route object for 168.121.16.0/22 with origin AS263072 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263072 in the RIR database for the space.4 of 673
Route object: RIR168.121.16.0/22Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR186.195.80.0/20Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:950::/32Route object only in TC. Add it in the RIR database for the space.631 of 636
AS-SET: not foundAS-VERO-INTERNET-CUSTOMERPeeringDB names AS-VERO-INTERNET-CUSTOMER; no IRR database read has it.

Route objects not announced

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