Google incident · via Google Workspace

Investigating elevated error rates with Gemini conversations.

Minor Resolved View vendor source →

Google experienced a minor incident on May 4, 2026 affecting Gemini, lasting 4d 2h. The incident has been resolved; the full update timeline is below.

Started
May 04, 2026, 04:40 PM UTC
Resolved
May 08, 2026, 06:53 PM UTC
Duration
4d 2h
Detected by Pingoru
May 04, 2026, 04:40 PM UTC

Affected components

Gemini

Update timeline

  1. monitoring May 05, 2026, 11:35 PM UTC

    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.

  2. monitoring May 06, 2026, 03:22 AM UTC

    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.

  3. monitoring May 06, 2026, 07:11 PM UTC

    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.

  4. monitoring May 07, 2026, 11:52 PM UTC

    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.

  5. resolved May 08, 2026, 01:00 AM UTC

    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 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 the "Something went wrong(13)" error message in their Gemini conversations.

  6. monitoring May 08, 2026, 05:16 AM UTC

    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.

  7. monitoring May 08, 2026, 07:29 AM UTC

    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.

  8. monitoring May 08, 2026, 10:23 AM UTC

    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.

  9. monitoring May 08, 2026, 03:53 PM UTC

    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.

  10. resolved May 08, 2026, 06:58 PM UTC

    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.