Megatelecom Telecomunicacoes
BGP inherited
Cluster stats
Netblocks10
All fragments 11 blocks across 2 clusters
Cluster ID193383647
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

2 weekly snapshots · JSON
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-06

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.82.109/32 Megatelecom Telecomunicacoes PEERINGDB ASSIGNED ● high
80.249.215.22/32 Megatelecom Telecomunicacoes PEERINGDB ASSIGNED ● high
187.16.213.61/32 Megatelecom Telecomunicacoes PEERINGDB ASSIGNED ● high
187.16.216.57/32 Megatelecom Telecomunicacoes PEERINGDB ASSIGNED ● high
198.32.160.253/32 Megatelecom Telecomunicacoes PEERINGDB ASSIGNED ● high
2001:504:1::a502:2381:1/128 Megatelecom Telecomunicacoes PEERINGDB ASSIGNED ● high
2001:7f8:1::a502:2381:1/128 Megatelecom Telecomunicacoes PEERINGDB ASSIGNED ● high
2001:12f8::57/128 Megatelecom Telecomunicacoes PEERINGDB ASSIGNED ● high
2001:12f8::213:61/128 Megatelecom Telecomunicacoes PEERINGDB ASSIGNED ● high
2001:12f8:0:2::54:109/128 Megatelecom Telecomunicacoes PEERINGDB ASSIGNED ● high

Network trust

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

NIC Handles

AS22381