MEGALINK TELECOMUNICACOES

Data as of 2026-08-30
BGP inherited
This organisation
Netblocks6
IPv6 3 prefixes (largest 2001:12f8::223:13/128)
Registered in Brazil (2) · United States (1)
Also registered under this name 9 netblocks across 2 separate records
Record ID233784091
RegistryPEERINGDB
Customerssee who runs inside 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 · report an issue

Footprint over time

7 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-08-30

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
64.191.233.54/32 MEGALINK TELECOMUNICACOES PEERINGDB ASSIGNED ● high
187.16.216.25/32 MEGALINK TELECOMUNICACOES PEERINGDB ASSIGNED ● high
187.16.223.13/32 MEGALINK TELECOMUNICACOES PEERINGDB ASSIGNED ● high
2001:504:0:7:0:5:2944:1/128 MEGALINK TELECOMUNICACOES PEERINGDB ASSIGNED ● high
2001:12f8::25/128 MEGALINK TELECOMUNICACOES PEERINGDB ASSIGNED ● high
2001:12f8::223:13/128 MEGALINK TELECOMUNICACOES PEERINGDB ASSIGNED ● high

IPv6 ranges (3)

Network trust

what's this?
RPKI hygiene: C how networks compare →
66.7% of checked blocks have valid RPKI ROA coverage (4 of 6)
No discrepancies found among checked blocks.

NIC Handles

AS52944