# Summary - Provider: [Google Workspace](https://down.guide/google-workspace) - Level: confirmed - Impact: Degraded - lasted 4d 2h - started 2026-05-04 16:40 UTC - Gemini - id: DWN-fc509bfbac - Official page: https://www.google.com/appsstatus/dashboard/incidents/1hr418kjGyBZ9ugXy3W3 ## Updates from Google Workspace ### 2026-05-05 23:35 UTC: 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. ### 2026-05-06 03:22 UTC: 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. ### 2026-05-06 19:11 UTC: 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. ### 2026-05-07 23:52 UTC: 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. ### 2026-05-08 01:00 UTC: 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. ### 2026-05-08 05:16 UTC: 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. ### 2026-05-08 07:29 UTC: 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. ### 2026-05-08 10:23 UTC: 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. ### 2026-05-08 15:53 UTC: 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. ### 2026-05-08 18:58 UTC: 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. From the builder: does your app depend on Google Workspace? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=google-workspace) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Google Workspace. --- down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-fc509bfbac), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.