Mbytechnology Limited

Data as of 2026-11-22
BGP inherited
This organisation
Netblocks5
IPv6 4 prefixes (largest 2a0c:b641:660::/44)
Also registered under this name 6 netblocks across 2 separate records
Record ID277528937
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 9 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (5)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.1.138.21/32 MBYTECHNOLOGY PEERINGDB ASSIGNED ● high
2a06:9801:1594::/48 Mbytechnology Limited RIPE ASSIGNED ● high
2a0c:b641:700:0:a5:20:2532:1/128 MBYTECHNOLOGY PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:10::15d/128 MBYTECHNOLOGY PEERINGDB ASSIGNED ● high
2a0c:b641:660::/44 Mbytechnology Limited RIPE ALLOCATED-BY-LIR ● low

IPv6 ranges (4)

Footprint over time

3 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-12

Network trust

what's this?
RPKI hygiene: D how networks compare →
20.0% of checked blocks have valid RPKI ROA coverage (1 of 5)
No discrepancies found among checked blocks.

NIC Handles

AS202532 DUMY-RIPE DUMY-RIPE LAGRANGE-AUTO-MNT LSRA2-RIPE MBYTECH-MNT ORG-ML950-RIPE ORG-ML995-RIPE SERVPERSO-MNT