incident.io had 29 outages in the last 2 years totaling 36h 31m of downtime — averaging 1.2 incidents per month.
There were 29 incident.io outages since August 28, 2025 totaling 36h 31m of downtime. Each is summarised below — incident details, duration, and resolution information.
Status: Investigating We're aware of issues affecting some customers logging in using SAML - we're investigating and will provide an update shortly. Affected components SAML login (Full outage)
Status: Identified This issue remains ongoing and we're working on a resolution. All other functionality is unaffected. Existing sessions on the mobile app and dashboard are unaffected and continue to have access as normal. We'll post our next update in the next 30 minutes. Affected components SAML login (Full outage)
Status: Monitoring SAML logins are now working with increased latency. We'll continue to monitor until fully recovered. All other functionality remains unaffected. Affected components SAML login (Degraded performance)
Status: Monitoring We're continuing to see elevated errors and latency with SAML logins. All other functionality remains unaffected. Affected components SAML login (Degraded performance)
Status: Monitoring SAML logins are now performing as normal. We'll continue to monitor for any further issues. Affected components SAML login (Operational)
Status: Resolved SAML login has continued to perform as normal. Affected components SAML login (Operational)
Status: Investigating We have identified increased latency and timeouts affecting some requests to our dashboard. Issues seem to be transient, and we recommend refreshing. We are continuing to investigate. Affected components Dashboard (Degraded performance)
Status: Monitoring Latency and error rates have returned to normal. We're continuing to monitor for any further issues. Affected components Dashboard (Operational)
Status: Resolved Between 19:31:30 and 19:34:30 UTC, some requests to our dashboard hit increased latency and connectivity errors. The cause was an upstream networking incident on Google Cloud Platform. Errors were transient and refreshing usually cleared them. Latency and error rates are back to normal and we're keeping an eye on things. We'll post a post-mortem covering the full impact. Affected components Dashboard (Operational)
Status: Resolved We observed a limited increase in latency as well as a small number of dashboard errors between 19:31:30 and 19:34:30 UTC. This affected 0.03% of calls to our dashboard. This was detected by our internal synthetic monitoring. The cause of these elevated errors was due to networking issues within GCP at the time. This is confirmed by our logs showing our GCP load balancer not forwarding success responses, as well as network timeouts when trying to reach external services. The impact was limited to a small number of users and was solved by refreshing the dashboard. Affected components Dashboard (Operational)
Status: Identified 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 and message delivery. Affected components Slack app (Degraded performance)
Status: Identified Slack have acknowledged the incident on their side. You can follow their status page here: https://slack-status.com/2026-05/46d9d5d41fbedd9f. Affected components Slack app (Degraded performance)
Status: Monitoring Error rates and latency on Slack operations have returned to normal, and the integration has recovered. You can follow updates on Slack's status page here: https://slack-status.com/2026-05/46d9d5d41fbedd9f. Affected components Slack app (Operational)
Status: Monitoring We are continuing to monitor Slack as it continues to recover, and are no longer seeing any direct impact on our Slack app You can follow updates on Slack's status page here "here": https://slack-status.com/2026-05/46d9d5d41fbedd9f. Affected components Slack app (Operational)
Status: Monitoring We are continuing to monitor Slack as it recovers. We are not seeing any direct impact on our Slack app. You can follow updates on Slack’s status page here "here": https://slack-status.com/2026-05/46d9d5d41fbedd9f. Affected components Slack app (Operational)
Status: Resolved Slack have confirmed their services have largely returned to operational levels. We've not seen any direct impact on our Slack app since ~23:20 UTC yesterday. We're resolving this on our side, and you can follow any further updates on Slack’s status page here: https://slack-status.com/2026-05/46d9d5d41fbedd9f. Affected components Slack app (Operational)
Status: Monitoring We’re seeing delays of up to 30 minutes in receiving webhooks from Opsgenie, which may delay alert delivery. Our systems are operating normally and process alerts as soon as they arrive; the issue appears to be on Opsgenie’s side. We’re monitoring closely and will share updates as we learn more. Affected components Opsgenie (Degraded performance)
Status: Resolved Webhooks appear to arriving as normal again, so you should no longer see any delays. Affected components Opsgenie (Operational)
Status: Identified 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. Affected components Atlassian Statuspage (Degraded performance)
Status: Resolved Error rates have returned to normal levels. Affected components Atlassian Statuspage (Operational)
Status: Identified 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. Affected components Microsoft Teams app (Degraded performance)
Status: Monitoring 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. Affected components Microsoft Teams app (Degraded performance)
Status: Monitoring 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. Affected components Microsoft Teams app (Degraded performance)
Status: Monitoring 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. Affected components Microsoft Teams app (Degraded performance)
Status: Resolved We are no longer seeing elevated latency and error rates from Microsoft Teams. Affected components Microsoft Teams app (Operational)
Status: Identified 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.
Status: Monitoring 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.
Status: Monitoring 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.
Status: Resolved We continue to use the failover region, and Scribe performance has returned to expected levels.
Status: Investigating We are currently investigating reports that users are unable to login using Slack.
Status: Identified 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.
Status: Monitoring 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.
Status: Resolved Slack have confirmed that the issue has been fully resolved, and affected customers have verified that they can log in successfully.
Status: Identified We've identified a drop in inbound traffic to incident.io "incident.io": http://incident.io from Opsgenie. This means that alerts may be slow to show up in incident.io "incident.io": http://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. Affected components Opsgenie (Degraded performance)
Status: Resolved Traffic appears to be back to normal levels now. Affected components Opsgenie (Operational)