bgpreport

Network · data from 2026-11-12

AS264164 AS264164 - Telecomunicacoes Netcoro Ltda

Registry name: AS264164 - Telecomunicacoes Netcoro Ltda, BR · not in PeeringDB

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

Announced routes

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

167.249.230.0/23 No ROA Nonecovered by 167.249.228.0/22 671 100% 67
138.94.132.0/23 No ROA Nonecovered by 138.94.132.0/22 670 100% 67
138.94.134.0/23 No ROA Nonecovered by 138.94.132.0/22 670 100% 67
167.249.228.0/23 No ROA Nonecovered by 167.249.228.0/22 670 100% 67
2804:2378::/33 No ROA Nonecovered by 2804:2378::/32 635 100% 67
2804:2378::/38 No ROA Nonecovered by 2804:2378::/32 635 100% 67
2804:2378:8000::/33 No ROA Nonecovered by 2804:2378::/32 635 100% 67
138.94.132.0/22 No ROA Other IRR onlyRADB 671 100% 67
167.249.228.0/22 No ROA Other IRR onlyRADB 671 100% 67
2804:2378::/32 No ROA Other IRR onlyRADB 635 100% 68

AS-SET

AS264164 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.

  • ROA: none10
  • Route object: none7
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none167.249.230.0/23No ROA covers it. Add a ROA for AS264164, maxLength 23.671 of 673
Route object: none167.249.230.0/23No route object for it. A route object for 167.249.228.0/22 with origin AS264164 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264164 in the RIR database for the space.671 of 673
ROA: none138.94.132.0/23No ROA covers it. Add a ROA for AS264164, maxLength 23.670 of 673
Route object: none138.94.132.0/23No route object for it. A route object for 138.94.132.0/22 with origin AS264164 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264164 in the RIR database for the space.670 of 673
ROA: none138.94.134.0/23No ROA covers it. Add a ROA for AS264164, maxLength 23.670 of 673
Route object: none138.94.134.0/23No route object for it. A route object for 138.94.132.0/22 with origin AS264164 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264164 in the RIR database for the space.670 of 673
ROA: none167.249.228.0/23No ROA covers it. Add a ROA for AS264164, maxLength 23.670 of 673
Route object: none167.249.228.0/23No route object for it. A route object for 167.249.228.0/22 with origin AS264164 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264164 in the RIR database for the space.670 of 673
ROA: none2804:2378::/33No ROA covers it. Add a ROA for AS264164, maxLength 33.635 of 636
Route object: none2804:2378::/33No route object for it. A route object for 2804:2378::/32 with origin AS264164 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264164 in the RIR database for the space.635 of 636
ROA: none2804:2378::/38No ROA covers it. Add a ROA for AS264164, maxLength 38.635 of 636
Route object: none2804:2378::/38No route object for it. A route object for 2804:2378::/32 with origin AS264164 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264164 in the RIR database for the space.635 of 636
ROA: none2804:2378:8000::/33No ROA covers it. Add a ROA for AS264164, maxLength 33.635 of 636
Route object: none2804:2378:8000::/33No route object for it. A route object for 2804:2378::/32 with origin AS264164 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264164 in the RIR database for the space.635 of 636
ROA: none138.94.132.0/22No ROA covers it. Add a ROA for AS264164, maxLength 22.671 of 673
Route object: RIR138.94.132.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none167.249.228.0/22No ROA covers it. Add a ROA for AS264164, maxLength 22.671 of 673
Route object: RIR167.249.228.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:2378::/32No ROA covers it. Add a ROA for AS264164, maxLength 32.635 of 636
Route object: RIR2804:2378::/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 AS264164 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.