Service Health
Incident affecting Vertex Gemini API
Vertex Gemini API experiencing issue globally
Incident began at 2024-12-13 01:07 and ended at 2024-12-13 11:01 (all times are US/Pacific).
Previously affected location(s)
Singapore (asia-southeast1)Iowa (us-central1)South Carolina (us-east1)Las Vegas (us-west4)
Date | Time | Description | |
---|---|---|---|
| 13 Dec 2024 | 11:01 PST | The issue with Vertex Gemini API has been resolved for all affected users as of Friday, 2024-12-13 09:00 US/Pacific. We thank you for your patience while we worked on resolving the issue. |
| 13 Dec 2024 | 08:05 PST | Summary: Vertex Gemini API experiencing issue globally Description: We are experiencing an issue with Vertex Gemini API beginning at Thursday, 2024-12-12 21:53 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2024-12-13 12:15 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Vertex Gemini API users may observe error 500 messages when they send requests to tuned endpoints. Workaround: None at this time. |
| 13 Dec 2024 | 04:26 PST | Summary: Vertex Gemini API experiencing issue globally Description: We are experiencing an issue with Vertex Gemini API beginning at Thursday, 2024-12-12 21:53 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2024-12-13 12:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Vertex Gemini API users may observe error 500 messages when they send requests to tuned endpoints. Workaround: None at this time. |
- All times are US/Pacific