--- title: "Alchemy launches Tokyo regional support" description: "Node RPC, WebSockets, and Dedicated Clusters are now live in Tokyo, with up to 8x lower median latency for requests from Japan." --- # Alchemy launches Tokyo regional support Alchemy [Node RPC](/rpc-api), [WebSockets](/smart-websockets), and [Dedicated Clusters](/dedicated-clusters) are now live in Tokyo, with up to 8x lower median latency for requests from Japan. That's about 70ms less per call for teams building in Japan, from wallets and payment apps to trading desks next to APAC's major venues and exchanges. Your slowest requests improve as well. Your p95 latency drops by up to ~76%. [See how we benchmark RPC performance](/blog/how-we-benchmark-rpc-performance). We launch Tokyo with the widest chain coverage in Asia, including Base, BNB, Robinhood Chain, Ethereum, HyperEVM, Arc, and more. With 100+ chain relationships built over almost 10 years, we'll continue to rapidly expand support for this region to provide ultra-low latency on every chain. Launching Tokyo regional support is our latest step to be the fastest, most reliable way to read and write onchain state. ## Purpose-built for trading and low-latency workflows Every trade runs through the same loop. A market signal arrives, and the app reads onchain state over RPC or WebSockets. A pricing or execution engine decides what to do. A transaction goes out, and the system watches for confirmation. Market makers, exchanges, trading platforms, and arbitrage systems all run a version of it. At every step, their market-data feeds, pricing and execution engines, order-management systems, and wallet backends make RPC requests or wait on WebSocket updates. Many of these teams already run their stack in Tokyo to sit close to venues like Binance and Hyperliquid. If their RPC and WebSocket traffic then leaves Tokyo for another region, every request pays for the extra distance. In a fast market, that delay results in stale price data, high slippage, and missed trades. Our Tokyo infrastructure removes that detour. The loop gets shorter and more predictable, including on the slowest requests, which cost the most when markets move. ## Why build for Japan on Alchemy? Japan's crypto market is large and active. As of March 2026, the country had about 14.1 million crypto trading accounts, and roughly 11% of the population held crypto assets, according to data cited in Coincheck Group's 2026 filing. People who trade every day notice when an app lags. With requests answered in Tokyo, wallets showing live balances, payments confirming settlement, and apps tracking transaction status all respond faster. In July 2026, Japan's Diet passed amendments that move crypto assets under the Financial Instruments and Exchange Act, the same law that covers stocks and bonds. The new rules are expected to take effect in 2027, giving exchanges and tokenized-asset platforms a defined structure to build toward, alongside Japan's existing stablecoin rules. These products never close, so uptime matters as much as speed. Our platform held 99.99% uptime through the largest liquidation event in crypto history. It supports 100+ chains, and it is the same infrastructure behind Visa, Circle, Robinhood, and J.P. Morgan's Kinexys. In APAC, Bitget verifies deposits and withdrawals for its 125 million users on Alchemy and named our Tokyo infrastructure as part of why they chose us. ## How does my traffic reach Tokyo? There's no new endpoint and no migration. Tokyo runs on the same Alchemy platform you already use. We automatically detect where a request is coming from and route it to the closest region. Get started in the [Alchemy Dashboard](https://dashboard.alchemy.com/) or [talk to our team](/contact-sales) about your Tokyo and APAC workloads. ## Frequently asked questions ### How much latency does Alchemy's Tokyo infrastructure save? For requests from Japan, median latency is up to 8x lower, about 70ms less per call. Tail latency at p95 drops by up to ~76%, to as low as 5ms. Your savings depend on where your systems run, the method, and which chain you call. See [how we benchmark RPC performance](/blog/how-we-benchmark-rpc-performance) for our methodology. ### Do I need to change my endpoint? No. Alchemy routes traffic to the closest available region automatically. Existing Node RPC and WebSocket integrations work without any changes. ### Which Alchemy products are available in Tokyo? [Node RPC](/rpc-api), [WebSockets](/smart-websockets), and [Dedicated Clusters](/dedicated-clusters) are live in Tokyo. ### Which networks are served from Tokyo? Tokyo launches with the widest chain coverage in Asia, including Base, BNB, Robinhood Chain, Ethereum, HyperEVM, Arc, and more. [Talk to our team](/contact-sales) to learn more. ### What happens if my network isn't served from Tokyo yet? Requests for that network route to the closest region that serves it, so nothing breaks. Those requests won't see the Tokyo latency improvement until the network is available in Tokyo.