Incident report · read from Google's status page

Google incident: Investigating elevated error rates with Gemini conversations.

Resolved after 4 d 2 h (4 May 2026 16:40 – 8 May 2026 18:53 UTC), impact minor, affecting Gemini.

Timeline

  1. identified

    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.

  2. identified

    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.

  3. identified

    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.

  4. identified

    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.

  5. identified

    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.

  6. identified

    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.

  7. identified

    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.

  8. identified

    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.

  9. identified

    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.

  10. 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.

Affected components

Source

Google's own report of this incident, on Google's status page. This page is a record of Google's own report; where the two disagree, theirs is right.

Last checked .

Must Have AI is a parody and is not affiliated with, endorsed by or connected to OpenAI, Anthropic or Google. Every outage shown here is read from the provider's own public status page.