MEGANET TELECOM
BGP inherited
Cluster stats
Netblocks12
All fragments 174 blocks across 24 clusters
Cluster ID191614773
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 2 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

3 weekly snapshots · JSON
12 +2 netblocks since 2026-07-05
2026-07-05 peak 12 2026-07-12

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.176.56.0/22 AS268969 BGP ANNOUNCED ● high
131.108.156.0/22 AS61681 BGP ANNOUNCED ● high
131.108.156.0/23 AS61681 BGP ANNOUNCED ● high
131.108.158.0/23 AS61681 BGP ANNOUNCED ● high
131.108.158.0/24 AS61681 BGP ANNOUNCED ● high
131.108.159.0/24 AS61681 BGP ANNOUNCED ● high
2804:1ce4::/32 AS61681 BGP ANNOUNCED ● high
2804:1ce4::/32 UNKNOWN LACNIC allocated ● high
2804:1ce4:2000::/36 AS61681 BGP ANNOUNCED ● high
2804:1ce4:3000::/36 AS61681 BGP ANNOUNCED ● high
2804:5d64::/32 AS268969 BGP ANNOUNCED ● high
2804:5d64::/32 UNKNOWN LACNIC allocated ● high

Network trust

what's this?
RPKI hygiene: D how networks compare →
25.0% of checked blocks have valid RPKI ROA coverage (3 of 12)
Possible discrepancies (3)

These blocks are registered to MEGANET TELECOM but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2804:5d64::/32 /32 authorized for AS268969 — AS268969
2804:5d64::/32 /32 authorized for AS268969 — AS268969
45.176.56.0/22 /22 authorized for AS268969 — AS268969

NIC Handles

AS268969 AS61681