bgpreport

Network · data from 2026-11-12

AS267430 AS267430 - CBR TELECOMUNICACOES LTDA

Registry name: AS267430 - CBR TELECOMUNICACOES LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267430, 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:4164:164::/48 Valid Nonecovered by 2804:4164::/32 635 100% 67
2804:4164:224::/48 Valid Nonecovered by 2804:4164::/32 635 100% 67
2804:4164:4100::/40 Valid Nonecovered by 2804:4164::/32 635 100% 67
2804:4164:2023::/48 Valid Nonecovered by 2804:4164::/32 634 100% 67
2804:4164:4000::/40 Valid Nonecovered by 2804:4164::/32 634 100% 67
164.163.224.0/22 Valid Other IRR onlyRADB 672 100% 66
164.163.224.0/24 Valid Other IRR onlyRADB 672 100% 66
164.163.225.0/24 Valid Other IRR onlyRADB 672 100% 66
164.163.227.0/24 Valid Other IRR onlyRADB 672 100% 66
164.163.226.0/24 Valid Other IRR onlyRADB 671 100% 66
2804:4164::/32 Valid Other IRR onlyRADB 630 99% 67

AS-SET

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

  • Route object: none5
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
Route object: none2804:4164:164::/48No route object for it. A route object for 2804:4164::/32 with origin AS267430 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267430 in the RIR database for the space.635 of 636
Route object: none2804:4164:224::/48No route object for it. A route object for 2804:4164::/32 with origin AS267430 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267430 in the RIR database for the space.635 of 636
Route object: none2804:4164:4100::/40No route object for it. A route object for 2804:4164::/32 with origin AS267430 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267430 in the RIR database for the space.635 of 636
Route object: none2804:4164:2023::/48No route object for it. A route object for 2804:4164::/32 with origin AS267430 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267430 in the RIR database for the space.634 of 636
Route object: none2804:4164:4000::/40No route object for it. A route object for 2804:4164::/32 with origin AS267430 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267430 in the RIR database for the space.634 of 636
Route object: RIR164.163.224.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR164.163.224.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR164.163.225.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR164.163.227.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR164.163.226.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:4164::/32Route object only in RADB. Add it in the RIR database for the space.630 of 636

Route objects not announced

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