CompaniesGoogle WorkspaceIncidents
Google Workspace: **Summary** Investigating elevated error rates with Gemini conversations. **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 Tuesday, 2026-05-05 20:30 PDT. **Symptoms** Affected customers are experiencing "Something went wrong(13)" error message in their Gemini conversations. **Workaround** None at this time.
Affected components: Gemini
Timeline of updates
- service information
Summary
Investigating elevated error rates with Gemini conversations.
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 Tuesday, 2026-05-05 20:30 PDT.
Symptoms
Affected customers are experiencing "Something went wrong(13)" error message in their Gemini conversations.
Workaround
None at this time. - service information
Summary
Investigating elevated error rates with Gemini conversations.
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 Wednesday, 2026-05-06 09:00 PDT.
Symptoms
Affected customers are experiencing "Something went wrong(13)" error message in their Gemini conversations.
Workaround
None at this time. - service information
Summary
Gemini conversations are experiencing elevated error rates.
Description
Our engineering team has determined that further investigation is required to mitigate the issue.
We do not have an ETA for mitigation at this point.
We will provide more information by Thursday, 2026-05-07 17:00 PDT.
Symptoms
Affected customers are experiencing "Something went wrong(13)" error message in their Gemini conversations.
Workaround
None at this time. - service information
Summary
Gemini conversations are experiencing elevated error rates.
Description
Our engineering team has determined that further investigation is required to mitigate the issue.
We do not have an ETA for mitigation at this point.
We will provide more information by Thursday, 2026-05-07 20:30 PDT.
Symptoms
Affected customers are experiencing "Something went wrong(13)" error message in their Gemini conversations.
Workaround
None at this time. - service information
Summary
Gemini conversations may have experienced elevated error rates.
Description
The issue with Gemini has been resolved for all affected users as of Thursday, 2026-05-07 17:00 PDT.
The issue was triggered due to a combination of insufficient database resources, and application issues. The database capacity issues were resolved, and further code changes are being made to mitigate the application issues.
We thank you for your patience while we worked on resolving the issue.
Symptoms
Affected customers may have experienced the "Something went wrong(13)" error message in their Gemini conversations. - service information
Summary
Gemini conversations are experiencing elevated error rates.
Description
Our engineering team has determined that further investigation is required to mitigate the issue.
We do not have an ETA for mitigation at this point.
We will provide more information by Friday, 2026-05-08 01:00 PDT.
Symptoms
Affected customers may encounter "Something went wrong(13)" error message in their Gemini conversations.
Workaround
None at this time. - service information
Summary
Gemini conversations may experience elevated error rates.
Description
Our engineering team has isolated the underlying issue and is in the process of reverting the specific code deployments that triggered the impact.
We are actively monitoring the progress of the rollback, alongside system health indicators, to confirm that the restoration is proceeding effectively.
We will provide more information by Friday, 2026-05-08 04:00 PDT.
Symptoms
Affected customers may encounter "Something went wrong(13)" error message in their Gemini conversations.
Workaround
None at this time. - service information
Summary
Gemini conversations may experience elevated error rates.
Description
Our engineering team has isolated the underlying issue and is in the process of reverting the specific code deployments that triggered the impact.
We are actively monitoring the progress of the rollback, alongside system health indicators, to confirm that the restoration is proceeding effectively.
We will provide more information by Friday, 2026-05-08 09:00 PDT.
Symptoms
Affected customers may encounter "Something went wrong(13)" error message in their Gemini conversations.
Workaround
None at this time. - service information
Summary
Gemini conversations may experience elevated error rates.
Description
Our engineering team has isolated the underlying issue and is in the process of reverting the specific code deployments that triggered the impact.
We are actively monitoring the progress of the rollback, alongside system health indicators, to confirm that the restoration is proceeding effectively.
We will provide more information by Friday, 2026-05-08 12:00 PDT.
Symptoms
Affected customers may encounter "Something went wrong(13)" error message in their Gemini conversations.
Workaround
None at this time. - resolved
Summary
Gemini conversations may have experienced elevated error rates.
Description
The issue with Gemini has been resolved for all affected users as of Friday, 2026-05-08 11:53 PDT.
The issue was triggered due to a combination of insufficient database resources, and application bugs. The database capacity issues were resolved, and further code changes are being made to mitigate the application issue.
We thank you for your patience while we worked on resolving the issue.
Symptoms
Affected customers may have experienced "Something went wrong(13)" error message in their Gemini conversations.
Workaround
None at this time.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-19 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
5f029c4975e089e2…
Impact, status and times are the vendor’s own, as last archived. View on www.google.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Google Workspace, started 2026-05-04 16:40 UTC, resolved after 4 d, 10 update(s).
- Title
- **Summary** Investigating elevated error rates with Gemini conversations. **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 Tuesday, 2026-05-05 20:30 PDT. **Symptoms** Affected customers are experiencing "Something went wrong(13)" error message in their Gemini conversations. **Workaround** None at this time.
- Vendor
- Google Workspace
- Date
- URL
- https://rewindex.com/company/google-workspace/incidents/1hr418kjgybz9ugxy3w3
Google Workspace profileRecent Google Workspace incidentsAll outages on May 4, 2026Google Workspace in May 2026MarkdownJSON