bgpreport

Network · data from 2026-11-12

AS52906 AS52906 - VOXX TELECOM LTDA - ME

Registry name: AS52906 - VOXX TELECOM LTDA - ME, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52906, 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.23.56.0/23 Valid Nonecovered by 177.23.56.0/21 123 18% 44
177.23.58.0/23 Valid Nonecovered by 177.23.56.0/21 123 18% 44
177.23.60.0/23 Valid Nonecovered by 177.23.56.0/21 123 18% 44
177.23.62.0/23 Valid Nonecovered by 177.23.56.0/21 123 18% 44
177.23.56.0/21 Valid Other IRR onlyRADB, TC 670 100% 67
2804:8740::/32 Valid Other IRR onlyTC 635 100% 67

AS-SET

AS52906 isn't in PeeringDB, where networks name their 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 9 are in fix.csv.

  • Route object: none4
  • Route object: RIR2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none177.23.56.0/23No route object for it. A route object for 177.23.56.0/21 with origin AS52906 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52906 in the RIR database for the space.123 of 673
Route object: none177.23.58.0/23No route object for it. A route object for 177.23.56.0/21 with origin AS52906 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52906 in the RIR database for the space.123 of 673
Route object: none177.23.60.0/23No route object for it. A route object for 177.23.56.0/21 with origin AS52906 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52906 in the RIR database for the space.123 of 673
Route object: none177.23.62.0/23No route object for it. A route object for 177.23.56.0/21 with origin AS52906 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52906 in the RIR database for the space.123 of 673
Route object: RIR177.23.56.0/21Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:8740::/32Route object only in TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

177.23.57.0/24RADBValid
177.23.60.0/24RADBValid
177.23.63.0/24RADBValid

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.