Service Health
Incident affecting Vertex Gemini API
Issue with Vertex Gemini API
Incident began at 2024-11-08 17:49 and ended at 2024-11-08 22:33 (all times are US/Pacific).
Previously affected location(s)
Taiwan (asia-east1)Hong Kong (asia-east2)Tokyo (asia-northeast1)Seoul (asia-northeast3)Mumbai (asia-south1)Singapore (asia-southeast1)Oregon (us-west1)
Date | Time | Description | |
---|---|---|---|
| 8 Nov 2024 | 22:33 PST | The issue with Vertex Gemini API has been resolved for all affected users as of Friday, 2024-11-08 22:32 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
| 8 Nov 2024 | 21:48 PST | Summary: Issue with Vertex Gemini API Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Saturday, 2024-11-09 01:00 US/Pacific. Diagnosis: Customers impacted by this issue may see HTTP 500 errors for requests in the affected regions. Workaround: None at this time. |
| 8 Nov 2024 | 20:17 PST | Summary: Issue with Vertex Gemini API Description: We are experiencing an issue with Vertex Gemini API. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2024-11-08 22:00 US/Pacific with current details. Diagnosis: Customers impacted by this issue may see HTTP 500 errors for requests in the affected regions. Workaround: None at this time. |
- All times are US/Pacific