Autonomous system
AS205809 MEGA MEGA Privacy Kft.
Hosting RIPE Content
Summary
MEGA
vpn cloud privacy business
MEGA is operated by MEGA Privacy Kft.
What it's used for
- The address space carries infrastructure for MEGA's encrypted cloud storage, VPN, and privacy services, as indicated by netnames such as
HU-MEGAPRIVACY-20170530andMEGA-PT. - With 4,352 IPv4 addresses and 16 IPv6 prefixes announced against only 5 observed neighbours, the network functions as a service endpoint rather than a transit provider.
- Traffic from this AS consists of user connections to MEGA's secure file hosting, private chat, and VPN endpoints, supporting the company's global privacy-focused product suite.
Notable
- Registrants for most prefixes are
MEGA Privacy Kft., while82.29.204.0/22is registered toInternet Utilities Europe and Asia Limitedunder netnameNET-82-29-128-0-17. - The address inventory includes a mix of Hungarian allocations and a block registered to a private customer, reflecting a consolidated corporate estate for a global service provider.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-11-04, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 8 prefixes · 4.35K addresses IPv6 18 prefixes
| Country | Name | Prefixes |
|---|---|---|
| HU | Hungary | 26 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS205809- Registry name
- MEGA
- Registrant
- lir-hu-megaprivacy-1-MNT
- Abuse contact
- abuse@mega.io
- Registered
- 2017-05-30
- Last changed
- 2026-04-28
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- MEGA New Zealand
- Network type
- Content
- Scope
- Global
- Traffic ratio
- Mostly Outbound
- Peering policy
- Selective
- Present at
- 1 exchanges
- Facilities
- 7 facilities
- Website
- https://mega.io
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 100% valid · 33 valid, 0 with no ROA
- ROAs
- 30 authorising AS205809
- ASPA
- no ASPA record
- IRR
- 94% registered · 31 of 33 announcements
- Route objects
- 50 naming AS205809
Reputation
Classification and threat
Hosting Datacenter or cloud provider. Addresses are servers, not people.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 453 networks and 1,853 prefixes, as published 2026-11-05. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere