bgpreport

Network · data from 2026-11-12

AS266949 Vero Internet AS266949

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

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

Announced routes

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

2804:45c8:8000::/44 Valid Nonecovered by 2804:45c8::/32 331 52% 65
2804:45c8:8200::/40 Valid Nonecovered by 2804:45c8::/32 331 52% 65
45.225.196.0/23 Valid Nonecovered by 45.225.196.0/22 127 19% 44
45.225.196.0/24 Valid Nonecovered by 45.225.196.0/22 5 1%low visibility 3
45.225.197.0/24 Valid Nonecovered by 45.225.196.0/22 5 1%low visibility 3
45.225.198.0/24 Valid Nonecovered by 45.225.196.0/22 5 1%low visibility 3
45.225.199.0/24 Valid Nonecovered by 45.225.196.0/22 5 1%low visibility 3
45.225.196.0/22 Valid Other IRR onlyTC 668 99% 67
2804:45c8::/32 Valid Other IRR onlyTC 631 99% 67

AS-SET

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

  • Route object: none7
  • Route object: RIR2
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
Route object: none2804:45c8:8000::/44No route object for it. A route object for 2804:45c8::/32 with origin AS266949 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266949 in the RIR database for the space.331 of 636
Route object: none2804:45c8:8200::/40No route object for it. A route object for 2804:45c8::/32 with origin AS266949 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266949 in the RIR database for the space.331 of 636
Route object: none45.225.196.0/23No route object for it. A route object for 45.225.196.0/22 with origin AS266949 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266949 in the RIR database for the space.127 of 673
Route object: none45.225.196.0/24No route object for it. A route object for 45.225.196.0/22 with origin AS266949 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266949 in the RIR database for the space.5 of 673
Route object: none45.225.197.0/24No route object for it. A route object for 45.225.196.0/22 with origin AS266949 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266949 in the RIR database for the space.5 of 673
Route object: none45.225.198.0/24No route object for it. A route object for 45.225.196.0/22 with origin AS266949 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266949 in the RIR database for the space.5 of 673
Route object: none45.225.199.0/24No route object for it. A route object for 45.225.196.0/22 with origin AS266949 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266949 in the RIR database for the space.5 of 673
Route object: RIR45.225.196.0/22Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:45c8::/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 AS266949 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.