Rate Limits
There's no one ceiling to memorize — each Blockspace product applies its own limit, and the exact number depends on the service and the tier you're on.
Per-service limits
ShredStream caps bandwidth and connections per tier, with no per-message rate limit; connection counts show up in the dashboard. Direct Shreds is bandwidth-bound only — it's a dedicated link to your IP, so there's no shared-tenant cap to hit. SWQOS applies per-region RPS caps on transaction submission that scale with plan tier, and bursts above the ceiling come back as 429 Too Many Requests. For Relayer/TPU, bundle and tx-submission rates are capped per searcher.
Plan-specific values are shown in the dashboard on the service page.
Burst behavior
A leaky-bucket limiter soaks up short bursts on rate-limited services. Push sustained traffic past the ceiling, though, and you'll trigger a 429 (HTTPS) or a flow-control signal (gRPC) — build exponential backoff into your retry logic.
Errors to watch for
| Status | Meaning | What to do |
|---|---|---|
401 | Missing/invalid token (or unrecognised source IP / signing pubkey on allowlist-based products) | Re-check credentials and transport per the product quickstart |
429 | RPS ceiling hit | Backoff + retry |
503 | Service temporarily unavailable | Backoff + retry; check the status page |