ST-2026-141 · Runtimes & execution environments
Google API Gateway changes quota and authentication status codes during runtime rollout
Google API Gateway began a runtime-architecture rollout that changes two gRPC error mappings and makes selected 4xx quota failures fail closed across gRPC and OpenAPI gateways.
Previous state
gRPC gateways mapped quota exhaustion to Unavailable and invalid API keys to InternalError, while selected client-side quota failures did not use the new fail-closed behaviour.
Current state
Quota exhaustion maps to ResourceExhausted, invalid API keys map to InvalidArgument and selected 4xx quota failures are rejected fail closed.
Affected users
Who needs to care
Clients, retry middleware and observability rules that classify API Gateway errors by status code.
Required response
What to do
Update retry and alerting logic, test both gateway types and account for a rollout that can vary by zone for up to four weeks.
Evidence boundary
What the source does not prove
The release does not remove existing API Gateway features and does not state one universal per-instance activation date.
Lifecycle history
Dated event sequence
- Runtime rollout announced
Google began the architecture update and documented the new error mappings and fail-closed behaviour.
- Maximum stated rollout window
Production rollout could take up to four weeks across all Google Cloud zones; this is not a guaranteed per-instance cutover date.
Evidence ledger
First-party sources
- 01Google Cloud — API Gateway release notes
Official runtime release note · 2026-06-18
Open official source ↗