bgpreport

Network · data from 2026-11-12

AS265172 NavelinkNet

Registry name: AS265172 - E. C. E. Telecomunicacoes LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265172, 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:2bbc:2000::/36 No ROA Nonecovered by 2804:2bbc::/33 635 100% 67
167.249.240.0/24 No ROA Other IRR onlyBBOI, RADB, TC 671 100% 67
167.249.242.0/24 No ROA Other IRR onlyBBOI, RADB, TC 670 100% 67
167.249.241.0/24 No ROA Other IRR onlyBBOI, RADB, TC 669 99% 67
167.249.243.0/24 No ROA Other IRR onlyBBOI, RADB, TC 669 99% 67
2804:2bbc:3000::/36 No ROA Other IRR onlyRADB, TC 635 100% 67
2804:2bbc:7000::/36 No ROA Other IRR onlyRADB, TC 635 100% 67
2804:2bbc:c000::/36 No ROA Other IRR onlyTC 635 100% 67
2804:2bbc:8000::/36 No ROA Other IRR onlyRADB, TC 633 100% 67

AS-SET

AS265172'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 24 are in fix.csv.

  • ROA: none9
  • Route object: none1
  • Route object: RIR8
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none2804:2bbc:2000::/36No ROA covers it. Add a ROA for AS265172, maxLength 36.635 of 636
Route object: none2804:2bbc:2000::/36No route object for it. A route object for 2804:2bbc::/33 with origin AS265172 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265172 in the RIR database for the space.635 of 636
ROA: none167.249.240.0/24No ROA covers it. Add a ROA for AS265172, maxLength 24.671 of 673
Route object: RIR167.249.240.0/24Route object only in BBOI, RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none167.249.242.0/24No ROA covers it. Add a ROA for AS265172, maxLength 24.670 of 673
Route object: RIR167.249.242.0/24Route object only in BBOI, RADB, TC. Add it in the RIR database for the space.670 of 673
ROA: none167.249.241.0/24No ROA covers it. Add a ROA for AS265172, maxLength 24.669 of 673
Route object: RIR167.249.241.0/24Route object only in BBOI, RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none167.249.243.0/24No ROA covers it. Add a ROA for AS265172, maxLength 24.669 of 673
Route object: RIR167.249.243.0/24Route object only in BBOI, RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none2804:2bbc:3000::/36No ROA covers it. Add a ROA for AS265172, maxLength 36.635 of 636
Route object: RIR2804:2bbc:3000::/36Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:2bbc:7000::/36No ROA covers it. Add a ROA for AS265172, maxLength 36.635 of 636
Route object: RIR2804:2bbc:7000::/36Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:2bbc:c000::/36No ROA covers it. Add a ROA for AS265172, maxLength 36.635 of 636
Route object: RIR2804:2bbc:c000::/36Route object only in TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:2bbc:8000::/36No ROA covers it. Add a ROA for AS265172, maxLength 36.633 of 636
Route object: RIR2804:2bbc:8000::/36Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

167.249.240.0/22BBOI, RADB, TCNo ROA
167.249.240.0/23BBOI, RADB, TCNo ROA
167.249.242.0/23BBOI, RADB, TCNo ROA
2804:2bbc::/32BBOI, RADB, TCNo ROA
2804:2bbc::/33BBOI, RADBNo ROA
2804:2bbc:8000::/33BBOINo ROA

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.