Quick answer
Clerk documents backend request allowance as Production: 1,000 requests/10s; development: 100/10s. Endpoint-specific and frontend limits can apply in addition to the backend allowance.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| backend request allowanceEndpoint-specific and frontend limits can apply in addition to the backend allowance. | Production: 1,000 requests/10s; development: 100/10s | Per Clerk instance | ClerkAug 22, 2026 |
Why does this limit matter?
A development instance can throttle at one tenth the documented production request allowance.
This value is scoped to Per Clerk instance; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Confirm instance type and aggregate backend calls across every server worker.
- 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
- Bulk operations and invitations have separate longer-window 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