API Gateway runtime architecture update
Google Cloud's API Gateway is updating its runtime architecture to enhance integration with GCP services. While core features remain unaffected, status code mappings for gRPC APIs have changed, and 4xx client-side quota failures will now result in rejected requests. This update applies to all API Gateway users and is rolling out over four weeks.
Enhancements (1) ›
- API Gateway Update to the API Gateway runtime architecture
Update to the API Gateway runtime architecture The API Gateway runtime architecture is being updated to improve its integration with Google Cloud Platform and its services. This update does not affect existing API Gateway features. However, be aware of the following differences: Status code changes for gRPC API Gateways Error New status code Previous status code Quota exceeded ResourceExhausted Unavailable Invalid API key InvalidArgument InternalError For 4xx client-side quota failures, API Gateway will now reject requests (fail closed). This applies to both gRPC and OpenAPI API Gateways. If y
https://docs.cloud.google.com/release-notes#June_18_2026
Related releases
- Cloud Load Balancing: Global External Passthrough Network Load Balancer Preview Google Cloud release notes ·
- Google Cloud Managed Service for Apache Kafka: Synthetic Data Generation Google Cloud release notes ·
- Dataflow batch jobs can now be paused on failure Google Cloud release notes ·
- Config Connector 1.154.1 Adds New Alpha Resources and Field Support Google Cloud release notes ·
- Security Command Center: Data Residency & Agent Vulnerability Scanning Preview Google Cloud release notes ·
- Cloud SQL for PostgreSQL: Private Service Connect changes August 2026 Google Cloud release notes ·