L E M TELECOMUNICAÇÕES

BGP inherited
Cluster stats
Netblocks8
All fragments 10 blocks across 2 clusters
Cluster ID213185785
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.73.93/32 L E M TELECOMUNICAÇÕES PEERINGDB ASSIGNED ● high
187.16.212.94/32 L E M TELECOMUNICAÇÕES PEERINGDB ASSIGNED ● high
200.219.145.194/32 L E M TELECOMUNICAÇÕES PEERINGDB ASSIGNED ● high
200.219.147.86/32 L E M TELECOMUNICAÇÕES PEERINGDB ASSIGNED ● high
2001:12f8::212:94/128 L E M TELECOMUNICAÇÕES PEERINGDB ASSIGNED ● high
2001:12f8:0:8::194/128 L E M TELECOMUNICAÇÕES PEERINGDB ASSIGNED ● high
2001:12f8:0:9::145:93/128 L E M TELECOMUNICAÇÕES PEERINGDB ASSIGNED ● high
2001:12f8:0:10::86/128 L E M TELECOMUNICAÇÕES PEERINGDB ASSIGNED ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “L E M” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

AS263292