For the complete documentation index, see llms.txt. This page is also available as Markdown.

QUIC Transaction Submission

Astralane's QUIC endpoint provides a faster, more efficient path for submitting Solana transactions compared to traditional HTTP/JSON-RPC.

Available Endpoints

  • Location
    IP Address
    MEV Protected IP address

    Frankfurt (Recommended)

    185.191.117.97:7000

    185.191.117.97:9000

    Frankfurt

    45.139.132.160:7000

    45.139.132.160:9000

    San Francisco

    74.118.142.151:7000

    74.118.142.151:9000

    Tokyo

    189.1.164.31:7000

    189.1.164.31:9000

    New York

    64.130.45.19:7000

    64.130.45.19:9000

    Amsterdam (Recommended)

    64.130.43.43:7000

    64.130.43.43:9000

    Amsterdam

    84.32.186.73:7000

    84.32.186.73:9000

    Limburg

    162.19.222.232:7000

    162.19.222.232:9000

    Singapore

    67.209.54.176:7000

    67.209.54.176:9000

    Lithuania

    84.32.97.47:7000

    84.32.97.47:9000

    London

    63.254.168.71:7000

    63.254.168.71:9000

JSON-RPC VS QUIC

Parameter
HTTP/JSON-RPC
QUIC

Latency

HTTP overhead + JSON serialization/deserialization

Direct binary stream, sub-millisecond send

Connection

New TCP connection per request (or keep-alive with limits)

Single persistent QUIC connection, multiplexed streams

Concurrency

Sequential requests or multiple connections

Up to 64 concurrent streams on a single connection

Serialization

JSON-RPC wrapping + base64/base58 encoding

Raw bincode bytes; no encoding overhead

Reconnection

Manual retry logic required

Automatic transparent reconnection built into the client

Protocol overhead

TCP + TLS handshake per connection

0-RTT capable, built-in encryption

Why Use astralane-quic-client?

  • Zero-config authentication : TLS certificate with your API key is generated automatically

  • Automatic reconnection : transparent recovery from timeouts and server restarts

  • Fire-and-forget : no response parsing or callback handling needed

  • Connection keep-alive : persistent connection with automatic 25s keep-alive pings, no repeated handshakes

  • Built-in backpressure : stream limits are handled gracefully without dropping your connection

Only authentication errors (UNKNOWN_API_KEY) require manual intervention, verify your API key is correct and active.

Getting Started

The recommended way to interact with Astralane's QUIC endpoint is through the official astralane-quic-client.

Installation

Quick Example


Server Limits

Parameter
Value
Description

Max connections per API key

10

Create multiple client instances for more connections

Max concurrent streams per connection

64

Streams beyond this limit will block until a slot frees up

Stream read timeout

750 ms

Server closes the stream if transaction bytes aren't received in time

Max transaction size

1232 bytes

Standard Solana transaction size limit

Idle timeout

30 s

Connection closes if no activity; client sends keep-alive every 25s


Error Codes

The server may close your connection with these application-level error codes:

Code
Name
When It Happens

0

OK

Normal closure (client or server initiated)

1

UNKNOWN_API_KEY

API key not recognized (check your API key is valid and active)

2

CONNECTION_LIMIT

Too many connections for this API key (close unused connections or contact support for a higher limit)

Rate Limiting

When the rate limit is exceeded, the server silently drops excess transactions. The connection stays alive - no error is returned to the client. Monitor your transaction landing rate to detect if you're being rate limited.

Stream Limits

When the concurrent stream limit (64) is reached, the client will block (backpressure) until a stream slot frees up. The server does not close the connection, your send call will simply take longer to return.

Last updated