{"meta":{"version":"v1","pricing":{"public":{"label":"Public","description":"Read-only API access for lightweight status checks and public integrations."},"premium":{"label":"Premium (early access)","description":"API keys with higher hourly quotas are available now; webhooks, alerting, and exports are on the roadmap."}},"generatedAt":"2026-07-09T05:22:34.819Z"},"data":{"id":"incident_gws_1hr418kjGyBZ9ugXy3W3","slug":"google-workspace-summary-investigating-elevated-error-rates-with-gemini-conversations-2026-05-04-9ugxy3w3","title":"**Summary** Investigating elevated error rates with Gemini conversations. **Description** Mitigation work is currently…","summary":"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.","status":"resolved","severity":"minor","startedAt":"2026-05-04T16:40:00+00:00","updatedAt":"2026-05-08T18:58:23+00:00","resolvedAt":"2026-05-08T18:53:00+00:00","provider":{"slug":"google-workspace","name":"Google Workspace"},"affectedServices":[],"links":{"html":"/incidents/google-workspace-summary-investigating-elevated-error-rates-with-gemini-conversations-2026-05-04-9ugxy3w3","api":"/api/v1/incidents/google-workspace-summary-investigating-elevated-error-rates-with-gemini-conversations-2026-05-04-9ugxy3w3","providerHtml":"/providers/google-workspace"},"impactSummary":"Google Workspace reported a low severity event affecting Gemini.","source":{"id":"source_google_workspace_status","kind":"official_api","name":"Google Workspace Status Dashboard","checkedAt":"2026-07-09T05:20:24.118+00:00","officialUrl":"https://www.google.com/appsstatus/dashboard","statusPageUrl":"https://www.google.com/appsstatus/dashboard"},"updates":[{"id":"update_gws_1hr418kjGyBZ9ugXy3W3_20260505t2335490000","status":"investigating","body":"**Summary**\nInvestigating elevated error rates with Gemini conversations.\n**Description**\nMitigation work is currently underway by our engineering team.\nWe do not have an ETA for mitigation at this point.\nWe will provide more information by Tuesday, 2026-05-05 20:30 PDT.\n**Symptoms**\nAffected customers are experiencing \"Something went wrong(13)\" error message in their Gemini conversations.\n**Workaround**\nNone at this time.","createdAt":"2026-05-05T23:35:49+00:00"},{"id":"update_gws_1hr418kjGyBZ9ugXy3W3_20260506t0322400000","status":"monitoring","body":"**Summary**\nInvestigating elevated error rates with Gemini conversations.\n**Description**\nMitigation work is currently underway by our engineering team.\nWe do not have an ETA for mitigation at this point.\nWe will provide more information by Wednesday, 2026-05-06 09:00 PDT.\n**Symptoms**\nAffected customers are experiencing \"Something went wrong(13)\" error message in their Gemini conversations.\n**Workaround**\nNone at this time.","createdAt":"2026-05-06T03:22:40+00:00"},{"id":"update_gws_1hr418kjGyBZ9ugXy3W3_20260506t1911020000","status":"monitoring","body":"**Summary**\nGemini conversations are experiencing elevated error rates.\n**Description**\nOur engineering team has determined that further investigation is required to mitigate the issue.\nWe do not have an ETA for mitigation at this point.\nWe will provide more information by Thursday, 2026-05-07 17:00 PDT.\n**Symptoms**\nAffected customers are experiencing \"Something went wrong(13)\" error message in their Gemini conversations.\n**Workaround**\nNone at this time.","createdAt":"2026-05-06T19:11:02+00:00"},{"id":"update_gws_1hr418kjGyBZ9ugXy3W3_20260507t2352490000","status":"monitoring","body":"**Summary**\nGemini conversations are experiencing elevated error rates.\n**Description**\nOur engineering team has determined that further investigation is required to mitigate the issue.\nWe do not have an ETA for mitigation at this point.\nWe will provide more information by Thursday, 2026-05-07 20:30 PDT.\n**Symptoms**\nAffected customers are experiencing \"Something went wrong(13)\" error message in their Gemini conversations.\n**Workaround**\nNone at this time.","createdAt":"2026-05-07T23:52:49+00:00"},{"id":"update_gws_1hr418kjGyBZ9ugXy3W3_20260508t0100010000","status":"monitoring","body":"**Summary**\nGemini conversations may have experienced elevated error rates.\n**Description**\nThe issue with Gemini has been resolved for all affected users as of Thursday, 2026-05-07 17:00 PDT.\nThe 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.\nWe thank you for your patience while we worked on resolving the issue.\n**Symptoms**\nAffected customers may have experienced the \"Something went wrong(13)\" error message in their Gemini conversations.","createdAt":"2026-05-08T01:00:01+00:00"},{"id":"update_gws_1hr418kjGyBZ9ugXy3W3_20260508t0516230000","status":"monitoring","body":"**Summary**\nGemini conversations are experiencing elevated error rates.\n**Description**\nOur engineering team has determined that further investigation is required to mitigate the issue.\nWe do not have an ETA for mitigation at this point.\nWe will provide more information by Friday, 2026-05-08 01:00 PDT.\n**Symptoms**\nAffected customers may encounter \"Something went wrong(13)\" error message in their Gemini conversations.\n**Workaround**\nNone at this time.","createdAt":"2026-05-08T05:16:23+00:00"},{"id":"update_gws_1hr418kjGyBZ9ugXy3W3_20260508t0729250000","status":"monitoring","body":"**Summary**\nGemini conversations may experience elevated error rates.\n**Description**\nOur engineering team has isolated the underlying issue and is in the process of reverting the specific code deployments that triggered the impact.\nWe are actively monitoring the progress of the rollback, alongside system health indicators, to confirm that the restoration is proceeding effectively.\nWe will provide more information by Friday, 2026-05-08 04:00 PDT.\n**Symptoms**\nAffected customers may encounter \"Something went wrong(13)\" error message in their Gemini conversations.\n**Workaround**\nNone at this time.","createdAt":"2026-05-08T07:29:25+00:00"},{"id":"update_gws_1hr418kjGyBZ9ugXy3W3_20260508t1023420000","status":"monitoring","body":"**Summary**\nGemini conversations may experience elevated error rates.\n**Description**\nOur engineering team has isolated the underlying issue and is in the process of reverting the specific code deployments that triggered the impact.\nWe are actively monitoring the progress of the rollback, alongside system health indicators, to confirm that the restoration is proceeding effectively.\nWe will provide more information by Friday, 2026-05-08 09:00 PDT.\n**Symptoms**\nAffected customers may encounter \"Something went wrong(13)\" error message in their Gemini conversations.\n**Workaround**\nNone at this time.","createdAt":"2026-05-08T10:23:42+00:00"},{"id":"update_gws_1hr418kjGyBZ9ugXy3W3_20260508t1553130000","status":"monitoring","body":"**Summary**\nGemini conversations may experience elevated error rates.\n**Description**\nOur engineering team has isolated the underlying issue and is in the process of reverting the specific code deployments that triggered the impact.\nWe are actively monitoring the progress of the rollback, alongside system health indicators, to confirm that the restoration is proceeding effectively.\nWe will provide more information by Friday, 2026-05-08 12:00 PDT.\n**Symptoms**\nAffected customers may encounter \"Something went wrong(13)\" error message in their Gemini conversations.\n**Workaround**\nNone at this time.","createdAt":"2026-05-08T15:53:13+00:00"},{"id":"update_gws_1hr418kjGyBZ9ugXy3W3_20260508t1858090000","status":"resolved","body":"**Summary**\nGemini conversations may have experienced elevated error rates.\n**Description**\nThe issue with Gemini has been resolved for all affected users as of Friday, 2026-05-08 11:53 PDT.\nThe 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.\nWe thank you for your patience while we worked on resolving the issue.\n**Symptoms**\nAffected customers may have experienced \"Something went wrong(13)\" error message in their Gemini conversations.\n**Workaround**\nNone at this time.","createdAt":"2026-05-08T18:58:09+00:00"}],"access":{"plan":"public","keyed":false}}}