Performance, keep-alive and monitoring

QUIC Keep-Alive

Recommended settings:

• Keep-alive ping: every 3 seconds
• Timeout: 10–15 seconds

Benefits:

• No reconnection cost
• Predictable 0.1ms dispatch
• Session stability for high-frequency bots

const client = new QuicClient("fastrelay.sh:4433", {
  keepAlive: true,
  keepAliveInterval: 3000,
  keepAliveTimeout: 15000,
});

HTTPS Keep-Alive

Use the /keepalive endpoint to keep your HTTP connection warm and monitor server status:

import axios from "axios";
import https from "https";

const agent = new https.Agent({ keepAlive: true });

const api = axios.create({
  baseURL: "https://fastrelay.sh",
  httpsAgent: agent,
});

// Poll every 5-10 seconds to maintain connection
setInterval(async () => {
  const { data } = await api.get("/keepalive");
  console.log("Server time:", data.server_time, "Slot:", data.slot);
}, 5000);

Response:

{
  "status": "alive",
  "server_time": "2026-05-02T12:00:00.000Z",
  "region": "fra",
  "slot": 312345678
}

This keeps the TCP connection alive, avoids repeated TLS handshakes, and gives you real-time server status.

Broadcast Pipeline

Every transaction is delivered through 5 parallel channels for maximum inclusion probability:

Latency Breakdown

Throughput

• QUIC: Up to 10,000 tx/s per connection
• HTTPS: Up to 1,000 tx/s per connection

For the absolute lowest latency, clients are strongly encouraged to co-locate their bots or trading engines with the relay.

Colocation Benefits

• Direct, private, ultra-fast link to the relay
• True sub-millisecond transaction dispatch
• Leader-aware execution
• Guaranteed throughput
• Access to private QUIC lanes
• Priority engineering support

Colocation Locations

• Frankfurt: TeraSwitch

Get in touch to secure a colocation slot.

Contact AllenHark | View Co-Location Details

Ping Service

To verify connectivity to the relay, use the ping endpoint:

# Primary (Frankfurt)
curl https://fastrelay.sh/ping

# Regional
curl https://fra.fastrelay.sh/ping
curl https://ams.fastrelay.sh/ping
curl https://ny.fastrelay.sh/ping
curl https://tyo.fastrelay.sh/ping

Response:

pong

1. Use QUIC for Production: Always use QUIC for production trading systems
2. Implement Retry Logic: Handle network errors with exponential backoff
3. Monitor Tip Amounts: Increase tips during network congestion
4. Keep Connections Alive: Maintain persistent connections for best performance
5. Use Nearest Region: Connect to the relay region closest to your infrastructure
6. Co-locate if Possible: For true 0.1ms, co-locate your infrastructure
7. Test on Devnet First: Always test integration on devnet before mainnet