Arcus API Latency — TESTNET

This is [TESTNET]. Switch to [MAINNET].

Place Order Latency

How quickly the Arcus API confirms a new order — the time from sending the order until the exchange's reply comes back. Error% = how often the API didn't reply within 10 seconds.

PeriodSamplesError%AverageMedianMint75%t85%t95%MaxStart_TimeEnd_Time
24 hours14040.000%0.1480.1370.1210.1460.1550.1940.8892026-10-17 02:19:01 UTC2026-10-18 02:19:01 UTC
7 days100320.000%0.1450.1390.0800.1480.1570.1853.1962026-10-11 02:19:02 UTC2026-10-18 02:19:01 UTC

Websocket Latency

How quickly a new order shows up on Arcus's live order feed — the real-time WebSocket stream that trading bots and the website watch for order and account updates. Error% = how often the order never appeared on the feed within 20 seconds.

PeriodSamplesError%AverageMedianMint75%t85%t95%MaxStart_TimeEnd_Time
24 hours14040.285%0.1690.1720.1200.1820.1890.2240.7742026-10-17 02:19:01 UTC2026-10-18 02:19:01 UTC
7 days100320.040%0.1450.1370.0790.1490.1660.1904.0322026-10-11 02:19:02 UTC2026-10-18 02:19:01 UTC
Note: Measurements taken from Tokyo, Japan.

Legend

Error%Error Rate
AverageAverage Latency (in seconds)
MedianMedian Latency (in seconds)
MinMinimum Latency (in seconds)
t75%75% below this latency (in seconds)
t85%85% below this latency (in seconds)
t95%95% below this latency (in seconds)
MaxMaximum latency (in seconds)

How these are measured

One test order is timed two ways from the moment it is sent: Place Order Latency (until the Arcus API replies) and Websocket Latency (until the order appears on the live WebSocket feed). One test order is timed two ways from the moment it is sent: Place Order Latency (until the Arcus API replies) and Websocket Latency (until the order appears on the live WebSocket feed).
Generated: Sun Oct 18 02:20:02 UTC 2026 / Runtime 0 seconds / Automatically updated every 5 minutes