All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
I wanted to know how fast each cloud region is from my home connection, so I built a tool for it
When I pick a region for a new server, I used to search for a cloud latency map and go with whatever looked green. At some point it clicked that every one of those maps, and every provider's looking glass, runs its tests from a datacenter. Datacenters buy good transit, so the numbers look great. My home line is one ISP with one set of international links, and those get crowded every evening. None of that shows up on a map measured from somewhere else.
The question I actually had was simple: from my connection, at this time of day, which region is closest?
So I built Me2Cloud: m2c.1ms.dog
You open the page and press Start. The requests go from your browser straight to each provider. It covers 361 regions across 17 providers: AWS, Azure, Google Cloud, Oracle, IBM Cloud, DigitalOcean, Linode, Vultr, Hetzner, OVHcloud and Scaleway, plus Alibaba Cloud, Tencent Cloud, Huawei Cloud, Volcengine, Baidu AI Cloud and Naver Cloud.
Today at noon I ran 6 of them from home in Beijing, 172 regions in about three minutes on the quick setting. AWS Beijing came in at 7.7 ms and Alibaba Cloud Beijing at 8.2 ms. Azure's best was Seoul at 83 ms, Google Cloud's was Los Angeles at 175 ms, and Hetzner Singapore was 500 ms. Those are the numbers that decide where I'd put a server, and you can't get them from a test that starts in Frankfurt.
Results are grouped into five tiers by median latency (GOATed, Top tier, Solid, NPC, Cooked). If you tell it what the server is for (gaming, video calls, SSH or a website), it applies the matching latency and jitter limits and suggests three regions.
A few decisions took more thought than the rest.
Why HTTPS requests instead of ping?
Partly because a browser can't send ICMP. But I wouldn't want ping anyway: websites, APIs and anything tunneled over 443 run on TCP, and plenty of ISPs queue or throttle ICMP separately. Ping can look fine while pages crawl.
The cost of HTTPS is a little server time on every request. I measured it per provider: roughly 0–5 ms on AWS, about 8 ms on Alibaba Cloud, about 20 ms on Huawei Cloud's object storage. Past 100 ms it doesn't matter; for regions very close to you, expect slightly higher numbers than ping. The first request pays for the TLS handshake and isn't counted. Every sample after that reuses the same connection, so it's one round trip.
What if I usually run a proxy?
Then you'll probably see Singapore, Tokyo and Frankfurt all within a few milliseconds of each other. That's the latency to your proxy node, not to the clouds. Before testing, the page checks a few things: whether your exit IP belongs to a datacenter, whether your timezone matches the exit country, whether WebRTC and HTTPS leave from the same address. If something looks off, it says so and gives you direct-connection rules for Clash/Mihomo, Surge, Shadowrocket, Quantumult X, Loon, sing-box, Xray or SwitchyOmega.
The rules went through a few versions. Early on some tools got suffix matches like amazonaws.com, which was easy but also sent every S3 download of yours direct, and in some countries direct is the slow path. Now the rules list only the 413 hostnames the test actually uses. No wildcards.
Won't hundreds of regions at once get you blocked?
If the requests come too fast, a provider's WAF or rate limit steps in and the numbers stop meaning anything. So each hostname gets one request at a time, at least 250 ms apart, 21 at most per run, and a host is skipped after three failures in a row. That's less traffic than loading an average web page.
Where does my data go?
Nowhere. There's no backend and no account, and results stay in your browser. Every request shows up in DevTools, and there's a request log on the page too.
Sharing doesn't touch a server either. The share link packs the results into the URL itself, and the share image, like this one from the run above, is drawn on a canvas in your browser.
Open source, and easy to host yourself
MIT licensed: github.com/yt1988/me2cloud
It's a static site, and the built pages are already in the repo. On Cloudflare Workers static assets it's free and unmetered:
git clone https://github.com/yt1988/me2cloud && cd me2cloud
npx wrangler deploy
You don't need to deploy anything to test your own server, though. Add it as a custom endpoint on the page and it shows up in the same chart as the big providers.
What it won't tell you
It measures one place, yours, not your users'. Ask a few of them to run it too. It tests each provider's public API or storage endpoint rather than the VM you'd rent, so premium network tiers can behave differently. It doesn't test bandwidth or UDP. And run it again between 8 and 11pm; peak hour is the result that counts.
I built it to pick regions for my own projects. If there's a provider or region you'd like added, or an endpoint that doesn't respond from where you are, open an issue or leave a comment.