MEGATECH

BGP inherited
Cluster stats
Netblocks9
Registered in Hong Kong (5) · Germany (3) · Spain (1)
All fragments 21 blocks across 7 clusters
Cluster ID208875141
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 10 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
61.92.104.163/32 MEGATECH APNIC ASSIGNED NON-PORTABLE ● low
61.93.247.136/29 MEGATECH APNIC ASSIGNED NON-PORTABLE ● low
61.239.250.117/32 MEGATECH APNIC ASSIGNED NON-PORTABLE ● low
81.201.150.237/32 Megatech_GmbH RIPE ASSIGNED PA ● low
145.253.130.112/28 MEGATECH-NET RIPE ASSIGNED PA ● low
193.97.204.128/27 MEGATECH RIPE ASSIGNED PA ● low
195.55.16.176/28 MEGATECH RIPE ASSIGNED PA ● low
203.186.221.160/30 MEGATECH APNIC ASSIGNED NON-PORTABLE ● low
203.186.221.164/30 MEGATECH APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “MEGATECH” — 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.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

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

NIC Handles

AC2009-AP ARCOR-MNT CH134-AP DSI-MNT DUMY-RIPE DUMY-RIPE MAINT-AS3352 MAINT-HK-CTI SL113-AP UUNETDE-I