Skip to main content

Billing and Rate Limits

getProgramAccounts is a resource-intensive method that have an additional rate limiting beyond standard requests per second. Consider filtering parameters, or breaking large queries into smaller chunks to stay within limits.
Helius automatically routes requests to the optimal region for performance. For specialized regional requirements or dedicated infrastructure, contact our sales team to discuss enterprise options.

Troubleshooting RPCs

Call the Priority Fee API, optimize compute-unit usage, and send the transaction with skipPreflight: true. See our Transaction Optimization Guide for a step-by-step walkthrough.
Check our status page for relevant updates. If there’s no related incident, contact support.

Using RPCs

Use getLatestBlockhash with "confirmed" commitment level for the most recent blockhash. Always fetch a fresh blockhash before submitting transactions to ensure validity. See our getLatestBlockhash guide for details.
Staked connections route your transactions directly to current and upcoming block leaders, bypassing public queues for near-guaranteed delivery. All paid plans automatically use staked connections by default - no code changes required. Learn more in our transaction sending overview.
Standard RPC plans provide access to all historical Solana data. Dedicated nodes only maintain ~48 hours of history.
Use Helius Sender. It simultaneously routes your transactions through Helius’s staked connections and to Jito Block Engines for maximum speed and landing probability.
All RPC requests sent through standard RPC URLs on shared plans are automatically routed to the closest server. There is no action required from you.
We operate RPC nodes globally including: Asia (Tokyo, Singapore), North America (Pittsburgh, Newark, Salt Lake City, Los Angeles, Vancouver), and Europe (Dublin, London, Amsterdam, Frankfurt).
Your RPC rate limits apply to all RPC methods in total, not to each one separately. For example, if your RPC rate limit is 100 and you’re making 50 getAccountInfo requests per second, you can only make 50 getTransaction requests in addition.
Some methods like getProgramAccounts have special rate limits due to their computational requirements. However, they still count towards the total RPC rate limit. For details, read our guide on special rate limits.
RPC rate limits and DAS rate limits are independent of each other. For example, if your plan has a RPC rate limit of 50 and a DAS rate limit of 10, this allows you to make 50 getBlock and 10 getAsset calls per second.

Need More Help?