Writing¶
Longer pieces that do not fit the reference documentation — how Solana RPC actually fails, and what is worth tuning.
The Solana RPC failure modes no status page shows you¶
Three of the four failures that take an application down return HTTP 200: a provider serving data from behind the chain tip, a write path that accepts transactions it never lands, and a partial rollout that fails one request in three. What each looks like from the client, and the health signals that catch them.
HTTP/3 for Solana RPC — and why it probably isn't your bottleneck¶
Every Solana SDK speaks HTTP/1.1, and a proxy can speak QUIC upstream without changing a line of client code. Measured from a residential connection to a Singapore edge: one full round trip saved per connection setup — a third off a cold request — against about 2 ms on a warm pooled one. Why that still means "leave it off" for a colocated sidecar, and the fallback behaviour that will silently take a provider out of your fleet if you enable it blind.
Working on cost rather than reliability? The by-workload pages compute what a trading bot, an indexer and a wallet backend each cost across seven providers, and compare has the head-to-head crossovers.