INCIDENT OFICIAL ARCHIVADO

Investigating elevated error rates with Gemini conversations.

Gemini · Último estado guardado del proveedor: resolved

Informe actual del servicio →

El texto de la fuente oficial se muestra en su idioma original.

Es evidencia histórica.

El último estado guardado de un evento no es el estado actual del servicio. Las listas de fuentes pueden ser incompletas, y desaparecer de una fuente no confirma recuperación. Abre el informe actual o la fuente oficial para obtener evidencia más reciente.

Detalles de evento guardados

Estado del proveedor
resolved
Impacto del proveedor
SERVICE INFORMATION
Registro del proveedor creado
05 May 2026, 23:35:49 UTC
Registro del proveedor actualizado
08 May 2026, 18:58:23 UTC
Inicio explícito del proveedor
04 May 2026, 16:40:00 UTC
Fin explícito del proveedor
08 May 2026, 18:53:00 UTC

Componentes afectados reportados por el proveedor

  • Gemini npdyhgECDJ6tB66MxXyo

Estas asociaciones describen el alcance reportado del evento. No establecen disponibilidad actual de componentes ni dependencias verificadas.

La hora de creación de un registro no es necesariamente el inicio de una interrupción. Las horas no reportadas siguen sin estar disponibles. No calculamos el tiempo de inactividad a partir de las horas de recopilación.

Producto Gemini en Google Workspace Status Dashboard. La ausencia de incidentes reportados no es una prueba independiente de disponibilidad. Este flujo no abarca Gemini API, Google AI Studio ni Vertex AI.

Actualizaciones del proveedor en revisiones guardadas

Más recientes primero. Mostramos hasta 100 actualizaciones distintas de las últimas 20 revisiones de contenido guardadas. Las modificaciones de redacción a la misma hora del proveedor se conservan por separado.

  1. AVAILABLE

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

    Visto en una revisión guardada a las 06 Oct 2026, 13:58:40 UTC
  2. 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.

    Visto en una revisión guardada a las 06 Oct 2026, 13:58:40 UTC
  3. 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.

    Visto en una revisión guardada a las 06 Oct 2026, 13:58:40 UTC
  4. 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.

    Visto en una revisión guardada a las 06 Oct 2026, 13:58:40 UTC
  5. 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.

    Visto en una revisión guardada a las 06 Oct 2026, 13:58:40 UTC
  6. 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.

    Visto en una revisión guardada a las 06 Oct 2026, 13:58:40 UTC
  7. 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.

    Visto en una revisión guardada a las 06 Oct 2026, 13:58:40 UTC
  8. 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.

    Visto en una revisión guardada a las 06 Oct 2026, 13:58:40 UTC
  9. 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.

    Visto en una revisión guardada a las 06 Oct 2026, 13:58:40 UTC
  10. 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.

    Visto en una revisión guardada a las 06 Oct 2026, 13:58:40 UTC