Quick answer
Stripe documents global operations per second as Live: 100 ops/s; sandbox: 25 ops/s. Stripe also applies endpoint and concurrency limiters.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| global operations per secondStripe also applies endpoint and concurrency limiters. | Live: 100 ops/s; sandbox: 25 ops/s | Basic global limit | StripeAug 22, 2026 |
Why does this limit matter?
A distributed worker fleet shares account-level capacity and can exceed the global limiter collectively.
This value is scoped to Basic global limit; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Aggregate requests across services and inspect Stripe-Rate-Limited-Reason on 429 responses.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Meter events and some Connect operations use separate limits.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related