33 incidentes de incident.io Status registrados desde septiembre de 2025, con actualizaciones oficiales, componentes afectados, duración y detalles de resolución.
Estado: Resuelvado Este incidente ha sido resuelto. Iniciar sesión a través de Slack está operando normalmente de nuevo, y no se requiere ninguna acción adicional. Componentes afectados Aplicación Slack (Operational)
Traducido automáticamente desde la actualización oficial del incidente.
Estado: Latencia Resuelta ha vuelto a la normalidad. Entre las 13:00 y las 15:08 UTC hubo períodos de mayor latencia de algunas API de Microsoft. Los mensajes en Microsoft Teams se entregaron con mayor latencia. Nuestro panel de control y aplicación móvil no fueron afectados. Componentes afectados aplicación Microsoft Teams (Operational)
Traducido automáticamente desde la actualización oficial del incidente.
Estado: Resuelvado Ahora volamos y las alertas de listado están funcionando normalmente de nuevo. Componentes afectados Ingestión de alerta, procesamiento y paging (Operational)
Traducido automáticamente desde la actualización oficial del incidente.
Estado: Resolver la entrega de Opsgenie webhook devuelto a la normalidad alrededor de 17:48 BST Componentes afectados Opsgenie (Operational)
Traducido automáticamente desde la actualización oficial del incidente.
Estado: Resuelto Entre las 00:00 y 02:44 UTC, algunas características de AI volvieron a aumentar las tasas de error. Ahora estamos viendo la recuperación completa. (Operación) Administración (Operación)
Traducido automáticamente desde la actualización oficial del incidente.
Somos conscientes de los problemas que afectan a algunos clientes accediendo al uso de SAML - estamos investigando y proporcionaremos una actualización en breve.
Este problema sigue en curso y estamos trabajando en una resolución. Toda otra funcionalidad no está afectada. Las sesiones existentes en la aplicación móvil y el dashboard no son afectadas y siguen teniendo acceso como normal. Publicaremos nuestra próxima actualización en los próximos 30 minutos.
Los logins de SAML están trabajando con mayor latencia. Seguiremos monitoreando hasta que se recuperen completamente. Toda otra funcionalidad no se ve afectada.
Continuamos viendo errores elevados y latencia con los logins de SAML. Toda otra funcionalidad no se ve afectada.
Los logins de SAML se están ejecutando como normales. Seguiremos monitoreando para cualquier otro problema.
El login SAML ha continuado actuando como normal.
Traducido automáticamente desde la actualización oficial del incidente.
Hemos identificado un aumento de latencia y los plazos que afectan algunas solicitudes a nuestro dashboard. Los problemas parecen ser transitorios, y recomendamos refrescarnos. Continuamos investigando.
Latency and error rates have returned to normal. Seguiremos monitoreando para cualquier otro problema.
Entre las 19:31:30 y las 19:34:30 UTC, algunas peticiones a nuestro dashboard alcanzaron mayores errores de latencia y conectividad. La causa fue un incidente de networking en Google Cloud Platform. Los errores eran transitorios y refrescante generalmente los limpiaba. Latencia y las tasas de error vuelven a la normalidad y estamos vigilando las cosas. Pondremos un post-mortem cubriendo todo el impacto.
Se observó un aumento limitado de latencia, así como un pequeño número de errores de panel de control entre 19:31:30 y 19:34:30 UTC. Esto afectó el 0\.03% de las llamadas a nuestro panel. Esto fue detectado por nuestro monitoreo sintético interno. La causa de estos errores elevados se debió a problemas de redes dentro del GCP en ese momento. Esto es confirmado por nuestros registros mostrando nuestro balanceador de carga GCP no reenviando respuestas de éxito, así como los plazos de red cuando intentan llegar a servicios externos. El impacto se limitó a un pequeño número de usuarios y fue resuelto refrescando el panel de control.
Traducido automáticamente desde la actualización oficial del incidente.
Hemos identificado mayores tasas de error con nuestra integración Slack. Actualmente estamos investigando cómo esto está afectando nuestra plataforma - esto parece ser un problema en el lado Slack, particularmente alrededor de la creación de canales y la entrega de mensajes.
Slack ha reconocido el incidente de su lado. Puede seguir su estado [aquí](https://slack-status.com/2026-05/46d9d5d41fbedd9f).
Las tasas de error y latencia en las operaciones de Slack han vuelto a la normalidad, y la integración se ha recuperado. Puede seguir las actualizaciones de la página de estado de Slack [aquí](https://slack-status.com/2026-05/46d9d5d41fbedd9f).
Continuamos monitoreando a Slack mientras continúa recuperándose, y ya no estamos viendo ningún impacto directo en nuestra aplicación Slack Puede seguir las actualizaciones de la página de estado de Slack [aquí](https://slack-status.com/2026-05/46d9d5d41fbedd9f "aquí").
Continuamos monitorizando a Slack mientras se recupera. No estamos viendo ningún impacto directo en nuestra aplicación Slack. Puede seguir las actualizaciones de la página de estado de Slack [aquí](https://slack-status.com/2026-05/46d9d5d41fbedd9f "aquí").
Slack ha confirmado que sus servicios han regresado en gran medida a los niveles operacionales. No hemos visto ningún impacto directo en nuestra aplicación Slack desde ~23:20 UTC ayer. Estamos resolviendo esto de nuestro lado, y usted puede seguir cualquier actualización adicional en la página de estado de Slack [aquí](https://slack-status.com/2026-05/46d9d5d41fbedd9f).
Traducido automáticamente desde la actualización oficial del incidente.
We have identified increased error rates with our Slack integration. We are currently investigating how this is impacting our platform - this seems to be an issue on the Slack side, particularly around channel creation.
We've confirmed the issue is relating to errors being returned by Slack. This is affecting a number of features of our integration, including: • Creating incident channels • Sending messages • Syncing Slack user groups Our web dashboard continues to be available and Scribe is unaffected.
Slack have acknowledged the incident on their side. You can follow their status page [here](https://slack-status.com/2026-05/fe557ca05fdb64fa).
We're continuing to monitor the situation - Slack have posted an update on their status page to confirm that they're working on it.
The issue has been resolved on Slack's side and we've confirmed that things look normal on our side too.
Traducido automáticamente desde la actualización oficial del incidente.
The website is now up and working as normal.
The web dashboard is unavailable due to a JavaScript deployment issue.
Traducido automáticamente desde la actualización oficial del incidente.
Estamos viendo retrasos de hasta 30 minutos en la recepción de webhooks de Opsgenie, que puede retrasar la entrega de alerta. Nuestros sistemas están operando normalmente y alertas de proceso tan pronto como lleguen; el problema parece estar en el lado de Opsgenie. Estamos monitoreando de cerca y compartiremos actualizaciones mientras aprendemos más.
Webhooks parece volver a llegar como normal, por lo que ya no debe ver ningún retraso.
Traducido automáticamente desde la actualización oficial del incidente.
We have identified increased error rates with our Atlassian Statuspage integration. Atlassian have published this to their status page [here](https://metastatuspage.com/incidents/94fwk40f4z15).
Error rates have returned to normal levels.
We have identified increased error rates coming from Microsoft Teams. We are currently investigating how this is impacting our platform and we will update with more information shortly as we learn more.
We have identified increased error rates coming from Microsoft Teams that are causing delays in sending messages to Teams channels and DMs. We'll continue to monitor the situation and we will update with more information shortly as we learn more. We will provide the next update by 1830 UTC.
We are continuing to see an increase in error rates from Microsoft Teams, causing a delay in sending some messages to Teams channels and DMs. We are monitoring the situation and will provide an update by 1930 UTC.
We have seen an improvement in error rates and latency for requests to Microsoft Teams, and we expect the performance of sending messages to Teams channels and DMs to have returned to normal. We are continuing to monitor to ensure performance remains as expected, and we will provide a further update by 2100 UTC.
We are no longer seeing elevated latency and error rates from Microsoft Teams.
We have identified increased error rates with an upstream call transcription provider. This is affecting Scribe for all customers. Our team are investigating and we will update with more information shortly as we learn more.
The issues were isolated to one region and we have performed a failover to a secondary region, restoring Scribe for all customers. You may need to ask Scribe to rejoin your call. We'll continue to monitor the situation and are working closely with the upstream provider while they resolve the issue.
Our failover region is continuing to work as expected, and Scribe functionality has been restored. You may need to ask Scribe to rejoin your calls. We'll continue to monitor the situation and are working closely with the upstream provider while they resolve the issue.
We continue to use the failover region, and Scribe performance has returned to expected levels.
We are currently investigating reports that users are unable to login using Slack.
Users in some Slack workspaces are unable to sign in with Slack. We have escalated this issue to Slack. Signing in with SAML and Microsoft Teams is not affected.
Slack have rolled back a change which caused this issue, and we have confirmed recovery. Please reach out to support if you're still experiencing any issues signing in with Slack.
Slack have confirmed that the issue has been fully resolved, and affected customers have verified that they can log in successfully.
We've identified a drop in inbound traffic to [incident.io](http://incident.io "incident.io") from Opsgenie. This means that alerts may be slow to show up in [incident.io](http://incident.io "incident.io"), and paging via Opsgenie may be slow to reflect updates. This appears to be an issue with outbound webhooks on Opsgenie's side, we're monitoring the situation and will update as we know more.
Traffic appears to be back to normal levels now.
We have identified increased error rates with our Atlassian Statuspage integration. Atlassian have acknowledged an issue on their side (<https://metastatuspage.com/incidents/ctw5xv6t643h>). We'll continue to monitor this until the issue is resolved.
Atlassian's status page continues to show the issue with Statuspage (<https://metastatuspage.com/incidents/ctw5xv6t643h>). To restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in incident.io. We'll continue to monitor this until the issue is resolved.
Atlassian's status page continues to show the issue with Statuspage (<https://metastatuspage.com/incidents/ctw5xv6t643h>). To restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in [incident.io.](http://incident.io./ "incident.io.") We'll continue to monitor this until the issue is resolved.
Atlassian's status page continues to show the issue with Statuspage (<https://metastatuspage.com/incidents/ctw5xv6t643h>). To restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in [incident.io.](http://incident.io./ "incident.io.") We'll continue to monitor this and give an update in the next hour.
Atlassian's status page now reports that they are rolling out a fix (<https://metastatuspage.com/incidents/ctw5xv6t643h>). In the meantime, to restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in [incident.io.](http://incident.io./ "incident.io.") We continue to monitor the issue until it is resolved.
Atlassian have confirmed that the issues with Statuspage have been resolved. You should now be able to reuse your original API key in our integration.
We have identified increased error rates with our Sentry integration. We are currently investigating how this is impacting our platform and we will update with more information shortly as we learn more.
Sentry have acknowledged an issue on their side ([https://status.sentry.io/incidents/wpg3tnwnwctj](https://status.sentry.io/incidents/wpg3tnwnwctj "https://status.sentry.io/incidents/wpg3tnwnwctj")), and we're seeing alerts come through from them ok. We'll continue to monitor things before closing this out.
We've not seen any errors from Sentry since 15:35 UTC so we're closing this out. Please see Sentry's status page for any further details.
We have identified an increased rate of Sentry integrations becoming disconnected. Alert ingestion is unaffected. Please don't uninstall our application from Sentry: we are working to restore these connections on our side, and no action is currently required. We will provide an update in 30 minutes.
We're currently testing the fix that will allow us to re-connect any disconnected Sentry integrations on behalf of customers, and will have another update on this in 30 minutes.
We've verified a fix locally, and we're starting to roll this out in production now.
We have confirmed that we are able to restore these connections, and we are now in the process of restoring these. When this happens, you'll see that the Sentry integration no longer flags up as requiring reconnection. Once we have finished restoring access, we'll post another update here.
We have managed to re-establish a connection to Sentry for almost all of the affected customers. If Sentry is still showing up as disconnected, you will need to remove the incident.io integration from the Sentry side, and then go through the reinstallation flow by opening incident.io and going to Settings → Integrations → Sentry. If you do this, please note that Sentry will remove the "Notify incident.io" action from alert rules when you uninstall the integration. If that was the only action in the alert rule, the entire rule is disabled. You will therefore need to verify any alert rules after re-installing.
We are aware of an issue that is causing delays updating data in Insights. The team are currently investigating, and we'll provide further updates soon.
We are aware of an issue that is causing delays updating data in Insights. The team are currently working on mitigating this, and we'll provide further updates soon.
The team have resolved this issue, and Insights are now syncing as expected.
