Mbytechnology Limited

Data as of 2026-10-04
BGP inherited
This organisation
Netblocks4
IPv6 3 prefixes (largest 2a0c:b641:660::/44)
Also registered under this name 5 netblocks across 2 separate records
Record ID246685043
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 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 (4)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.1.138.21/32 MBYTECHNOLOGY PEERINGDB 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 (3)

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 →
25.0% of checked blocks have valid RPKI ROA coverage (1 of 4)
No discrepancies found among checked blocks.

NIC Handles

AS202532 DUMY-RIPE DUMY-RIPE MBYTECH-MNT ORG-ML950-RIPE SERVPERSO-MNT