Quick answer
Firebase documents hosting request timeout as 60 seconds. The Hosting request can time out before a longer Cloud Run backend maximum.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| Hosting request timeoutThe Hosting request can time out before a longer Cloud Run backend maximum. | 60 seconds | Hosting rewrites to serverless | FirebaseAug 22, 2026 |
Why does this limit matter?
A backend that supports minutes of work is still unsuitable for a synchronous Hosting path capped at 60 seconds.
This value is scoped to Hosting rewrites to serverless; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Trace the public route through Hosting and measure response time at that boundary.
- 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
- Direct Cloud Run access and Firebase Hosting have different front-door constraints.
- 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