Limits (HTTP & WebSocket)
Rate limits are enforced per IP based on your subscription tier.
HTTP JSON-RPC
| Tier | RPS (reads) | TPS (transactions) |
|---|---|---|
| Build | 100 | 15 |
| Grow | 200 | 35 |
| Accelerate | 500 | 50 |
WebSocket
| Metric | Shared | Dedicated |
|---|---|---|
| Concurrent connections | 10 | Custom |
| Subscriptions per connection | 50 | Custom |
| Message rate | Fair use | Uncapped |
Exceeding Limits
- HTTP: returns
429 Too Many Requests. Back off and retry. - WebSocket: the server drops the oldest connection or subscription. Your client should detect the disconnect and reconnect.
If you are consistently hitting 429 responses, the options are to optimize your request patterns, for example caching or batching, or upgrade your tier. Details on all limits in one place: Limits & Fair Use.