Quick answer
Google Cloud Run documents maximum requests per instance as 1,000 concurrent requests. The console default is lower, and the application must safely support parallel requests.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| maximum requests per instanceThe console default is lower, and the application must safely support parallel requests. | 1,000 concurrent requests | Cloud Run services | Google CloudAug 22, 2026 |
Why does this limit matter?
High concurrency can reduce instance count but increase memory, CPU, connection, and latency contention.
This value is scoped to Cloud Run services; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Read the deployed revision's concurrency value and load-test application-level parallel safety.
- 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
- The configured value is a maximum; Cloud Run can route fewer requests when an instance is highly utilized.
- 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