Regions & Latency
Choose the right region and tier for your bots based on cost, latency, and exchange proximity.
Overview
Every bot runs on a dedicated compute instance — a single-tenant instance per bot, never shared with another bot. When you deploy a bot, you select a region and a tier. The instance is provisioned automatically and torn down when you stop the bot. Bots with trading sessions also sleep between sessions, deprovisioning the instance automatically to save costs.
plutarc offers regions across EU, US, and Asia-Pacific. Each region has a friendly city name and a stable, provider-neutral code (e.g. ap-southeast-1). Every region delivers the same bot functionality — the difference is pricing and proximity to exchange matching engines.
Standard vs Performance
Every location comes in one of two compute classes. You pick a class and a location when you deploy — there is no server sizing to configure.
Standard
Our most cost-effective instances, from £0.04/hr. Your bot still runs single-tenant on its own instance; it shares underlying capacity with other tenants to keep costs low. Ideal for swing and low-frequency strategies where a few milliseconds of latency jitter is irrelevant.
Performance
Dedicated compute with no noisy neighbours — for latency-sensitive execution. From £0.24/hr.
Both classes run one bot per instance (single-tenant to your bot). The difference is whether the underlying compute is dedicated or shared.
Regions
Europe
eu-north-1standardperformance£0.04–0.24/hreu-central-1standardperformance£0.04–0.24/hreu-central-2standardperformance£0.04–0.24/hreu-west-1standardperformance£0.12–0.34/hreu-west-2standardperformance£0.12–0.35/hreu-west-3performance£0.27/hrAmericas
us-east-1standardperformance£0.10–0.24/hrus-west-1standardperformance£0.10–0.24/hrAsia-Pacific
ap-southeast-1standardperformance£0.15–0.30/hrap-southeast-2performance£0.27/hrap-southeast-3performance£0.38/hrap-northeast-1performance£0.27/hrap-northeast-2performance£0.39/hrap-east-1performance£0.42/hrSee the Pricing page for the full per-region breakdown.
Choosing a Region
The most important factor is proximity to the exchange matching engine. Deploying in the same city as the matching engine minimises round-trip latency for order placement, fills, and position updates.
Exchange Matching Engine Locations
| Exchange | Matching Engine |
|---|---|
| BitMEX | Tokyo |
| Bybit | Singapore |
| Binance | Tokyo |
| Kraken | London |
| OKX | Singapore |
| KuCoin | Tokyo |
| Deribit | Amsterdam |
| Gemini | New York |
| Phemex | Singapore |
| WooX | Singapore |
Datacenter locations are based on publicly available information and may change without notice.
Latency by Region
Approximate round-trip time from each deployment region to exchange API servers, measured periodically by probes in each datacenter.
| Region | BitMEX | Bybit | Binance | Kraken | OKX | KuCoin | Deribit | Gemini | Phemex | WooX |
|---|---|---|---|---|---|---|---|---|---|---|
Helsinki, Finland eu-north-1 | ~325ms | ~207ms | ~275ms | ~137ms | ~266ms | ~313ms | ~88ms | ~402ms | ~32ms | ~337ms |
Falkenstein, Germany eu-central-1 | ~308ms | ~217ms | ~297ms | ~90ms | ~254ms | ~303ms | ~15ms | ~105ms | ~220ms | ~220ms |
Dublin, Ireland eu-west-1 | ~275ms | ~204ms | ~233ms | ~79ms | ~232ms | ~257ms | ~44ms | ~285ms | ~33ms | ~265ms |
London, UK eu-west-2 | ~247ms | ~187ms | ~244ms | ~47ms | ~227ms | ~268ms | ~22ms | ~80ms | ~196ms | ~196ms |
London, UK eu-west-3 | ~251ms | ~191ms | ~242ms | ~43ms | ~223ms | ~265ms | ~20ms | ~78ms | ~194ms | ~194ms |
Nuremberg, Germany eu-central-2 | ~317ms | ~244ms | ~316ms | ~95ms | ~259ms | ~304ms | ~18ms | ~108ms | ~216ms | ~216ms |
Ashburn, USA us-east-1 | ~227ms | N/A | N/A | ~128ms | ~262ms | ~214ms | ~95ms | ~12ms | ~220ms | ~220ms |
Hillsboro, USA us-west-1 | ~131ms | N/A | N/A | ~206ms | ~176ms | ~137ms | ~168ms | ~42ms | ~270ms | ~185ms |
Singapore ap-southeast-1 | ~138ms | ~25ms | ~118ms | ~230ms | ~96ms | ~135ms | ~210ms | ~240ms | ~28ms | ~28ms |
Singapore ap-southeast-2 | ~127ms | ~25ms | ~97ms | ~209ms | ~76ms | ~109ms | ~195ms | ~235ms | ~25ms | ~25ms |
Singapore ap-southeast-3 | ~124ms | ~30ms | ~102ms | ~218ms | ~76ms | ~114ms | ~200ms | ~240ms | ~32ms | ~32ms |
Tokyo, Japan ap-northeast-1 | ~42ms | ~96ms | ~27ms | ~290ms | ~86ms | ~33ms | ~270ms | ~175ms | ~95ms | ~95ms |
Tokyo, Japan ap-northeast-2 | ~60ms | ~100ms | ~28ms | ~284ms | ~91ms | ~32ms | ~276ms | ~605ms | ~37ms | ~39ms |
Hong Kong ap-east-1 | ~116ms | ~61ms | ~159ms | ~233ms | ~40ms | ~97ms | ~225ms | ~210ms | ~61ms | ~61ms |
N/A indicates the exchange does not support API access from that region.
Green (<50ms) = same geographic area as matching engine. Amber (50–150ms) = adjacent region. Red (>150ms) = cross-continental.
When Latency Matters
Not every strategy needs the lowest possible latency. Consider your timeframe:
- Short timeframes (1m, 5m) — Latency has a direct impact on fill quality. Deploy in the same city as the exchange matching engine for the best results. Asia-Pacific regions (Singapore, Tokyo) are recommended for exchanges with Asia-Pacific matching engines (BitMEX, Bybit, Binance, OKX, KuCoin, Phemex, WooX). EU regions suit Deribit (Amsterdam) and Kraken (London). US-East regions suit Gemini (New York).
- Medium timeframes (15m, 1h) — Adjacent regions (amber latency) are generally fine. The difference between 30ms and 100ms is negligible when candles close every 15–60 minutes.
- Long timeframes (4h, 1d) — Region choice has minimal impact on execution quality. EU Standard regions offer the best value.
Cost vs Latency
There is a clear trade-off between cost and proximity to APAC exchange matching engines:
- Budget-friendly — EU Standard (from £0.04/hr). Cross-continental latency to APAC exchanges, but excellent for longer timeframes or EU-based exchanges like Kraken.
- Balanced — Singapore regions (from £0.27/hr). Good latency to Bybit, Binance, and OKX at moderate cost.
- Lowest latency — Tokyo or Singapore Performance regions (£0.27–0.42/hr). Best for latency-sensitive strategies trading on 1m–5m candles.
Every region delivers the same bot functionality, strategy evaluation, and risk management. The only differences are pricing and network latency to the exchange.