bgpreport

Network · data from 2026-11-12

AS264007 AS264007 - Eletric Telecomunicacoes e Informatica LTDA ME

Registry name: AS264007 - Eletric Telecomunicacoes e Informatica LTDA ME, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264007, 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.
143.0.180.0/22 No ROA Other IRR onlyRADB 670 100% 66
2804:2944::/32 No ROA Other IRR onlyRADB 636 100% 67

AS-SET

AS264007 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 26 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced22
ChangePrefix or setDetailFull-table peers
ROA: none143.0.180.0/22No ROA covers it. Add a ROA for AS264007, maxLength 22.670 of 673
Route object: RIR143.0.180.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2804:2944::/32No ROA covers it. Add a ROA for AS264007, maxLength 32.636 of 636
Route object: RIR2804:2944::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

143.0.180.0/23RADBNo ROA
143.0.180.0/24RADBNo ROA
143.0.181.0/24RADBNo ROA
143.0.182.0/23RADBNo ROA
143.0.182.0/24RADBNo ROA
143.0.183.0/24RADBNo ROA
2804:2944::/36RADBNo ROA
2804:2944:1000::/36RADBNo ROA
2804:2944:2000::/36RADBNo ROA
2804:2944:3000::/36RADBNo ROA
2804:2944:4000::/36RADBNo ROA
2804:2944:5000::/36RADBNo ROA
2804:2944:6000::/36RADBNo ROA
2804:2944:7000::/36RADBNo ROA
2804:2944:8000::/36RADBNo ROA
2804:2944:9000::/36RADBNo ROA
2804:2944:a000::/36RADBNo ROA
2804:2944:b000::/36RADBNo ROA
2804:2944:c000::/36RADBNo ROA
2804:2944:d000::/36RADBNo ROA
2804:2944:e000::/36RADBNo ROA
2804:2944:f000::/36RADBNo 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.