33 incident.io Status incidents · september 2025 — official updates, affected components, duration and resolution details.
Status: Opløst Denne hændelse er blevet løst. Login via Slack fungerer normalt igen, og der kræves ingen yderligere handling. Berørte komponenter Slack app (Operationel)
Automatisk oversat fra den officielle hændelsesopdatering.
Status: Løsningen på Latency er nu vendt tilbage til normal. Mellem 13: 00 og 15: 08 UTC var der perioder med øget latency fra nogle Microsoft API 'er. Meddelelser i Microsoft Teams blev leveret med øget latency. Vores dashboard og mobil app blev ikke påvirket. Berørte komponenter Microsoft Team app (Operationelle)
Automatisk oversat fra den officielle hændelsesopdatering.
Status: Opløst Vi har nu rullet tilbage og listen indberetninger fungerer normalt igen. Berørte komponenter Alert indtagelse, behandling og personsøgning (drift)
Automatisk oversat fra den officielle hændelsesopdatering.
Status: Løs Opsgenie webhook levering tilbage til normal på omkring 17: 48 BST Berørte komponenter Opsgenie (Operationel)
Automatisk oversat fra den officielle hændelsesopdatering.
Status: Løs mellem omkring 00: 00 og 02: 44 UTC, nogle AI funktioner returneret øgede fejlrater. Vi ser nu fuld bedring. Berørte komponenter Zoom (Operational) Slack (Operational) Mobile app (Operational) SAML login (Operational) Atlantisk Statuspage (Operational) Genvej (Operational) Push notifikationer (Operational) Microsoft Teams app (Operational) Okta (Operational) Zapier (Operational) Splunk (Operational) Alert (Operational) Azure DevOps (Operational) Opsgenie (Operational) API (Operational) Dashboard (Operational) Vana (Operational) SLAck app (Operational) Operational) Operational) Operational (Operational) Operational (Operational) (Operational) Operational) Operational (Operational) (Operational) (Operational) (Operational) Operational) (Operational) (Operational) Operational) (Operational) Operational) Operational) Asanal) Asanal) Asanal) (Operational
Automatisk oversat fra den officielle hændelsesopdatering.
Vi er opmærksomme på problemer, der påvirker nogle kunder logge ind ved hjælp af SAML - vi undersøger og vil levere en opdatering inden for kort tid.
Dette spørgsmål fortsætter, og vi arbejder på en beslutning. Alle andre funktioner er upåvirket. Eksisterende sessioner på den mobile app og dashboard er upåvirket og fortsætter med at have adgang som normalt. Vi sender næste opdatering om 30 minutter.
SAML logins arbejder nu med øget latency. Vi fortsætter med at overvåge, indtil vi er kommet os. Alle andre funktioner forbliver upåvirket.
Vi fortsætter med at se forhøjede fejl og latency med SAML logins. Alle andre funktioner forbliver upåvirket.
SAML logins fungerer nu som normalt. Vi fortsætter med at overvåge for yderligere problemer.
SAML login har fortsat med at udføre som normalt.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi har identificeret øget latency og timeout påvirker nogle anmodninger til vores dashboard. Spørgsmål synes at være forbigående, og vi anbefaler forfriskende. Vi fortsætter med at undersøge sagen.
Late og fejlrater er vendt tilbage til normal. Vi fortsætter med at overvåge for yderligere problemer.
Mellem 19: 31: 30 og 19: 34: 30 UTC, nogle anmodninger til vores dashboard ramte øget latency og forbindelse fejl. Årsagen var en opstrømsnetværkshændelse på Google Cloud Platform. Fejl var forbigående og forfriskende normalt ryddet dem. Late og fejlrater er normale igen, og vi holder øje med tingene. Vi sender en post-mortem, der dækker det hele.
Vi observerede en begrænset stigning i latency samt et lille antal dashboard fejl mellem 19: 31: 30 og 19: 34: 30 UTC. Dette påvirkede 0\ .03% af opkald til vores dashboard. Dette blev opdaget af vores interne syntetiske overvågning. Årsagen til disse forhøjede fejl skyldtes netværksproblemer inden for GCP på det tidspunkt. Dette bekræftes af vores logfiler, der viser vores GCP belastning balancer ikke videresendelse succesfulde svar, samt netværk timeouts, når du forsøger at nå eksterne tjenester. Virkningen var begrænset til et lille antal brugere og blev løst ved at opfriske instrumentbrættet.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi har identificeret øgede fejlrater med vores Slack integration. Vi undersøger i øjeblikket, hvordan dette påvirker vores platform - dette synes at være et problem på Slack side, især omkring kanal skabelse og meddelelse levering.
Slack har erkendt hændelsen på deres side. Du kan følge deres statusside [her] (https: / / slack- status.com / 2026- 05 / 46d9d5d41fbedd9f).
Fejlrater og latency på Slack operationer er vendt tilbage til normal, og integrationen er kommet sig. Du kan følge opdateringer på Slack 's status side [her] (https: / / slack- status.com / 2026- 05 / 46d9d5d41fbedd9f).
Vi fortsætter med at overvåge Slack som det fortsætter med at komme sig, og er ikke længere ser nogen direkte indvirkning på vores Slack app Du kan følge opdateringer på Slack status side [her] (https: / / slack- status.com / 2026- 05 / 46d9d5d41fbedd9f "her").
Vi fortsætter med at overvåge Slack, efterhånden som det kommer sig. Vi ser ingen direkte indvirkning på vores Slack app. Du kan følge opdateringer på Slack status side [her] (https: / / slack- status.com / 2026- 05 / 46d9d5d41fbedd9f "her").
Slack har bekræftet deres tjenester er i vid udstrækning vendt tilbage til operationelle niveauer. Vi har ikke set nogen direkte indvirkning på vores Slack app siden ~ 23: 20 UTC i går. Vi løser dette på vores side, og du kan følge yderligere opdateringer på Slack 's status side [her] (https: / / slack- status.com / 2026- 05 / 46d9d5d41fbedd9f).
Automatisk oversat fra den officielle hændelsesopdatering.
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.
Automatisk oversat fra den officielle hændelsesopdatering.
The website is now up and working as normal.
The web dashboard is unavailable due to a JavaScript deployment issue.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi ser forsinkelser på op til 30 minutter i at modtage webkroge fra Opsgenie, hvilket kan forsinke alarmforsyningen. Vores systemer fungerer normalt og behandle advarsler, så snart de ankommer; problemet synes at være på Opsgenies side. Vi overvåger nøje og vil dele opdateringer, som vi lærer mere.
Webkroge synes at ankomme som normalt igen, så du bør ikke længere se nogen forsinkelser.
Automatisk oversat fra den officielle hændelsesopdatering.
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.
