bgpreport

Network · data from 2026-11-12

AS263520 VOA TELECOMUNICACOES LTDA

Registry name: AS263520 - VOA TELECOMUNICACOES LTDA, BR · PeeringDB

23IPv4 routes 100.0% RPKI valid · 13.0% with a route object
7IPv6 routes 100.0% RPKI valid · 14.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 26 with no route object for this origin
8Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS263520, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS263520, 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.126.156.0/22 Valid Nonecovered by 177.126.152.0/21 672 100% 67
181.192.80.0/21 Valid Nonecovered by 181.192.80.0/20 672 100% 67
181.192.80.0/22 Valid Nonecovered by 181.192.80.0/20 672 100% 67
181.192.88.0/21 Valid Nonecovered by 181.192.80.0/20 672 100% 67
181.192.86.0/24 Valid Nonecovered by 181.192.80.0/20 671 100% 67
181.192.82.0/23 Valid Nonecovered by 181.192.80.0/20 211 31% 56
181.192.84.0/22 Valid Nonecovered by 181.192.80.0/20 211 31% 56
181.192.86.0/23 Valid Nonecovered by 181.192.80.0/20 211 31% 56
181.192.88.0/22 Valid Nonecovered by 181.192.80.0/20 211 31% 56
181.192.88.0/23 Valid Nonecovered by 181.192.80.0/20 211 31% 56
181.192.90.0/23 Valid Nonecovered by 181.192.80.0/20 211 31% 56
181.192.92.0/22 Valid Nonecovered by 181.192.80.0/20 211 31% 56
177.126.152.0/23 Valid Nonecovered by 177.126.152.0/22 210 31% 56
177.126.154.0/23 Valid Nonecovered by 177.126.152.0/22 210 31% 56
177.126.156.0/23 Valid Nonecovered by 177.126.152.0/21 210 31% 56
177.126.158.0/23 Valid Nonecovered by 177.126.152.0/21 210 31% 56
181.192.80.0/23 Valid Nonecovered by 181.192.80.0/20 210 31% 56
181.192.94.0/23 Valid Nonecovered by 181.192.80.0/20 210 31% 56
181.192.84.0/23 Valid Nonecovered by 181.192.80.0/20 43 6%low visibility 14
181.192.92.0/23 Valid Nonecovered by 181.192.80.0/20 43 6%low visibility 14
2804:1330::/33 Valid Nonecovered by 2804:1330::/32 34 5%low visibility 13
2804:1330:4000::/34 Valid Nonecovered by 2804:1330::/32 34 5%low visibility 13
2804:1330:8000::/33 Valid Nonecovered by 2804:1330::/32 34 5%low visibility 13
2804:1330:8000::/34 Valid Nonecovered by 2804:1330::/32 34 5%low visibility 13
2804:1330:c000::/34 Valid Nonecovered by 2804:1330::/32 34 5%low visibility 13
2804:1330::/34 Valid Nonecovered by 2804:1330::/32 31 5%low visibility 12
177.126.152.0/21 Valid Other IRR onlyALTDB, TC 672 100% 67
177.126.152.0/22 Valid Other IRR onlyRADB 672 100% 67
181.192.80.0/20 Valid Other IRR onlyALTDB, TC 672 100% 67
2804:1330::/32 Valid Other IRR onlyALTDB, TC 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS263520: AS263520:AS-ANNOUNCEMENTS. 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 (AS263520 isn't in the set, or no route object for AS263520 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 objectsAS263520 in itNot covered
AS263520:AS-ANNOUNCEMENTS TC 5242 Yes 0

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

  • Route object: none26
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
Route object: none177.126.156.0/22No route object for it. A route object for 177.126.152.0/21 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.672 of 673
Route object: none181.192.80.0/21No route object for it. A route object for 181.192.80.0/20 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.672 of 673
Route object: none181.192.80.0/22No route object for it. A route object for 181.192.80.0/20 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.672 of 673
Route object: none181.192.88.0/21No route object for it. A route object for 181.192.80.0/20 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.672 of 673
Route object: none181.192.86.0/24No route object for it. A route object for 181.192.80.0/20 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.671 of 673
Route object: none181.192.82.0/23No route object for it. A route object for 181.192.80.0/20 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.211 of 673
Route object: none181.192.84.0/22No route object for it. A route object for 181.192.80.0/20 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.211 of 673
Route object: none181.192.86.0/23No route object for it. A route object for 181.192.80.0/20 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.211 of 673
Route object: none181.192.88.0/22No route object for it. A route object for 181.192.80.0/20 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.211 of 673
Route object: none181.192.88.0/23No route object for it. A route object for 181.192.80.0/20 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.211 of 673
Route object: none181.192.90.0/23No route object for it. A route object for 181.192.80.0/20 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.211 of 673
Route object: none181.192.92.0/22No route object for it. A route object for 181.192.80.0/20 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.211 of 673
Route object: none177.126.152.0/23No route object for it. A route object for 177.126.152.0/22 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.210 of 673
Route object: none177.126.154.0/23No route object for it. A route object for 177.126.152.0/22 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.210 of 673
Route object: none177.126.156.0/23No route object for it. A route object for 177.126.152.0/21 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.210 of 673
Route object: none177.126.158.0/23No route object for it. A route object for 177.126.152.0/21 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.210 of 673
Route object: none181.192.80.0/23No route object for it. A route object for 181.192.80.0/20 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.210 of 673
Route object: none181.192.94.0/23No route object for it. A route object for 181.192.80.0/20 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.210 of 673
Route object: none181.192.84.0/23No route object for it. A route object for 181.192.80.0/20 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.43 of 673
Route object: none181.192.92.0/23No route object for it. A route object for 181.192.80.0/20 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.43 of 673
Route object: none2804:1330::/33No route object for it. A route object for 2804:1330::/32 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.34 of 636
Route object: none2804:1330:4000::/34No route object for it. A route object for 2804:1330::/32 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.34 of 636
Route object: none2804:1330:8000::/33No route object for it. A route object for 2804:1330::/32 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.34 of 636
Route object: none2804:1330:8000::/34No route object for it. A route object for 2804:1330::/32 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.34 of 636
Route object: none2804:1330:c000::/34No route object for it. A route object for 2804:1330::/32 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.34 of 636
Route object: none2804:1330::/34No route object for it. A route object for 2804:1330::/32 with origin AS263520 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263520 in the RIR database for the space.31 of 636
Route object: RIR177.126.152.0/21Route object only in ALTDB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.126.152.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR181.192.80.0/20Route object only in ALTDB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:1330::/32Route object only in ALTDB, TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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