Regions & endpoints

Regions

All products are available in every region. You choose your regions when you request access, and your endpoints are provided for those regions.

Endpoints

Endpoints are not published. You receive them together with your API key, for the products and the region in your offer. Treat them like your credentials and never share them publicly (see Terms).

The code examples in these docs read the endpoints from environment variables:

All endpoints use TLS. Plain-text connections are not accepted.

Choosing a location

• Host your strategy in the same city as the endpoint, ideally in the same data center. Every additional network hop adds latency.
• Pick the region where your strategy runs. Frankfurt, where our main validator is located, is one of the main hubs of Solana validator infrastructure, which also shortens the path to many slot leaders.
• Measure the round-trip time from your server before going live, for example with ping or mtr. See Latency & benchmarking.

Checking the network path

# Host name of one of your endpoints, without https:// or a port
HOST=your-endpoint-host

# Round-trip time and packet loss on every hop
mtr --report --report-cycles 50 "$HOST"

# TLS handshake time to an endpoint
curl -o /dev/null -s -w "connect: %{time_connect}s  tls: %{time_appconnect}s\n" "$MEV_SEND_URL"

From a server in the same Frankfurt data center, the round-trip time is typically below 1 millisecond. From elsewhere in Frankfurt it is typically a few milliseconds.

Shreds are delivered to a server in the same region with a median latency (p50) of 3 milliseconds.