1. [Home](https://fxapis.com/) 2. / 3. Benchmarks Benchmarks · measured 29 September 2026 # fxapis, measured. Not promised. Three numbers describe how fxapis feels in use: how long an account takes to come online, how long an order takes to reach the broker and back, and how close together orders leave when you trade many accounts at once. Here is each one, how we measured it, and what changes it in the real world. Connect to online Measured 9.6seconds From asking for an account to come online until it is signed in at the broker and ready to trade. One run. Order round trip Measured 96–110ms From our servers sending an order to the broker's answer, to a broker with trade servers in London. 100-account spread Measured 30ms Between the first and the last of 100 accounts' orders leaving fxapis, in one multi-account order, in a local benchmark against an instant broker. 1 · Connect to online ## 9.6 seconds. **What:** the time from `POST /v1/accounts/prepare` to the account's status reading `ready` — signed in at the broker, prices arriving, orders accepted. **Where and against what:** our production service in the EU (Amsterdam), with a retail broker's MetaTrader 5 demo account whose trade servers are in London, on 29 September 2026. This figure is from one run. **What it means for you:** an account in on-demand mode that has gone offline — after 15 quiet minutes — needs about this long before its first order. That is why click-to-trade prepares a member's account when they *open* a signal, not when they approve it, and why accounts that must react instantly should be always connected. Once an account is online, orders go straight through. Sign-in time also depends on the broker's own servers. A busy broker can take longer, which is why the [polling guide](https://docs.fxapis.com/accounts#polling-well) suggests a generous timeout. 2 · Order round trip ## 96–110 milliseconds. **What:** the time from our server sending a market order to the broker's trade server returning its answer, for an account that was already online. **Where and against what:** the same production service and demo account, on 29 September 2026. Our servers are in Amsterdam; the broker's trade servers are in London. The figure includes the broker's own time to process the order. 1. 01 Your backend Anywhere 2. 02 fxapis API EU · Amsterdam 3. 03 MT5 terminal Our cloud, same region 4. 04 Broker trade server Wherever your broker runs it The measured round trip covers steps 3 → 4 → 3: 96–110 ms to a London broker The time from your backend to our API is added on top, and depends on where your servers are. 3 · Multi-account spread ## 30 ms across 100 accounts. **What:** in a multi-account order, the time between the first account's order being sent and the last one's, measured from each order's own send time. Every multi-account order reports this figure as `dispatchSpreadMs`, so you can watch it on your own trades. **Against what:** a local broker that answers instantly. That removes the broker's latency — which differs by broker and by moment — and leaves the part fxapis controls: how close together it sends the orders. **What it shows:** the cost per account falls as the order grows, which is what sending in parallel should look like. Real brokers add their own execution time to each account, so fills will still arrive at slightly different moments and prices. EURUSD · buy · 100 accounts 30 msfirst account to last Benchmark 17 ms 26 ms 30 ms 10 accounts50 accounts100 accounts Time from the first account's order to the last, by number of accounts, in our benchmark against an instant broker — every multi-account order reports its own spread. The more accounts you trade at once, the less each one adds: 1.7 ms at 10 accounts, 0.3 ms at 100. | Aspect | First to last | Per account | | ------------ | ------------- | ----------- | | 10 accounts | 17 ms | 1.70 ms | | 50 accounts | 26 ms | 0.52 ms | | 100 accounts | 30 ms | 0.30 ms | In the real world ## What changes your numbers. - **Your broker.** Where its trade servers are, and how it executes orders, matter more than anything else. A broker in New York or Asia will be further from our EU servers than one in London. - **Whether the account is online.** An offline account signs in first — about 10 seconds. Keep time-critical accounts always connected, or prepare them ahead. - **The market.** Around news, prices move quickly; brokers requote or reject orders whose price has moved beyond the deviation you allow. - **Your own servers.** The time from your backend to our API is on top of everything here. Servers in or near the EU keep it small. - **How many accounts at once.** Larger multi-account orders spread slightly wider, but each extra account adds less. On demand and always-on are different clocks An on-demand account starts when you trade and stops when it has been idle. The first order waits for that start, usually seconds, sometimes longer if the broker is slow. An always-on account keeps the terminal running, so it does not pay that start. The figures on this page are not a promise for a cold account. Modes and the always-on price are on the [pricing page](https://fxapis.com/pricing). A TradingView hook that fires while the account is offline gets `ACCOUNT_NOT_READY` and nothing is sent. What we have not measured yet Uptime over a long period, brokers in other regions, and very large multi-account orders against real brokers. We will add them here when we have measured them — not before. FAQ ## About these numbers ### Are these numbers guaranteed? No. They are measurements of our own service under the conditions described on this page. Your results depend on your broker, where its trade servers are, the market at the time and where your own servers are. Service levels are only agreed in an Enterprise contract. ### Why is the multi-account spread measured against an instant broker? To isolate our own contribution. A real broker adds its own execution time to every order, and that time varies from broker to broker and moment to moment. Measuring against a broker that answers instantly shows how far apart fxapis sends the orders, which is the part we control. ### Why is the round trip about 100 milliseconds? It is the time from our servers sending an order to the broker's trade server answering, and it includes the broker's own processing. Our servers are in Amsterdam; the broker we measured keeps its MT5 trade servers in London. A broker with servers elsewhere, or a slower execution model, will show a different number. ### How do I get the fastest execution? Keep accounts that must act instantly in always-connected mode, or bring them online ahead of time with POST /v1/accounts/prepare, so no order waits for a sign-in. Run your own backend close to our EU servers, and set a sensible price deviation so fast markets don't cause needless rejections. ### Do you publish uptime figures? Not yet. We will publish uptime once there is a long enough record to make the figure meaningful, and not before. See how the numbers shape a product: [click-to-trade for signal providers](https://fxapis.com/solutions/signal-providers) and [copy trading on multi-account orders](https://fxapis.com/solutions/copy-trading). \> Connect. Execute. Scale. ## Measure it on your own broker. Connect a demo account at your broker and time your first orders yourself. [Get API key](https://fxapis.com/sign-up) [ ](https://fxapis.com/sign-up) [Quickstart](https://docs.fxapis.com/quickstart)