Skip to content
Four regionsFastRelay runs independent relay instances in Frankfurt, Amsterdam, New York, Tokyo.NYAMSFRATYO
FastRelay runs independent relay instances in Frankfurt, Amsterdam, New York, Tokyo.

Endpoints — four regions, three transports

FastRelay operates across multiple regions. Each region runs an independent relay instance with the full 5-channel broadcast pipeline.

QUIC Endpoints (Recommended)

QUIC connects to the region host on port 4433. Resolve the name once when you open the connection, then reuse the connection for every transaction:

RegionQUIC Address
Frankfurt (Primary)fra.fastrelay.sh:4433
Amsterdamams.fastrelay.sh:4433
New Yorkny.fastrelay.sh:4433
Tokyotyo.fastrelay.sh:4433

HTTPS Endpoints

POST /v1/sendTx and POST /v1/sendBundle are served over both HTTPS and plain HTTP on the same host. HTTP skips the TLS handshake on a fresh connection; HTTPS encrypts the request (and your API key) in transit:

RegionHTTPSHTTP
Frankfurt (Primary)https://fra.fastrelay.sh/v1/sendTxhttp://fra.fastrelay.sh/v1/sendTx
Amsterdamhttps://ams.fastrelay.sh/v1/sendTxhttp://ams.fastrelay.sh/v1/sendTx
New Yorkhttps://ny.fastrelay.sh/v1/sendTxhttp://ny.fastrelay.sh/v1/sendTx
Tokyohttps://tyo.fastrelay.sh/v1/sendTxhttp://tyo.fastrelay.sh/v1/sendTx

WebSocket Endpoints

Persistent wss:// streams. Two paths per region — one for single transactions and one for atomic bundles:

RegionSingle-tx streamBundle stream
Frankfurt (Primary)wss://fra.fastrelay.sh/v1/stream/txwss://fra.fastrelay.sh/v1/stream/bundle
Amsterdamwss://ams.fastrelay.sh/v1/stream/txwss://ams.fastrelay.sh/v1/stream/bundle
New Yorkwss://ny.fastrelay.sh/v1/stream/txwss://ny.fastrelay.sh/v1/stream/bundle
Tokyowss://tyo.fastrelay.sh/v1/stream/txwss://tyo.fastrelay.sh/v1/stream/bundle

Note: Always use a region host (fra.fastrelay.sh, ams.fastrelay.sh, ny.fastrelay.sh, tyo.fastrelay.sh). The bare fastrelay.sh is the website and does not accept transactions.

Important: QUIC Protocol (Recommended) — works efficiently from any location worldwide. All stake-weighted endpoints are used simultaneously regardless of your region.

HTTP/HTTPS is best when co-located with the relay region. For cross-region, use QUIC.