incident.io Outage History

incident.io experienced delays in receiving webhooks from Opsgenie, causing alert delivery delays of up to 30 minutes. The issue was identified as originating from Opsgenie's side rather than incident.io's systems, which continued operating normally. The incident was resolved after 19 minutes of monitoring and investigation.

incident.io experienced intermittent errors with their Atlassian Statuspage integration due to increased error rates in the service. The issue affected the ability to post updates to Atlassian Statuspages and was linked to a broader Atlassian service incident. The problem lasted 25 minutes and was identified and tracked through Atlassian's own status page reporting.

incident.io experienced increased error rates from Microsoft Teams integration that caused delays in sending messages to Teams channels and direct messages. The issue affected the platform's ability to deliver notifications through Microsoft Teams for 4.4 hours. Error rates and latency improved and returned to normal performance levels.

Incident.io's Scribe service experienced degraded performance due to increased error rates from an upstream call transcription provider, affecting all customers for 1.6 hours. The team identified the issues were isolated to one region and performed a failover to a secondary region, restoring Scribe functionality. Customers may need to ask Scribe to rejoin their calls following the restoration.

Some users were unable to sign in to incident.io via Slack due to an issue affecting certain Slack workspaces. The problem was caused by a change on Slack's side and did not affect SAML or Microsoft Teams login methods. The issue was resolved after 2.4 hours when Slack rolled back the problematic change.