Independent community project. Not affiliated with, authorised by or endorsed by MEGA Limited, mega.nz or mega.io.
MEGAPROXY.top

A public HTTP rotating proxy for the official MEGA clients.

Point MEGAsync or MEGAcmd at the address below and your transfers leave from a rotating exit instead of your own connection. No account, no client to install, no fee.

Public endpoint EU
Host eu.ingress.megaproxy.top
Port 8080
Type HTTP

No username or password required.

MEGA sees an address from the exit pool, never yours. Your files are encrypted by the client before they leave your machine, so the proxy only ever moves ciphertext.

Setup

Two minutes, no restart of anything except the transfer itself.

MEGAsync

desktop app

  1. Open the proxy settings

    Settings, then Proxy, then manual configuration.

  2. Fill in the three values

    Type HTTP, and leave the authentication boxes empty. Tap a value to copy it.

  3. Apply, then restart a transfer

    If it resumes and your visible address is no longer your own, you are going through the proxy.

MEGAcmd

command line
$ mega-https on
$ mega-proxy http://eu.ingress.megaproxy.top:8080

HTTPS is required. MEGAcmd moves transfer data over plain HTTP by default, and those requests do not survive the proxy. Run mega-https on first, in that order, or transfers will fail with connection errors. Inside the interactive shell the same command is https on. If transfers stall later, check that it is still enabled.

One thing to be clear about. This exists so your transfers do not come straight from your home connection. It is not a way around MEGA transfer quotas, and using it that way puts your account at risk. Please stay within MEGA's Terms of Service.

Details

What you are actually connecting to.

Automatic IP Rotation
Every connection uses a fresh egress IP. Consecutive connections can leave from different ones.
Unlimited Bandwidth
No data caps, no speed limits.
Zero‑Logs
The proxy is a passive conduit between you and MEGA's own servers. Content is not, and cannot be, inspected or stored.
Accounts
None. Nothing to register, nothing to enter, no client to install.
Expanding Network
Currently EU ingress with more regions coming soon.
Availability
Best effort, run as a side project. Capacity is shared, so throughput varies with load and no uptime is guaranteed.

Questions

Is it safe to run my MEGA account through it?

You are not required to sign into your MEGA account to download files. MEGA encrypts your files on your own device before anything is sent, and the API session runs over TLS. A proxy in the middle carries sealed traffic and holds none of the keys. With mega-https on set for MEGAcmd, every connection is a tunnel the proxy cannot read into.

Will this give me extra transfer quota?

It is not meant to, and treating it as a quota workaround is against MEGA's terms. Limits on a signed in account follow the account rather than the address it connects from.

Does it slow transfers down?

Usually a little. Traffic takes an extra hop and the pool is shared, so throughput depends on how busy the exits are at that moment.

Something is broken. What now?

For MEGAcmd, confirm HTTPS is on before anything else, since that accounts for most failures. Otherwise mail [email protected] with the client you use and the error it shows.