Quick answer
Google Cloud Run documents maximum instance memory as 32 GiB. The writable in-memory filesystem also consumes instance memory.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| maximum instance memoryThe writable in-memory filesystem also consumes instance memory. | 32 GiB | Per container instance | Google CloudAug 22, 2026 |
Why does this limit matter?
Files written to the in-memory filesystem reduce the memory available to the application process.
This value is scoped to Per container instance; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Inspect revision memory, tmpfs use, heap telemetry, and regional quota together.
- 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
- Regional aggregate memory quota can prevent scaling to the per-instance maximum across many instances.
- 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