Documentation

Limits

Plan around send rates, key limits, request sizes, connections and timeouts

// updated 2026-11-17

Submission rate

The default is 15 sends per second per key at each metro, with bursts of up to one second. Each metro counts separately, whichever hostname reaches it; fra.tpu.supanode.xyz counts against the metro that serves you. Each transaction uses one submission; queries do not count. Bundles have their own rate.

Supanode confirms your key rate when issuing it. Request higher limits through Supanode on Telegram.

For rate_limited, use per_second and retry_after_ms when included. Slow down and wait before retrying; more connections do not raise the rate.

Issued keys

Supanode issues and manages keys through Telegram. Request additional keys, replacement or revocation there. Direct-provider team-account limits do not define your customer allocation.

Request sizes

RequestLimit
Legacy or v0 transaction1,232 wire bytes
v1 transaction4,096 wire bytes
Bundle1 to 4 transactions, each within its transaction limit
JSON-RPC request65,536 body bytes; one request per call, batches are refused

Use base64 for transactions above 1,232 bytes. See JSON-RPC, HTTP and QUIC for exact request formats.

too_large reports the allowed limit and the submitted size when known. For a bundle, index identifies the affected transaction.

Connections

Reuse connections across submissions.

Hosted connectionLimit per metro host
HTTP/HTTPS from one source IPv4 address256 open connections combined
QUIC using one API key32 open connections

Timeouts

Finish writing request bodies within 2 seconds. If a request times out or disconnects, its outcome may be unknown: check the transaction's signature before replacing it.

Busy metros

For overloaded or a temporary not_ready, wait and retry while the transaction is valid, or choose another metro host.

Declared tips

Arrange declared tips with support before using them. See Billing for payment and account guidance.