bgpreport

Network · data from 2026-11-12

AS264557 Vale & Bonomo Telecomunicacoes Ltda - ME

Registry name: AS264557 - Vale & Vale Telecomunicacoes Ltda - ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264557, 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.
138.0.164.0/24 Valid Nonecovered by 138.0.164.0/22 671 100% 66
138.0.165.0/24 Valid Nonecovered by 138.0.164.0/22 671 100% 66
138.0.166.0/24 Valid Nonecovered by 138.0.164.0/22 670 100% 66
2804:217c::/33 Valid Nonecovered by 2804:217c::/32 630 99% 67
138.0.166.0/23 Valid Nonecovered by 138.0.164.0/22 2 0%low visibility 2
138.0.164.0/22 Valid Other IRR onlyRADB 672 100% 66
138.0.167.0/24 Valid Other IRR onlyRADB 672 100% 66
2804:217c::/32 Valid Other IRR onlyRADB 632 99% 67

AS-SET

AS264557's PeeringDB record names no 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 8 are in fix.csv.

  • Route object: none5
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
Route object: none138.0.164.0/24No route object for it. A route object for 138.0.164.0/22 with origin AS264557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264557 in the RIR database for the space.671 of 673
Route object: none138.0.165.0/24No route object for it. A route object for 138.0.164.0/22 with origin AS264557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264557 in the RIR database for the space.671 of 673
Route object: none138.0.166.0/24No route object for it. A route object for 138.0.164.0/22 with origin AS264557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264557 in the RIR database for the space.670 of 673
Route object: none2804:217c::/33No route object for it. A route object for 2804:217c::/32 with origin AS264557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264557 in the RIR database for the space.630 of 636
Route object: none138.0.166.0/23No route object for it. A route object for 138.0.164.0/22 with origin AS264557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264557 in the RIR database for the space.2 of 673
Route object: RIR138.0.164.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR138.0.167.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:217c::/32Route object only in RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

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