Limits & Fair Use
All HighTower endpoints enforce rate limits at the IP level. The specific caps depend on your subscription tier and the interface you are using.
HTTP JSON-RPC
| Tier | RPS (read requests) | TPS (sendTransaction) |
|---|---|---|
| Build | 100 | 15 |
| Grow | 200 | 35 |
| Accelerate | 500 | 50 |
WebSocket
| Metric | Shared Tiers | Dedicated |
|---|---|---|
| Concurrent connections | 10 | Custom |
| Subscriptions per connection | 50 | Custom |
| Message rate | Fair use | Uncapped* |
Yellowstone gRPC
| Tier | Connections | Message rate |
|---|---|---|
| Build | 5 | Fair use |
| Grow | 15 | Fair use |
| Accelerate | 50 | High priority |
| Dedicated | Custom | Uncapped* |
*Hardware limits apply.
In pricing and support communication, we refer to these stream caps as connections. Technically, they map to your active concurrent gRPC streams.
Individual gRPC messages are capped at 4 MB. Use account or program filters to keep responses within this size.
What Happens When You Hit a Limit
- HTTP/gRPC: the server returns 429 Too Many Requests. Back off exponentially before retrying.
- WebSocket: the oldest connection or subscription is dropped. Your client should detect the disconnect and reconnect with backoff.
- Sustained abuse: if traffic patterns consistently overload shared infrastructure, our team will reach out via Discord to discuss options such as a tier upgrade or dedicated hardware.
Fair Use
There are no hidden quotas beyond the numbers listed above. "Fair use" on gRPC and WebSocket message rate means we do not enforce a fixed cap per second, but we do monitor aggregate bandwidth. If a single client's traffic visibly degrades service for others on the same shared node, we will throttle that client and open a conversation about moving to a higher tier or a dedicated deployment.