33 incident.io Status incidents · Gwengolo 2025 — official updates, affected components, duration and resolution details.
Estado: resolvido Este incidente foi resolvido. Login via Slack está funcionando normalmente novamente, e nenhuma ação adicional é necessária. Componentes afetados Aplicativo Slack (Operativo)
Traduzido automaticamente da atualização oficial do incidente.
Status: A latência resolvida voltou ao normal. Entre as 13:00 e 15:08 UTC houve períodos de latência aumentada de algumas APIs da Microsoft. As mensagens nas Equipes Microsoft foram entregues com maior latência. Nosso painel e aplicativo móvel não foram afetados. Componentes afetados App Microsoft Teams (Operativa)
Traduzido automaticamente da atualização oficial do incidente.
Estado: resolvido Recuámos e os alertas estão a funcionar normalmente. Componentes afetados Alertar a ingestão, processamento e paginação (Operativa)
Traduzido automaticamente da atualização oficial do incidente.
Status: Resolvido Opsgenie webhook entrega retornou ao normal em torno 17:48 BST componentes afetados Opsgenie (Operação)
Traduzido automaticamente da atualização oficial do incidente.
Status: Resolvido Entre cerca de 00:00 e 02:44 UTC, alguns recursos de IA retornaram taxas de erro aumentadas. Estamos agora a ver uma recuperação total. Componentes afetados Google Docs (operacional) Azure DevOps (operacional) Shortcut (operacional) API (operacional) Splunk (operacional) Email (operacional) Microsoft Teams app (operacional) ClickUp (operacional) Confluência (operacional) OpsLevel (operacional) Asana (operacional) Jira (operacional) Sentry (operacional) Zapier (operacional) Slack app (operacional) Atlassian Statuspage (operacional) Cortex (operacional) PagerDuty (operacional) GitHub (operacional) SAML login (operacional) Opsgenie (operacional) Phone (operacional) Push Notifications (operacional) Insights (operacional) Okta (operacional) Dashboard (operacional) Google Calendar (operacional) Alertar a ingestão, processamento e paging (Operativa) SMS (Operativa) Páginas de Status (Operativa) Google Meet (Operativa)
Traduzido automaticamente da atualização oficial do incidente.
Estamos cientes de problemas que afetam alguns clientes fazendo login usando SAML - estamos investigando e forneceremos uma atualização em breve.
Esta questão continua em curso e estamos a trabalhar numa resolução. Todas as outras funcionalidades não são afetadas. As sessões existentes no aplicativo e painel móvel não são afetadas e continuam a ter acesso normal. Publicaremos a nossa próxima actualização nos próximos 30 minutos.
Os logins SAML agora estão trabalhando com latência aumentada. Continuaremos a monitorizar até recuperarmos completamente. Todas as outras funcionalidades permanecem inalteradas.
Continuamos a ver erros e latência elevados com logins SAML. Todas as outras funcionalidades permanecem inalteradas.
Os logins SAML agora estão funcionando como normais. Continuaremos a monitorizar quaisquer outras questões.
O login do SAML continuou a funcionar normalmente.
Traduzido automaticamente da atualização oficial do incidente.
Identificamos um aumento de latência e tempo de espera afetando algumas solicitações ao nosso painel. As questões parecem ser transitórias, e recomendamos refrescante. Continuamos a investigar.
A latência e as taxas de erro voltaram ao normal. Continuamos a monitorizar quaisquer outros problemas.
Entre 19:31:30 e 19:34:30 UTC, alguns pedidos para o nosso painel atingiram maiores erros de latência e conectividade. A causa foi um incidente de rede no Google Cloud Platform. Os erros eram transitórios e geralmente refrescantes. A latência e as taxas de erro voltaram ao normal e estamos de olho nas coisas. Postaremos uma autópsia cobrindo o impacto total.
Observamos um aumento limitado na latência, bem como um pequeno número de erros de painel entre 19:31:30 e 19:34:30 UTC. Isso afetou 0\.03% das chamadas para o nosso painel. Isso foi detectado pelo nosso monitoramento sintético interno. A causa desses erros elevados foi devido a problemas de rede dentro do GCP na época. Isso é confirmado por nossos logs mostrando nosso balanceador de carga GCP não encaminhando respostas de sucesso, bem como timeouts de rede ao tentar alcançar serviços externos. O impacto foi limitado a um pequeno número de usuários e foi resolvido ao refrescar o painel.
Traduzido automaticamente da atualização oficial do incidente.
Nós identificamos taxas de erro aumentadas com nossa integração Slack. Estamos atualmente investigando como isso está impactando nossa plataforma - isso parece ser um problema do lado Slack, particularmente em torno da criação de canais e entrega de mensagens.
Slack reconheceu o incidente do lado deles. Você pode seguir sua página de status [aqui](https://slack-status.com/2026-05/46d9d5d41fbedd9f).
Taxas de erro e latência em operações Slack retornaram ao normal, e a integração recuperou. Você pode acompanhar as atualizações na página de status do Slack [aqui](https://slack-status.com/2026-05/46d9d5d41fbedd9f).
Estamos continuando a monitorar Slack como ele continua a recuperar, e não estão mais vendo qualquer impacto direto em nosso aplicativo Slack Você pode acompanhar as atualizações na página de status do Slack [aqui](https://slack-status.com/2026-05/46d9d5d41fbedd9f "aqui").
Continuamos a monitorizar o Slack à medida que se recupera. Não estamos vendo nenhum impacto direto em nosso aplicativo Slack. Você pode acompanhar as atualizações na página de status do Slack [aqui](https://slack-status.com/2026-05/46d9d5d41fbedd9f "aqui").
A Slack confirmou que os seus serviços regressaram largamente aos níveis operacionais. Não vimos nenhum impacto direto no nosso aplicativo Slack desde 23:20 UTC ontem. Estamos resolvendo isso do nosso lado, e você pode acompanhar quaisquer atualizações adicionais na página de status do Slack [aqui](https://slack-status.com/2026-05/46d9d5d41fbedd9f).
Traduzido automaticamente da atualização oficial do 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.
Traduzido automaticamente da atualização oficial do incidente.
The website is now up and working as normal.
The web dashboard is unavailable due to a JavaScript deployment issue.
Traduzido automaticamente da atualização oficial do incidente.
Estamos vendo atrasos de até 30 minutos em receber webhooks da Opsgenie, o que pode atrasar a entrega de alerta. Nossos sistemas estão funcionando normalmente e processam alertas assim que chegam; a questão parece estar do lado da Opsgenie. Estamos monitorando de perto e compartilharemos atualizações conforme soubermos mais.
Webhooks parecem chegar como normal novamente, então você não deve mais ver quaisquer atrasos.
Traduzido automaticamente da atualização oficial do 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.
