Rate Limits
Rate limits control the maximum number of requests per second (RPS) that can be made to Syndica's Solana RPC API. Limits vary by plan tier and method.
HTTP RPC Rate Limits
The following limits represent the maximum RPS for each method on Standard and Scale plans:
| Method | Standard Mode | Scale Mode |
|---|---|---|
| getBlock | 25 | 100 |
| getBlockTime | 40 | 120 |
| getBlocks | 35 | 100 |
| getLargestAccounts | 0 | 0 |
| getMultipleAccounts | 25 | 75 |
| getProgramAccounts | 0 | 5 |
| getSignaturesForAddress | 50 | 150 |
| getTokenAccountsByOwner | 35 | 200 |
| getTransaction | 20 | 60 |
| sendTransaction | 20 | 60 |
| Unspecified methods (not listed) | 100 | 300 |
Rates may vary based on network conditions, server load, and other factors.
WebSocket Limits
Connections are the open sockets between your client and our server.
Subscriptions are event listeners (e.g. accountSubscribe, logsSubscribe) created over those connections.
- One connection can host many subscriptions
- Reuse connections and clean up unused subscriptions to stay within limits
Max Active WebSocket Connections
| Standard Mode | Scale Mode |
|---|---|
| 100 | 300 |
Max Total Active WebSocket Subscriptions
The total number of active subscriptions across all connections and namespaces.
| Standard Mode | Scale Mode |
|---|---|
| 100 | 600 |
Max Subscriptions per WebSocket Connection
| Standard Mode | Scale Mode |
|---|---|
| 100 | 600 |
WebSocket Method Limits
Mainnet
| Method | Standard Mode | Scale Mode |
|---|---|---|
| accountSubscribe | 30 | 600 |
| blockSubscribe | 30 | 90 |
| logsSubscribe | 10 | 100 |
| programSubscribe | 10 | 100 |
| signatureSubscribe | 100 | 600 |
| slotSubscribe | 30 | 600 |
| slotsUpdatesSubscribe | 10 | 600 |
| voteSubscribe | 30 | 90 |
| Unspecified methods (not listed) | 100 | 600 |
Devnet
| Method | Standard Mode | Scale Mode |
|---|---|---|
| accountSubscribe | 30 | 300 |
| blockSubscribe | 30 | 90 |
| logsSubscribe | 10 | 30 |
| programSubscribe | 10 | 30 |
| signatureSubscribe | 100 | 300 |
| slotSubscribe | 30 | 300 |
| slotsUpdatesSubscribe | 10 | 300 |
| voteSubscribe | 30 | 90 |
| Unspecified methods (not listed) | 100 | 300 |
Custom Rate Limits
You can set custom rate limits per API key to control access more precisely. Learn more in the Custom Rate Limits guide, which covers:
- Protecting front-end RPC endpoints from abuse
- Managing rate limits across multiple projects
- Setting credential-wide and method-specific limits
- Configuring per-IP rate limits
- Advanced patterns and use cases
FAQ and Troubleshooting
How do I know if I'm hitting rate limits?
Rate limit responses return HTTP 429 status codes. You can monitor your usage in the RPC Analytics dashboard. See Observability to learn how to inspect logs and metrics when diagnosing throttling, review Rate Limits and plans/pricing for plan-specific limits, or configure custom rate limits per API key.
What You Can Do Next
- Create an API Key - Set up credentials with custom rate limits
- View Account Limits - Check your current plan limits
- Error Handling - Handle rate limit errors (429) in your application
- Upgrade Your Plan - Increase your rate limits