Triton activates HTTP/3 and QUIC on Solana RPCs
Triton One has activated HTTP/3 and QUIC on all shared-infrastructure load balancers. Lower time-to-first-byte, better packet-loss resilience, separate streams — relevant for mobile wallets and dApp frontends.
What happened
Triton One has activated the HTTP/3 standard with QUIC transport on all shared-infrastructure load balancers. The change applies immediately for every customer on the shared RPC tier. Source: Triton original post on X.
What changes technically
HTTP/3 replaces TCP as the transport layer with QUIC, a UDP-based multiplexing protocol. Three direct effects:
- Lower time-to-first-byte after the initial handshake — roughly 50 percent less latency according to Triton’s measurements.
- Better packet-loss resilience: a single lost packet no longer blocks the entire stream (TCP head-of-line blocking is gone).
- Separate streams per request: parallel requests run independently and do not throttle each other.
The difference is most noticeable on unstable connections — mobile networks, public Wi-Fi, high-latency paths.
Who notices the difference
RPC clients that support HTTP/3 benefit without any code changes:
- Browser wallets (Phantom Web, Solflare Web, Backpack) — modern browsers speak HTTP/3 natively.
- Mobile dApps on Seeker, Saga, and standard phones via the Solana Mobile Stack.
- Server-side clients using HTTP/3-capable libraries (e.g. newer versions of Reqwest, undici, hyper).
Older HTTP/1.1 and HTTP/2 clients keep working — Triton falls back automatically.
Context
Triton is Solana’s second-largest independent RPC provider alongside Helius. Earlier this year, Triton introduced prepaid billing for RPC usage. The HTTP/3 activation continues the performance track: no price change, no API migration, only the underlying transport layer.
Not financial advice. This article describes technical infrastructure changes.