Chainstack sets out new limits for heavy Solana reads
On 20 October, Chainstack described a rebuild of its Solana RPC. Chainstack puts getProgramAccounts p95 at 25 to 60 seconds before and under 2 seconds after. Every figure is Chainstack’s own claim.
On 20 October, Chainstack described a rebuild of its Solana RPC on X. The figures are in a blog post created on 12 October and updated on 15 October. They are Chainstack’s own claims.
Chainstack says heavy scan methods run in their own node pool. The pool covers getProgramAccounts, getTokenAccountsByOwner, getTokenAccountsByDelegate, and getSupply.
Chainstack sets the getSupply limit at 300 requests per second. The earlier limit was 2.
In its own rollout measurements, Chainstack puts getProgramAccounts p95 at 25 to 60 seconds before and under 2 seconds after. For getTokenAccountsByOwner, Chainstack cites a p95 of up to 2 minutes before and about 1 second after. Chainstack does not name a location for these p95 figures.
Chainstack says median getLatestBlockhash latency in Frankfurt was about 17 milliseconds before and about 2 milliseconds after. For that Frankfurt figure, Chainstack points to the public RPC dashboard at solana.com/data.
For programs under 10,000 accounts, Chainstack sets filtered getProgramAccounts at 20 requests per second. The earlier limit was 1 request per second. From 1 million accounts upward, Chainstack sets the limit at 3 requests per 20 seconds.
Chainstack writes that large programs are limited more tightly than before. The blog steps the limits by account count.
Chainstack says a scan stops after 60 seconds or at the memory limit and returns error -32012. The same error applies when a scan waits more than 15 seconds for a free slot.
Chainstack says the heavy reads run on Agave v4.3.0, with a preloaded account index. Chainstack moved part of its capacity in Frankfurt, New York, and Singapore onto new bare-metal servers.
A 16 October post dates Solana’s move to GEN 2.0 to late August 2026.
On the Frankfurt 1 shred-feed cluster, Chainstack cites a gap of 16.65 percent before. After the change it cites 5.36 percent.
What to watch
- When the new
getProgramAccountslimits took effect