Google Cloud release notes

The following release notes cover the most recent changes over the last 60 days. For a comprehensive list of product-specific release notes, see the individual product release note pages.

You can also see and filter all release notes in the Google Cloud console or you can programmatically access release notes in BigQuery.

To get the latest product updates delivered to you, add the URL of this page to your feed reader, or add the feed URL directly.

September 18, 2026

Cloud Load Balancing
Feature

Managed workload identity for backend mTLS is generally available for the following Application Load Balancers:

  • Global external Application Load Balancers
  • Regional external Application Load Balancers
  • Cross-region internal Application Load Balancers
  • Regional internal Application Load Balancers

The key benefits are as follows:

  • Streamline certificate management: Automated certificate and trust management for backend mTLS through seamless integration with Certificate Authority Service and Certificate Manager.

  • Eliminate operational toil: Certificates are automatically rotated based on the workload identity pool's configuration, removing the complexity and manual bottleneck of private key provisioning and maintenance.

  • Improve visibility and governance: Gain visibility into communication between distributed services and proactively apply governance to workloads across environments.

For more information, see Backend mTLS with managed workload identity overview

Cloud Scheduler
Change

Cloud Scheduler is available in the following location:

  • asia-southeast3 (Bangkok, Thailand)
Gemini Enterprise Agent Platform
Feature

xAI's Grok 4.6 is generally available

Grok 4.6 is now generally available (GA) and available for production use on the global endpoint and the US multi-region endpoint.

Google Cloud Contact Center as a Service
Fixed

This release addresses the following issues:

  • Fixed an issue where session metadata and data feed files were missing from external storage for chats that ended before the first message from the end-user.

  • Fixed an issue with Kustomer integrations where the caller's information didn't appear on the Incoming call page of the call adapter for direct-line inbound calls.

  • Fixed an issue with inbound mobile calls where the end-user leg of the call failed, returning Unknown error, while the agent leg connected normally.

  • Fixed an agent desktop issue where live call and chat data were lost.

  • Fixed an issue that occurred when the receiving agent in an agent-to-agent transfer didn't answer the call. The receiving agent was marked as active on the call indefinitely, even after the call ended.

  • Fixed an issue where the Dismiss button remained active after an agent sent a message, resulting in a 409 error when clicked.

  • Fixed an issue where duplicate "chat finished" events were reported when the end-user left a chat session at nearly the same time that the agent ended the chat session.

  • Fixed an issue where deflected calls were missing from the All Call History and Voice Inbound (IVR) History reports.

  • Fixed an issue that occurred when a direct inbound call was deflected to the agent's overcapacity queue, then that queue redirected to a SIP URI. The SIP redirect didn't include the custom SIP headers.

  • Fixed an issue where an in-queue announcement interval of several minutes for inbound IVR calls was incorrectly reduced to approximately 60 seconds.

  • Fixed an issue where calls that agents were unable to answer due to microphone failures were incorrectly reported as "picked up" in the Agent Activity Timeline report.

  • Fixed an issue where the system incorrectly marked agents as still being on a call after it ended, which either prevented them from changing their status to Available or silently blocked them from receiving new calls.

  • Fixed an issue where processing delays for ended calls caused timeout errors.

  • Fixed an issue where a sudden spike in calls bypassed capacity limits, causing agent availability to drop below required minimums.

  • Fixed an issue where the Agent Activity Timeline report incorrectly attributed manual agent logins and logouts to System instead of the appropriate agents.

  • Fixed an issue where calls with a missed offer became permanently stuck in the queue, preventing them from being routed to other available agents. This occurred with queues configured with multicast fallback disabled.

  • Fixed an issue where manual or cascade outbound calls that were canceled before connecting were missing from team-filtered Call History reports.

  • Fixed an issue that prevented over-capacity deflection from triggering when an agent warm-transferred an outbound call to a queue.

  • Fixed an issue where calls weren't correctly routed to the top-ranked agent when using agent priority overrides.

  • Fixed an issue where escalated voice calls were incorrectly reported as both answered and abandoned.

  • Fixed an issue where calls were missing from the All Call History and Voice Inbound History reports if the caller hung up before leaving a voicemail.

  • Fixed an issue where Salesforce click-to-dial outbound calls were incorrectly associated with the most recent open case instead of the case from which the call was initiated.

  • Fixed an issue where email accounts remained disconnected indefinitely after a temporary authentication failure.

  • Fixed an issue in Agent Assist where long periods of silence during calls caused connection timeouts, triggering false-positive error alerts.

  • Fixed an issue where the arrow-down-icon and arrow-up-icon arrows on the Agents > Filter Settings page were rendered at an incorrect scale.

  • Fixed an issue where incoming calls incorrectly created duplicate Salesforce accounts instead of linking to existing accounts.

  • Fixed an issue where the outbound call queue list displayed stale information, potentially causing calls to be placed in a queue that didn't match the agent's selected language.

  • Fixed an issue where the menus for transferring calls and forwarding calls to voicemail appeared in English instead of the agent's selected language.

  • Fixed an issue where the wrap-up disposition panel froze after a network reconnection even though the submission had completed successfully.

  • Fixed an issue where outbound, click-to-dial calls initiated in Salesforce incorrectly linked to and reassigned ownership of other cases associated with the same phone number.

  • Fixed an issue where the agent adapter went blank and prevented new calls from reaching the agent if an end-user hung up immediately after the agent received the call notification.

  • Fixed an issue where calls that failed to connect got stuck in a silent 'connecting' state in the call adapter.

  • Fixed an issue where Salesforce CRM connections dropped for organizations enforcing OAuth Refresh Token Rotation.

  • Fixed an issue where part of an agent's audio was dropped from recordings when a virtual task assistant ran in the middle of a call.

  • Fixed a web SDK issue where menus in the pre-chat and chat screens didn't comply with WAI-ARIA keyboard navigation standards.

  • Fixed a web SDK issue where screen readers couldn't identify the purpose of the Text size options for the chat screen.

Model Armor
Feature

Filter version v4 is available and set as the default for the Latest alias. Filter version v3 is promoted to the Stable alias in all supported regions except the following:

  • In asia-northeast3, v1 remains the Stable version.
  • In australia-southeast2, v3 becomes the Stable version on September 25, 2026.

If your templates use the Stable alias, they automatically upgrade to v3 when v3 becomes Stable in that region.

Filter versions v1 (except in asia-northeast3, and starting September 25, 2026 in australia-southeast2) and v2 transition to Legacy status and retire on December 17, 2026. If your templates are explicitly configured with v1 or v2 in regions where those versions are in Legacy status, you must migrate them to v3 or the Stable alias before December 17, 2026.

For more information, see Version release timeline and Model Armor filter version history.

September 17, 2026

Apigee hybrid
Announcement

v1.16.10

On September 17, 2026 we released an updated version of the Apigee hybrid software, v1.16.10.

Fixed

Fixed in this release

Bug ID Description
556750755 Fixed an issue where EventFlow (Server-Sent Events) dropped or truncated events following a large (>16 KB) event under load on the http-adaptor datapath.
547712217 Fixed an issue where EventFlow (Server-Sent Events) responses larger than 16 KB could be truncated or corrupted across socket reads.
519729209 Fixed a SAML XML Signature Wrapping (XSW) vulnerability in the ValidateSAMLAssertion policy.
514384893 Hardened the Script policy to block server-side request forgery (SSRF) to link-local addresses.
505645076 Fixed a security issue in the OAuthV2 policy to prevent unauthorized token injection via HTTP form parameters.
505543289 Fixed thread-safety issues in the Netty client connection pool and channel lifecycle.
503817773 Improved security in the OAuthV2 policy implicit grant redirect_uri validation.
502268966 Apigee hybrid now supports optional decoding of percent-encoded path separators (%2F and %5C) before flow selection via the request.path.decode.encoded.separators proxy property.
480770263 Fixed an issue in the SpikeArrest policy to handle edge cases that previously caused NullPointerException and 500 errors.
472526232 Improved SAML assertion validation in the ValidateSAMLAssertion policy against entity and comment injection.
470375542 Fixed a memory leak in WSFrameDecoder that could result in a spike in 503 responses with no_healthy_upstream errors.
449228485 Apigee hybrid now supports configuring custom Kubernetes PodDisruptionBudget (minAvailable or maxUnavailable) values for Apigee hybrid components in your overrides.yaml file.