Vertex AI Gemini API customers experienced increased error rates when accessing the global endpoint.
Google Cloud · 最近保存的提供方状态：resolved
官方来源文字以原始语言显示。
最近保存的事件状态不是当前服务状态。来源列表可能不完整，事件从来源消失不确认恢复。请打开当前报告或官方来源查看较新证据。
已保存事件详情
- 提供方状态
- resolved
- 提供方影响程度
- SERVICE INFORMATION
- 提供方记录创建时间
- 27 Feb 2026, 16:12:30 UTC
- 提供方记录更新时间
- 09 Mar 2026, 05:25:43 UTC
- 提供方明确报告的开始时间
- 27 Feb 2026, 12:37:00 UTC
- 提供方明确报告的结束时间
- 27 Feb 2026, 14:35:00 UTC
提供方报告的受影响组件
- Dialogflow CX
BnCicQdHSdxaCv8Ya6Vm - Vertex Gemini API
Z0FZJAMvEB4j3NbCJs6B - Google Cloud Support
bGThzF7oEGP5jcuDdMuk - Agent Assist
eUntUKqUrHdbBLNcVVXq
这些关联描述此事件的报告范围。不能确认当前组件可用性或已核实依赖关系。
记录创建时间未必是故障开始时间。未报告的时间保持不可用。我们不根据采集时间计算故障时长。
Google Cloud 公开事件源，根据产品目录验证。不是 Personalized Service Health、特定项目健康、Gemini 应用状态或 Gemini API / AI Studio 状态。未报告事件不能独立确认服务可用性。事件更新保留提供方产品和地点信息，不推导地区探测结果。
已保存修订中的提供方更新
最新优先。最多显示最近 20 份已保存内容修订中的 100 条不同更新。同一提供方时间的文字修订单独保留。
- AVAILABLE
Reported products: Agent Assist, Dialogflow CX, Vertex Gemini API, Google Cloud Support. No affected locations listed in this update. # Incident Report ## Summary On Friday, 27 February 2026 at 04:37 US/Pacific, customers using Vertex AI Gemini API models experienced increased error rates. Impacted services included Google Cloud Support, Agent Assist, Vertex Gemini API and Dialogflow CX in US regions and the global endpoint. The issue persisted for a duration of 1 hour and 58 minutes. This is not the level of quality and reliability we strive to offer you, and we have taken immediate steps to improve the platform’s performance and availability. ## Root Cause This incident was caused by a configuration change to a safety filtering service that supports all Gemini models. For some specific requests, this created code paths that eventually led to service disruptions and capacity loss for the safety filtering service. Consequently, customers encountered overload (429 and 503) errors for their queries, with some users reporting elevated error rates for specific models in US regions. ## Remediation and Prevention Google engineers were alerted to the issue via our automated monitoring system on Friday, 27 February 2026 04:54 US/Pacific and immediately started an investigation. Engineers identified the faulty configuration change and initiated a rollback to restore the previous stable configuration. Engineers also added more capacity to the service to stabilize it. Full service restoration was confirmed by 06:35 US/Pacific as the rollback propagated and servers became healthy. \ \ Google is committed to preventing a repeat of this issue and is taking the following actions: * Reinforcing rollout processes to include mandatory validation checkpoints. * Improving alerting systems to monitor critical dependencies more closely. ## ## Detailed Description of Impact On Friday, 27 February 2026 between 04:37 and 06:35 US/Pacific, customers accessing Vertex Gemini APIs may have experienced the following: * **Affected Models:** All Vertex AI Gemini API models were affected, including gemini-2.5-flash, gemini-2.5-flash-lite, gemini-2.5-pro, gemini-3.0-flash-preview, gemini-3.0-pro-preview, gemini-2.0-flash, gemini-2.0-flash-lite. * **Error Experience:** * **PayGo Customers:** Experienced primarily 429 Resource Exhausted errors. * **Provisioned Throughput (PT) Customers:** Received 503 Service Unavailable errors. * For PT customers, most errors stopped at **06:00**. For PayGo customers, most errors stopped at **06:20**. * **Geographic Scope:** Global endpoint, us-central1, us-east4, and other US regions were impacted.
在 06 Oct 2026, 13:59:17 UTC 的已保存修订中观察到 - AVAILABLE
Reported products: Agent Assist, Dialogflow CX, Vertex Gemini API, Google Cloud Support. No affected locations listed in this update. # Preliminary Incident Report We apologize for the inconvenience this service disruption may have caused. We would like to provide some information about this incident below. Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. A final Incident Report with preventative actions will be posted once our investigation is complete. If you have experienced impact outside of what is listed below, please reach out to Google Cloud Support using https://cloud.google.com/support. ## Date/Time of the Issue (All time US/Pacific) Incident Start: 27 February 2026 04:37 Incident End: 27 February 2026 06:35 Duration: 1 hour, 58 minutes ## Summary On Friday, 27 February 2026 at 04:37 US/Pacific, customers using Vertex AI Gemini API models (including Gemini 2.0, 2.5, and 3.0 previews) experienced increased error rates. Impacted services included Google Cloud Support, Agent Assist, the Vertex Gemini API and Dialogflow CX in US regions and the global endpoint for a duration of 1 hour and 58 minutes. This is not the level of quality and reliability we strive to offer you, and we are taking immediate steps to improve the platform’s performance and availability. ## Preliminary Root Cause This incident was caused by a configuration change to a safety filtering service that supports all Gemini models. This configuration change enabled a code path that interacted poorly with specific requests, leading to service disruption for the safety filtering service. This in turn led to customers seeing overload (429 and 503) errors for their queries. Google engineers have begun a full root cause analysis and will provide additional information once it is available. ## Remediation Google engineers were alerted to the service disruption via automated alert on Friday, 27 February 2026 04:54 US/Pacific and immediately started an investigation. Engineers identified the faulty configuration change for a safety filtering service and initiated a rollback to restore the previous stable configuration. Additionally, engineers added more capacity to the service. Full service restoration was confirmed by 06:35 US/Pacific as the rollback propagated and servers became healthy. ## Description of Impact On Friday, 27 February 2026 between 04:37 and 06:35 US/Pacific, customers accessing Vertex Gemini APIs may have experienced the following: - Affected Models: All Gemini versions were affected, including gemini-2.5-flash, gemini-2.5-flash-lite, gemini-2.5-pro, gemini-3.0-flash-preview, gemini-3.0-pro-preview, gemini-2.0-flash, gemini-2.0-flash-lite. - Error Experience: - PayGo Customers: Experienced primarily 429 Resource Exhausted errors. - Provisioned Throughput (PT) Customers: Received 503 Service Unavailable errors. - For PT customers, most errors stopped at 06:00. For PayGo customers, most errors stopped at 06:20. - Geographic Scope: Global endpoint, us-central1, us-east4, and other US regions were impacted.
在 06 Oct 2026, 13:59:17 UTC 的已保存修订中观察到 - SERVICE INFORMATION
Reported products: Agent Assist, Dialogflow CX, Vertex Gemini API, Google Cloud Support. Reported locations: Montréal (northamerica-northeast1) (northamerica-northeast1), São Paulo (southamerica-east1) (southamerica-east1), Iowa (us-central1) (us-central1), South Carolina (us-east1) (us-east1), Northern Virginia (us-east4) (us-east4), Columbus (us-east5) (us-east5), Oregon (us-west1) (us-west1). **Description** \ Between Friday, 2026-02-27, 04:36 and 06:45 PST, customers experienced increased error rates when accessing the Vertex Gemini API Global endpoint. The issue impacted API requests to multiple Gemini models. The incident also caused downstream impact to Dialogflow CX, Agent Assist, Google Cloud Support AI agent, and Customer Experience Agent Studio, which rely on Gemini APIs. Preliminary analysis indicates the issue was triggered by a recent configuration change. Service was fully restored after the configuration change was rolled back. We thank you for your patience while we worked on resolving the issue. **Symptom** \ Customers experienced increased error rates when sending API requests to impacted multiple Gemini models through the global endpoint.
在 06 Oct 2026, 13:59:17 UTC 的已保存修订中观察到