Blockchain infrastructure

Top 9 RPC Providers in Japan (2026)

Compare Alchemy, Helius, Triton, QuickNode and five more on Tokyo routing, chain coverage, trading streams, transaction delivery and RPC pricing.

Tools at a glance

9 listed tools
  1. Alchemy
  2. Helius
  3. Triton RPC
  4. QuickNode
  5. Chainstack
  6. Ankr
  7. dRPC
  8. GetBlock
  9. Infura

For on-chain traders in Japan, Alchemy documents Tokyo EVM RPC, while Helius and Triton offer Solana data and transaction services with Tokyo connectivity. This comparison is based on each provider's official documentation and published features, checked in November 2026; we have not tested the tools hands-on.

Which one to pick

  • Need Tokyo-based EVM RPC: Alchemy, with Node RPC, WebSockets and dedicated infrastructure available in Tokyo for supported networks.
  • Trade Solana with regional streaming: Helius, with a Tokyo LaserStream region, Sender transaction delivery and preprocessed transaction data.
  • Need raw Solana transaction feeds in Tokyo: Triton RPC, with a dedicated Tokyo shred delivery service.
  • Trade across multiple chains, including Japan Open Chain: QuickNode, with broad network coverage and documented JOC mainnet access.
  • Need transaction routing and multi-chain infrastructure: Chainstack, with Global Nodes, Warp transactions and Solana Geyser streaming.
  • Prefer transparent per-request billing: Ankr, with published HTTPS prices for EVM and Solana RPC calls.

Compare RPC coverage and Japan connectivity

ToolType / use caseJapan connectivityPrice
AlchemyMulti-chain RPC and dedicated infrastructureTokyo RPC and WebSockets on supported chains30M free CUs/month; $0.525/1M CUs PAYG
HeliusSolana RPC and trading dataLaserStream includes Tokyo; regional Sender endpointsFree; paid from $49/month
Triton RPCSolana RPC, gRPC and raw shredsTokyo Solana shred feed$25 prepaid; Tokyo shreds $900/month or $0.35/15 min/IP
QuickNodeMulti-chain RPC and data servicesJapan Open Chain mainnet; no Tokyo POP claimOne-month free trial; paid from $49/month
ChainstackGeo-balanced RPC and transaction routingGlobal routing; specific Tokyo site not statedFree; Growth $49/month; Warp $0.15/transaction
AnkrMetered multi-chain RPCGlobal node coverage; city-level POP not specified200M free credits/month; EVM $0.00002 and Solana $0.00005 per HTTPS call
dRPCMulti-chain EVM and Solana RPCTokyo region not specified in public plan documentationFree 50M CUs/month; PAYG $6/1M requests; Pro $49/month
GetBlockShared and dedicated RPC nodesSingapore, Frankfurt and US East on listed major networksFree entry; paid CU subscriptions
InfuraEVM RPC and WebSocket subscriptionsTokyo location not publishedFree; Developer $50/month; Team $225/month

The tools

Alchemy

Tokyo-routed multi-chain RPC

Type / use caseMulti-chain RPC and dedicated infrastructurePrice30M free CUs/month; $0.525/1M CUs PAYG

Alchemy combines managed RPC, WebSockets and dedicated infrastructure across EVM and non-EVM networks. Its September 2026 regional announcement confirms Tokyo service for Node RPC, WebSockets and Dedicated Clusters. Named launch networks include Ethereum, Base, BNB Smart Chain, Robinhood Chain, HyperEVM and Arc. Requests for networks not yet served there are routed to another supported region. The pricing page lists 30 million free compute units monthly and pay-as-you-go billing at $0.525 per million CUs.

Choose it when your trading infrastructure runs in Japan and your target chain is included in its Tokyo deployment.

Watch out for chain-dependent regional coverage. A Tokyo deployment does not mean every supported network receives the same routing treatment.

Helius

Solana trading infrastructure

Type / use caseSolana RPC and trading dataPriceFree; paid from $49/month

Helius provides Solana RPC nodes, transaction submission and live data services. Its LaserStream product lists nine regions, including Tokyo, and supports real-time account, slot and program feeds with automatic reconnection and historical replay. Plan features differ: Free includes standard WebSockets, Developer costs $49 monthly, and Business at $499 monthly adds LaserStream gRPC. Sender is available on all plans; SWQOS-only tips start at 0.000005 SOL, while Sender Max starts at 0.001 SOL. Dedicated infrastructure is also available for larger trading operations.

Choose it when Solana is your primary execution chain and you need RPC, streaming and transaction delivery in one provider ecosystem.

Watch out for plan-specific streaming limits. Full LaserStream gRPC access requires a higher subscription, and Sender's regional endpoints should not be confused with the LaserStream regional deployment.

Triton RPC

Solana RPC and raw shred delivery

Type / use caseSolana RPC, gRPC and raw shredsPrice$25 prepaid; Tokyo shreds $900/month or $0.35/15 min/IP

Triton provides Solana-oriented RPC and streaming infrastructure, alongside endpoints for Sui and Monad. Standard RPC and unary gRPC are billed by calls and bandwidth. Its separate Shred Streaming service forwards signed raw Solana packets to a registered IP and port. Tokyo is one of its delivery cities, priced at $900 monthly or $0.35 per 15-minute interval per IP and data centre. The current pay-as-you-go account requires a $25 prepaid balance, usable for 12 months.

Choose it when your Solana strategy needs direct access to raw transaction data from a Tokyo delivery location.

Watch out for the engineering requirements. Raw shreds are not decoded RPC responses; your infrastructure must recover packets and reconstruct transactions. The Tokyo feed is a separate product, not proof that every standard RPC request is served from Tokyo.

QuickNode

Broad multi-chain infrastructure

Type / use caseMulti-chain RPC and data servicesPriceOne-month free trial; paid from $49/month

QuickNode offers managed full and archive nodes across more than 70 networks, with Streams, webhooks and chain-specific add-ons. Its Japan Open Chain documentation lists mainnet access over HTTP, archive data and Ethereum JSON-RPC alongside Debug API support. Pricing starts with a one-month trial; the Build plan is $49 monthly, or $34 per month with annual billing.

Choose it when you need several blockchain connections and want to include Japan Open Chain in the same infrastructure stack.

Watch out for API credit consumption. Different methods have different resource costs, so heavy historical queries and frequent reads can produce different bills from simple request counts.

Chainstack

Geo-balanced RPC and transaction routing

Type / use caseGeo-balanced RPC and transaction routingPriceFree; Growth $49/month; Warp $0.15/transaction

Chainstack covers Ethereum, Solana, BNB Smart Chain, Base, Arbitrum and Hyperliquid through its Global Nodes product. Requests are distributed through a geo-balanced network, with one request unit for full-node calls and two for archive access. The Growth subscription is $49 monthly. Separate trading products include Warp transaction routing at $0.15 per transaction and Yellowstone Geyser gRPC for Solana. Chainstack has announced that regional Trader Nodes will retire on 1 December 2026.

Choose it when you want multi-chain connectivity alongside dedicated transaction-delivery and streaming products.

Watch out for regional assumptions. Global routing does not promise a Tokyo-resident node, and the published architecture uses DNS-based routing for full-region recovery, which can take seconds.

Ankr

Metered multi-chain RPC

Type / use caseMetered multi-chain RPC

Ankr's Node API supplies standard JSON-RPC for more than 80 networks, including Ethereum, Solana, BNB Smart Chain, Base, Arbitrum, Bitcoin and Sui. Its Advanced API adds indexed cross-chain queries. Freemium accounts receive 200 million API credits monthly but retain Public rate limits. Premium unlocks private endpoints, WebSockets and trace/debug methods. Published HTTPS prices are $0.00002 per EVM call and $0.00005 per Solana call, with separate billing rules for streaming and gRPC.

Choose it when your trading system makes substantial multi-chain requests and you want method-level usage costs.

Watch out for the metered billing model. Different request types consume different credits, and public or freemium access retains shared rate restrictions.

dRPC

Multi-chain RPC with CU billing

Type / use caseMulti-chain EVM and Solana RPCPriceFree 50M CUs/month; PAYG $6/1M requests; Pro $49/month

dRPC exposes multi-chain and Solana RPC through public and premium node pools. Its current plan documentation shows 50 million CUs monthly on Free, pay-as-you-go at $6 per million requests, and Pro at $49 monthly. Paid plans add archive, debug and trace methods, WebSockets and Solana gRPC. The included CU pool can be used across multi-chain and Solana requests.

Choose it when you want EVM and Solana access under one usage-based account.

Watch out for the free-tier restrictions. Free access uses public nodes and does not include archive, debugging, trace or WebSocket features. Unused monthly CU allowances also do not roll over.

GetBlock

Shared and dedicated RPC nodes

Type / use caseShared and dedicated RPC nodesPriceFree entry; paid CU subscriptions

GetBlock offers shared, dedicated and Limitless RPC infrastructure across more than 130 networks. Its catalogue lists JSON-RPC and WebSocket access for Ethereum, BNB Smart Chain, Solana, Base and Arbitrum. Solana options include Yellowstone gRPC and shred-stream add-ons, while archive and MEV-protected access vary by network. For major chains, the published regional choices include Frankfurt, US East and Singapore. Shared access starts free and scales through compute-unit subscriptions; dedicated configurations are separately provisioned.

Choose it when you want to begin with shared infrastructure and move to private node capacity as trading traffic grows.

Watch out for regional availability. Singapore is the listed Asian location for these major networks, not Tokyo, and interfaces or archive support differ by chain.

Infura

Established EVM RPC and event subscriptions

Type / use caseEVM RPC and WebSocket subscriptionsPriceFree; Developer $50/month; Team $225/month

Infura is an EVM-oriented RPC service with more than 40 supported networks, full archive access and credit-based usage. Its WebSocket documentation covers subscriptions such as new heads and logs on Ethereum, Base, Arbitrum, Polygon, Optimism and other supported chains. Pending-transaction subscriptions are not available everywhere. The Core tier is free, Developer costs $50 monthly and Team costs $225 monthly.

Choose it when your trading infrastructure relies on established EVM networks and standard RPC subscriptions.

Watch out for plan quotas and network-specific WebSocket support. Developer or higher is needed for documented Debug and Trace API access, and the public pricing information does not specify a Tokyo region.

How to benchmark an RPC provider for on-chain trading from Japan

  1. Identify your execution workload. Write down the chains and venues you use, then separate ordinary state reads, historical queries, event subscriptions and transaction submissions. EVM traders should check methods such as eth_blockNumber, eth_getLogs and eth_sendRawTransaction. Solana traders should include getSlot, getLatestBlockhash, sendTransaction and the subscriptions they actually consume.
  2. Shortlist providers by regional coverage. Check Alchemy's Tokyo network list for EVM trading. For Solana, compare Helius LaserStream's TYO region with Triton's Tokyo shred feed. If you trade Japan Open Chain, verify QuickNode's JOC endpoint and method support. Do not treat an Asia-Pacific or global-routing statement as proof of a Tokyo deployment.
  3. Run the test from your real execution host. Provision endpoints and API keys, then test from the same cloud server or data centre that will run your bot. A benchmark from a personal laptop or unrelated VPN connection does not represent the route used by your production trading system.
  4. Measure read freshness and streaming quality. Send repeated block or slot queries and compare returned heights, response-time percentiles, HTTP errors and rate-limit responses. For WebSockets or gRPC, measure event arrival, disconnect frequency, reconnection time, missed updates and recovery behaviour.
  5. Test transaction submission separately. Use a controlled testnet or small-value transaction. Record the provider's response, transaction hash, time until first network observation, inclusion block and confirmation status. Compare these results rather than treating a successful JSON-RPC response as proof of execution.
  6. Calculate the actual operating cost. Replay your expected request mix against each pricing model. Include archive calls, subscriptions, gRPC bandwidth, transaction-routing fees, dedicated capacity and retries. Ankr's per-call prices, Chainstack's RUs and Alchemy's CUs are not directly interchangeable.
  7. Configure a primary and fallback. Keep independent provider credentials, monitor chain-head freshness and reconnect subscriptions after failover. If a submission times out, check the transaction hash, account nonce or signature status before resending.

Worked example (illustrative): Suppose a Tokyo-hosted EVM bot records 24 ms p95 read latency and 0.4% errors on Provider A, compared with 31 ms and no errors on Provider B over 1,000 requests. If both return the same chain head and Provider B passes the controlled transaction test, routing writes through B may be more appropriate despite its higher read latency. Keep A available as a fallback after verifying its own submission behaviour.

Trading risks to manage

An RPC acknowledgement does not guarantee transaction inclusion: a provider can accept a signed payload while a validator or sequencer never processes it. Stale chain state can distort quotes and balances, while careless retries can create nonce conflicts or duplicate execution attempts. Keep credentials server-side, protect strategy-sensitive order flow and reconcile transaction hashes, receipts and slot status before resubmitting.

Frequently asked questions

Which RPC providers have a Tokyo data path?

Alchemy documents Tokyo availability for Node RPC and WebSockets on supported networks. Helius includes Tokyo in its LaserStream regional deployment, while Triton offers a separate Tokyo Solana shred-delivery product. These are different service types, not interchangeable Tokyo RPC endpoints.

Does QuickNode's Japan Open Chain support mean it has a Tokyo server?

No. QuickNode documents JOC mainnet connectivity and archive support, which confirms access to that blockchain. It does not establish the physical location of the node serving a particular request.

Should Solana traders use Helius or Triton?

Helius combines ordinary Solana RPC, transaction submission and regional streaming. Triton is particularly relevant when you need raw shreds delivered to your own infrastructure in Tokyo. The choice depends on whether you need decoded application-level data or raw network packets.

Can RPC latency affect slippage?

RPC quality can affect how fresh your market information is and how quickly a signed transaction reaches the network. It does not improve pool liquidity or eliminate price impact. Trade size and execution conditions still matter; read the guide to slippage and price impact.

Does a successful RPC response mean my trade has landed?

No. Check the transaction receipt or Solana signature status to confirm inclusion.

Should I run two RPC providers simultaneously?

For production trading, an independent backup can reduce dependence on one provider's availability or rate limits.

Sources

Show all 21 sources