bgpreport

Network · data from 2026-11-12

AS265971 AS265971 - CRBC TELECOM LTDA ME

Registry name: AS265971 - CRBC TELECOM LTDA ME, BR · not in PeeringDB

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

Announced routes

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

164.163.196.0/24 Valid Nonecovered by 164.163.196.0/22 672 100% 66
164.163.197.0/24 Valid Nonecovered by 164.163.196.0/22 672 100% 66
164.163.198.0/24 Valid Nonecovered by 164.163.196.0/22 672 100% 66
164.163.199.0/24 Valid Nonecovered by 164.163.196.0/22 672 100% 66
164.163.196.0/23 Valid Nonecovered by 164.163.196.0/22 670 100% 67
164.163.198.0/23 Valid Nonecovered by 164.163.196.0/22 670 100% 67
2804:40a0:acc1::/48 Valid Nonecovered by 2804:40a0::/32 634 100% 67
2804:40a0:acc2::/48 Valid Nonecovered by 2804:40a0::/32 634 100% 67
2804:40a0:acc3::/48 Valid Nonecovered by 2804:40a0::/32 634 100% 67
2804:40a0:f100::/40 Valid Nonecovered by 2804:40a0::/32 634 100% 67
2804:40a0:f100::/41 Valid Nonecovered by 2804:40a0::/32 634 100% 67
2804:40a0:f180::/41 Valid Nonecovered by 2804:40a0::/32 634 100% 67
2804:40a0:f200::/40 Valid Nonecovered by 2804:40a0::/32 634 100% 67
2804:40a0:f200::/41 Valid Nonecovered by 2804:40a0::/32 634 100% 67
2804:40a0:f280::/41 Valid Nonecovered by 2804:40a0::/32 634 100% 67
2804:40a0:f300::/40 Valid Nonecovered by 2804:40a0::/32 634 100% 67
2804:40a0:f300::/41 Valid Nonecovered by 2804:40a0::/32 634 100% 67
2804:40a0:f380::/41 Valid Nonecovered by 2804:40a0::/32 634 100% 67
164.163.196.0/22 Valid Other IRR onlyRADB 672 100% 66
2804:40a0::/32 Valid Other IRR onlyRADB 635 100% 69

AS-SET

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

  • Route object: none18
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none164.163.196.0/24No route object for it. A route object for 164.163.196.0/22 with origin AS265971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265971 in the RIR database for the space.672 of 673
Route object: none164.163.197.0/24No route object for it. A route object for 164.163.196.0/22 with origin AS265971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265971 in the RIR database for the space.672 of 673
Route object: none164.163.198.0/24No route object for it. A route object for 164.163.196.0/22 with origin AS265971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265971 in the RIR database for the space.672 of 673
Route object: none164.163.199.0/24No route object for it. A route object for 164.163.196.0/22 with origin AS265971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265971 in the RIR database for the space.672 of 673
Route object: none164.163.196.0/23No route object for it. A route object for 164.163.196.0/22 with origin AS265971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265971 in the RIR database for the space.670 of 673
Route object: none164.163.198.0/23No route object for it. A route object for 164.163.196.0/22 with origin AS265971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265971 in the RIR database for the space.670 of 673
Route object: none2804:40a0:acc1::/48No route object for it. A route object for 2804:40a0::/32 with origin AS265971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265971 in the RIR database for the space.634 of 636
Route object: none2804:40a0:acc2::/48No route object for it. A route object for 2804:40a0::/32 with origin AS265971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265971 in the RIR database for the space.634 of 636
Route object: none2804:40a0:acc3::/48No route object for it. A route object for 2804:40a0::/32 with origin AS265971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265971 in the RIR database for the space.634 of 636
Route object: none2804:40a0:f100::/40No route object for it. A route object for 2804:40a0::/32 with origin AS265971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265971 in the RIR database for the space.634 of 636
Route object: none2804:40a0:f100::/41No route object for it. A route object for 2804:40a0::/32 with origin AS265971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265971 in the RIR database for the space.634 of 636
Route object: none2804:40a0:f180::/41No route object for it. A route object for 2804:40a0::/32 with origin AS265971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265971 in the RIR database for the space.634 of 636
Route object: none2804:40a0:f200::/40No route object for it. A route object for 2804:40a0::/32 with origin AS265971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265971 in the RIR database for the space.634 of 636
Route object: none2804:40a0:f200::/41No route object for it. A route object for 2804:40a0::/32 with origin AS265971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265971 in the RIR database for the space.634 of 636
Route object: none2804:40a0:f280::/41No route object for it. A route object for 2804:40a0::/32 with origin AS265971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265971 in the RIR database for the space.634 of 636
Route object: none2804:40a0:f300::/40No route object for it. A route object for 2804:40a0::/32 with origin AS265971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265971 in the RIR database for the space.634 of 636
Route object: none2804:40a0:f300::/41No route object for it. A route object for 2804:40a0::/32 with origin AS265971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265971 in the RIR database for the space.634 of 636
Route object: none2804:40a0:f380::/41No route object for it. A route object for 2804:40a0::/32 with origin AS265971 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265971 in the RIR database for the space.634 of 636
Route object: RIR164.163.196.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:40a0::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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