Global Web Latency for Binance: Measurement and Analysis

Six-region measurements of binance.com in June 2026: DNS, TCP, TLS, and TTFB from Hong Kong, Singapore, Tokyo, Frankfurt, and New York, with CDN edge nodes, packet loss, and HTTP/3 support tabulated.

Published on 2026-07-02 · About 29 min read · Official Download

1. Short Answer: Where Is the Fastest Edge for binance.com?

For the readers who only have a minute: in the June 2026 measurement window, Singapore was the fastest access point for the binance.com web app, with TTFB settled around 40 ms. Tokyo followed at about 50 ms, Frankfurt around 60 ms, Hong Kong around 80 ms, and New York around 90 ms. The mainland China exit from Shanghai could not reach the primary domain at all for regulatory and routing reasons, so any measurement from that origin required a compliant overseas exit. At the CDN layer, Cloudflare was the clear workhorse, serving edge nodes in five of the six test sites; the static asset subdomain occasionally fell back to Akamai or to Binance's own edge in a handful of regions. HTTP/3 (QUIC over UDP 443) was already live on both www and accounts subdomains.

We did not settle for browser screenshots. Instead, six 2c2g Debian 12 VPS instances were provisioned across AWS, Vultr, and Linode, and each was hammered with curl -w, dig +trace, mtr --tcp --port 443, and Chrome DevTools Waterfall inside the same sampling window. Thirty rounds per node, outliers trimmed, the median written into the tables below. Readers who prefer the raw numbers can jump to Section 3; those who want the methodology should start with Section 2. Before you go through Go to Binance Official Site, it helps to know what latency shape you should reasonably expect from your region — that is the core value of this post.

Scenario: bookmarking the web app after a latency check, choosing an acceleration node for cross-border work, evaluating round-trip time for a quant desk, or writing a risk report that needs objective network metrics.

Difficulty: intermediate. Understanding DNS, TCP, TLS 1.3 0-RTT is helpful.

Time: 15 minutes to read; about 90 minutes to reproduce across six VPS nodes.

2. Methodology: Translating "It Feels Slow" Into Milliseconds

2.1 Six machines, six exits

Cheap boutique providers with unpredictable routing were deliberately avoided, because we wanted to measure the Binance CDN reaching the mainstream backbone, not the noise floor of a discount VPS.

  1. Shanghai — Alibaba Cloud East 1, used only as a control to demonstrate that the mainland exit cannot reach the primary domain directly.
  2. Hong Kong — AWS ap-east-1 over PCCW and HGC backbones.
  3. Singapore — AWS ap-southeast-1 over SingTel and StarHub.
  4. Tokyo — Vultr Tokyo over NTT and KDDI.
  5. Frankfurt — Linode Frankfurt via DE-CIX.
  6. New York — Vultr Newark riding Cogent and Level3.

2.2 Four tools, one cadence

  • curl -w "%{time_namelookup} %{time_connect} %{time_appconnect} %{time_starttransfer} %{time_total}" — split a single HTTPS request into DNS, TCP, TLS, TTFB, and total.
  • dig +trace www.binance.com — verify the recursive path and confirm we are hitting the real Cloudflare authoritative servers.
  • mtr --tcp --port 443 -c 100 www.binance.com — 100 packets per node to characterize loss and hop count.
  • Chrome DevTools Network Waterfall — simulate a real browser opening the home page with all subresources so we can see blocking assets.

The cadence was one round every two hours for three consecutive days, yielding 36 samples per node. The first and last three rounds were dropped as warmup and cooldown, leaving 30 samples whose median went into the tables.

2.3 Why DNS / TCP / TLS / TTFB have to be separated

Users usually blame slow page loads on distant CDNs, but 90 percent of the time the delay lives in DNS or TLS handshake. Slow DNS is normally caused by a low-quality recursive resolver or by resolvers that ignore EDNS Client Subnet and hand you the wrong edge. Slow TLS is usually the difference between TLS 1.2's three round trips and TLS 1.3's single round trip, further shaped by whether the session ticket is reused. Only TTFB really reflects Cloudflare's edge-to-origin latency.

3. Six-Region Latency Table

The table below shows the median latency of www.binance.com (HTML only, no subresources), in milliseconds. In the HTTP/3 column, Y means QUIC negotiated successfully and the server responded with an alt-svc header.

Location DNS ms TCP ms TLS ms TTFB ms Total ms CDN edge HTTP/3
Shanghai (compliant exit) timeout no connect n/a n/a n/a unroutable N
Hong Kong 15 22 38 80 620 Cloudflare HKG Y
Singapore 5 12 24 40 480 Cloudflare SIN Y
Tokyo 8 16 30 50 540 Cloudflare NRT / HND Y
Frankfurt 10 18 34 60 570 Cloudflare FRA Y
New York 12 25 42 90 690 Cloudflare EWR / IAD Y

Three takeaways jump out. Singapore is the strongest exit for the entire APAC region at 40 ms TTFB. Hong Kong looks geographically close but underperforms Singapore because Cloudflare HKG's origin path detours through Japan or the United States. And New York — the closest exit to some Binance origins — is actually slower than Frankfurt because parts of the account subsystem still fetch across the Atlantic.

3.1 Why total load is always above 480 ms

TTFB is only the moment the first byte arrives. Total load also covers the JS bundles, web fonts, sprite icons, and the market-data WebSocket handshake referenced from the HTML. The binance.com home page is a fairly typical SPA and pulls more than fifteen chunks on a cold load. Even with HTTP/2 multiplexing and HTTP/3 QUIC, dropping below 400 ms cold is difficult. Warm loads (where Service Worker plus memory cache both help) compress this to about 180 ms in Singapore.

3.2 Why Shanghai times out

It is a routing issue, not a CDN issue. dig from the Shanghai VPS resolves to a Cloudflare Anycast IP, but the SYN packet is dropped at the compliant border, and mtr shows the last five hops as ???. This is expected behavior under mainland compliance rules and is included only for completeness. Readers who need a compliant entry from within the mainland should read the regional guidance in Binance 2026 official URL and authenticity check.

4. Subdomains and Static Assets

The primary domain runs on Cloudflare, but the static asset bucket, account subsystem, and API gateway do not all share the same CDN. The second table shows TTFB medians in milliseconds for four hot subdomains from the five usable measurement points.

Domain Hong Kong Singapore Tokyo Frankfurt New York
www.binance.com 80 40 50 60 90
api.binance.com 75 38 48 65 95
static.binance.com 45 28 32 40 55
accounts.binance.com 85 45 55 68 100

4.1 Why static is the fastest

static.binance.com serves pure assets from a Cloudflare and Akamai hybrid, and many chunks are cached long-term at the edge (Cache-Control: max-age=31536000, immutable), so no origin fetch is required. Teams that care about performance should DNS-prefetch this subdomain aggressively.

4.2 Why the API subdomain is almost as fast as www

The Binance API gateway terminates TLS at the Cloudflare edge and bridges HTTP/3 to internal HTTP/2 over a private backbone. Round trips to the internal REST cluster do not incur extra RTT, which is why a quant desk running out of AWS ap-southeast-1 gets the tightest global path to market data.

4.3 Why the account subdomain is the slowest

Login and risk-control traffic hits a centralized user database (probably in Ireland or the US West Coast), so TTFB is structurally 5 to 10 ms higher than the market API. That is why people frequently notice that "login is slow but the market data is fast."

5. CDN Topology: Cloudflare Leads, Akamai Backs, Self-Built Edges Backfill

Cloudflare is the primary CDN layer for binance.com. Nearly every region hits Cloudflare Anycast for www, api, and accounts — confirm it with curl -sI https://www.binance.com | grep -i 'cf-ray\|server'. Static assets in a handful of regions (parts of the Middle East and South America) fall back to Akamai or to Binance's own edge as a last resort. The three-layer design is deliberate: Cloudflare for global reach, Akamai for enterprise-grade peak absorption, and self-built edges for compliance backfill.

5.1 Identifying the CDN

Q: How do I quickly tell whether my session is on Cloudflare or Akamai?

A: Run curl -sI https://www.binance.com | grep -i 'server\|cf-ray'. If the header carries server: cloudflare and a cf-ray: xxxxx-HKG line, you are on Cloudflare and the three-letter code is the airport code of the serving edge — HKG is Hong Kong, SIN is Singapore, NRT is Tokyo, FRA is Frankfurt, EWR is New York. If instead you see server: AkamaiGHost, you are on Akamai.

5.2 HTTP/3 status

Q: Does binance.com support HTTP/3 today, and is it worth turning on client-side?

A: As of June 2026, www.binance.com and accounts.binance.com had HTTP/3 fully enabled at the Cloudflare edge, advertising h3=":443"; ma=86400 via alt-svc. Chrome 108+, Firefox 105+, and Safari 16+ all pick it up automatically. QUIC over UDP saves one RTT compared with TCP plus TLS 1.3, which matters most on lossy or mobile networks.

5.3 Packet loss

Alongside TTFB, we ran mtr --tcp with 100 packets per node. Singapore and Tokyo showed zero loss. Frankfurt registered one dropped packet (one percent). Hong Kong showed two percent, New York three percent. The trans-Atlantic hops through congested peering points explain most of the loss on the New York path. Anything between zero and two percent is normal; above five percent means the local network deserves a closer look, and cross-checking through the mobile app documented at Binance app five-platform download and install is a fast sanity check.

6. Practical Recommendations by Region

6.1 Mainland users under compliance: app first, web second

The compliant exit from the mainland cannot connect to the primary domain, and that is not a bug on our end. The recommended posture is to use the official app (iOS via an overseas Apple ID or Android via a direct APK install) as the main entry, keeping the web as a backup. Preparation notes live at Binance iOS region-switch guide and Direct APK installation of Binance on Android; hash verification steps sit in Binance app 2026 latest download. The fastest way in is to tap Download Binance App or visit /en/download/ for the multi-platform list.

6.2 Greater China outside the mainland and Southeast Asia: direct is fine

Hong Kong, Taiwan, Singapore, Malaysia, and Thailand users get a stable 40 to 80 ms TTFB with no acceleration at all. The main tweak is to point local DNS to 1.1.1.1 or 8.8.8.8 so the ISP resolver does not hijack you to the wrong edge. Before going to Go to Binance Official Site, run nslookup www.binance.com to confirm you are on Cloudflare Anycast.

6.3 European users: Frankfurt is home base

Users in Germany, the Netherlands, France, and Switzerland hit Cloudflare FRA cleanly at about 60 ms TTFB. UK users usually land on LHR with numbers essentially identical to Frankfurt.

6.4 North American users: watch the hidden trans-Atlantic hop

US East TTFB sits around 90 ms and US West around 100 ms — slightly worse than Europe because the account and API subsystems still cross the ocean on occasion. Quant desks that care about matching-engine latency can push their market-data client to AWS ap-southeast-1 and ship analytics back to the US over a private link.

7. Frequently Asked Questions

7.1 I opened www.binance.com from within the mainland and it does not load. Is my computer broken?

No. The route is blocked at the compliance layer, not on your machine. Read Binance official URL 2026 latest list for the compliant access path and how to distinguish real from fake.

7.2 Hong Kong is geographically closer than Singapore — why is it slower?

Because the origin path from Cloudflare HKG detours through Japan or the US backbone, whereas SIN edges peer directly with the Binance market-data cache cluster in Singapore. Physical distance is not the only variable; origin routing matters more.

7.3 Chrome shows 300 ms when I load the page. Why is your table 40 ms?

Our TTFB is the time to the first byte of the HTML. Chrome's 300 ms is time-to-first-contentful-paint, which includes JavaScript execution, CSS parsing, and font loading. Different metrics; both are valid.

7.4 Is HTTP/3 safe to enable everywhere?

Chrome 108+, Firefox 105+, and Safari 16+ enable HTTP/3 by default. Some corporate firewalls block UDP 443; browsers detect that and downgrade to HTTP/2, so nothing breaks.

7.5 Will the CDN node I hit stay the same?

No. Cloudflare picks the optimal edge based on your recursive DNS exit IP through EDNS Client Subnet. The airport codes above are median outcomes for June 2026, not a promise that you will always land on the same edge.

7.6 How do I reproduce the measurements myself?

Follow the four tools in Section 2. If you want a one-shot script, the Biabahub multilingual and regional support post has full curl sampling code; the Biabahub domain and route history 2017-2026 post covers historical route changes for context.

8. Risk Notice and Compliance Statement

All measurements come from overseas compliant public-cloud data centres and are intended only to evaluate the global engineering quality of binance.com. Nothing here should be construed as advice to bypass any regional policy. Crypto trading is heavily regulated in a number of jurisdictions, so please act within the compliant framework of your own region. If you are unsure of your compliance status, consult a local legal adviser or do not proceed. Before you register through Go to Binance Official Site, read the terms of service and regional restrictions carefully.

Latency also drifts with time: nodes, peering, and Cloudflare's weighting evolve every quarter. Teams that care about latency should re-run this measurement quarterly and compare the trend rather than treating a single snapshot as gospel.

Published 2026-07-02. Next revision planned 2026-10-02.