incident.io Outage History

Started Nov 02, 2026, 03:39 PM UTC· resolved Nov 02, 2026, 05:35 PM UTC

1. identified Nov 02, 2026, 03:39 PM UTC

   We have identified increased error rates and latency 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's incident can be tracked on their status page here: https://status.sentry.io/incidents/35sw8wr49l3p.

2. monitoring Nov 02, 2026, 04:15 PM UTC

   Sentry is experiencing an outage affecting their API. Alerts from Sentry are still being received. Other actions we take in Sentry, such as adding comments to linked issues or automatically resolving them, may fail or be delayed until Sentry recovers. You can follow Sentry's incident on their status page: https://status.sentry.io/incidents/35sw8wr49l3p.

3. resolved Nov 02, 2026, 05:35 PM UTC

   We're seeing that Sentry performance has returned to normal. Sentry have reported that the issue is mitigated, but they are continuing to monitor the situation. You can follow further updates on their status page: https://status.sentry.io/incidents/35sw8wr49l3p.

Read the full incident report →

Started Oct 02, 2026, 10:33 PM UTC· resolved Oct 02, 2026, 11:47 PM UTC

1. identified Oct 02, 2026, 10:33 PM UTC

   Some customers on Slack Enterprise Grid who sign in with Slack are seeing Slack-originating errors when logging in. We've raised this with Slack and are monitoring for a fix. Customers using SAML sign-in aren't affected. Alert ingestion and our On-call product's paging functionality are unaffected.

2. resolved Oct 02, 2026, 11:47 PM UTC

   This incident has been resolved. Login via Slack is operating normally again, and no further action is required.

Read the full incident report →

Started Aug 20, 2026, 01:02 PM UTC· resolved Aug 20, 2026, 04:31 PM UTC

1. identified Aug 20, 2026, 02:42 PM UTC

   We have identified increased latency in our Microsoft Teams app. We are currently investigating how this is impacting our platform and we will update with more information shortly as we learn more.

2. identified Aug 20, 2026, 03:31 PM UTC

   We are continuing to see periods of increased latency with our Microsoft Teams app. All other surfaces, including the dashboard and our mobile app, remain unaffected.

3. resolved Aug 20, 2026, 04:31 PM UTC

   Latency has now returned to normal. Between 13:00 and 15:08 UTC there were periods of increased latency from some Microsoft APIs. Messages in Microsoft Teams were delivered with increased latency. Our dashboard and mobile app were not affected.

Read the full incident report →

Started Aug 18, 2026, 11:24 AM UTC· resolved Aug 18, 2026, 11:37 AM UTC

1. identified Aug 18, 2026, 11:24 AM UTC

   We've identified an issue listing alerts. Regular alerting and paging is unaffected.

2. resolved Aug 18, 2026, 11:37 AM UTC

   We've now rolled back and listing alerts is working normally again.

Read the full incident report →

Started Aug 03, 2026, 03:56 PM UTC· resolved Aug 03, 2026, 05:04 PM UTC

1. identified Aug 03, 2026, 03:56 PM UTC

   We have identified increased webhook latency with our Opsgenie integration. We are currently investigating how this is impacting our platform and we will update with more information shortly as we learn more.

2. resolved Aug 03, 2026, 05:04 PM UTC

   Opsgenie webhook delivery returned to normal at around 17:48 BST

Read the full incident report →

Started Aug 01, 2026, 12:08 AM UTC· resolved Aug 01, 2026, 02:45 AM UTC

1. investigating Aug 01, 2026, 12:08 AM UTC

   We detected increased error rates with some AI features.

2. resolved Aug 01, 2026, 02:45 AM UTC

   Between around 00:00 and 02:44 UTC, some AI features returned increased error rates. We are now seeing full recovery.

Read the full incident report →

Started Jul 16, 2026, 08:02 AM UTC· resolved Jul 16, 2026, 10:12 AM UTC

1. investigating Jul 16, 2026, 08:32 AM UTC

   We're aware of issues affecting some customers logging in using SAML - we're investigating and will provide an update shortly.

2. identified Jul 16, 2026, 09:12 AM UTC

   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.

3. monitoring Jul 16, 2026, 09:27 AM UTC

   SAML logins are now working with increased latency. We'll continue to monitor until fully recovered. All other functionality remains unaffected.

4. monitoring Jul 16, 2026, 10:16 AM UTC

   We're continuing to see elevated errors and latency with SAML logins. All other functionality remains unaffected.

5. monitoring Jul 16, 2026, 10:29 AM UTC

   SAML logins are now performing as normal. We'll continue to monitor for any further issues.

6. resolved Jul 16, 2026, 10:54 AM UTC

   SAML login has continued to perform as normal.

Read the full incident report →

Started Jun 23, 2026, 07:31 PM UTC· resolved Jun 23, 2026, 07:35 PM UTC

1. investigating Jun 23, 2026, 07:45 PM UTC

   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.

2. monitoring Jun 23, 2026, 07:55 PM UTC

   Latency and error rates have returned to normal. We're continuing to monitor for any further issues.

3. resolved Jun 23, 2026, 08:25 PM UTC

   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.

4. resolved Jun 25, 2026, 11:51 AM UTC

   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.

Read the full incident report →

Started May 27, 2026, 10:24 PM UTC· resolved May 27, 2026, 11:21 PM UTC

1. identified May 27, 2026, 10:42 PM UTC

   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.

2. identified May 27, 2026, 11:02 PM UTC

   Slack have acknowledged the incident on their side. You can follow their status page here: https://slack-status.com/2026-05/46d9d5d41fbedd9f.

3. monitoring May 27, 2026, 11:21 PM UTC

   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.

4. monitoring May 28, 2026, 12:19 AM UTC

   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.

5. monitoring May 28, 2026, 02:31 AM UTC

   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.

6. resolved May 28, 2026, 06:29 AM UTC

   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.

Read the full incident report →

Started May 14, 2026, 02:08 PM UTC· resolved May 14, 2026, 03:45 PM UTC

1. identified May 14, 2026, 02:08 PM UTC

   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.

2. identified May 14, 2026, 02:12 PM UTC

   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.

3. monitoring May 14, 2026, 02:41 PM UTC

   Slack have acknowledged the incident on their side. You can follow their status page here: https://slack-status.com/2026-05/fe557ca05fdb64fa.

4. monitoring May 14, 2026, 03:15 PM UTC

   We're continuing to monitor the situation - Slack have posted an update on their status page to confirm that they're working on it.

5. resolved May 14, 2026, 03:45 PM UTC

   The issue has been resolved on Slack's side and we've confirmed that things look normal on our side too.

Read the full incident report →

Started May 07, 2026, 07:12 AM UTC· resolved May 07, 2026, 07:25 AM UTC

1. identified May 07, 2026, 07:12 AM UTC

   The web dashboard is unavailable due to a JavaScript deployment issue.

2. resolved May 07, 2026, 07:25 AM UTC

   The website is now up and working as normal.

Read the full incident report →

Started Apr 27, 2026, 11:58 PM UTC· resolved Apr 28, 2026, 12:14 AM UTC

1. monitoring Apr 27, 2026, 11:58 PM UTC

   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.

2. resolved Apr 28, 2026, 12:14 AM UTC

   Webhooks appear to arriving as normal again, so you should no longer see any delays.

Read the full incident report →

Started Apr 09, 2026, 07:05 AM UTC· resolved Apr 09, 2026, 07:49 AM UTC

1. identified Apr 09, 2026, 07:33 AM UTC

   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.

2. resolved Apr 09, 2026, 07:55 AM UTC

   Error rates have returned to normal levels.

Read the full incident report →

Started Mar 24, 2026, 04:30 PM UTC· resolved Mar 24, 2026, 08:52 PM UTC

1. identified Mar 24, 2026, 04:30 PM UTC

   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.

2. monitoring Mar 24, 2026, 05:27 PM UTC

   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.

3. monitoring Mar 24, 2026, 06:33 PM 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.

4. monitoring Mar 24, 2026, 07:30 PM 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.

5. resolved Mar 24, 2026, 08:52 PM UTC

   We are no longer seeing elevated latency and error rates from Microsoft Teams.

Read the full incident report →

Started Mar 24, 2026, 03:31 PM UTC· resolved Mar 24, 2026, 05:02 PM UTC

1. identified Mar 24, 2026, 03:31 PM UTC

   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.

2. monitoring Mar 24, 2026, 03:33 PM UTC

   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.

3. monitoring Mar 24, 2026, 04:18 PM UTC

   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.

4. resolved Mar 24, 2026, 05:02 PM UTC

   We continue to use the failover region, and Scribe performance has returned to expected levels.

Read the full incident report →

Started Mar 13, 2026, 02:19 PM UTC· resolved Mar 13, 2026, 04:40 PM UTC

1. investigating Mar 13, 2026, 02:19 PM UTC

   We are currently investigating reports that users are unable to login using Slack.

2. identified Mar 13, 2026, 02:53 PM UTC

   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.

3. monitoring Mar 13, 2026, 03:54 PM UTC

   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.

4. resolved Mar 13, 2026, 04:40 PM UTC

   Slack have confirmed that the issue has been fully resolved, and affected customers have verified that they can log in successfully.

Read the full incident report →

Started Mar 12, 2026, 01:20 PM UTC· resolved Mar 12, 2026, 02:27 PM UTC

1. identified Mar 12, 2026, 01:20 PM UTC

   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.

2. resolved Mar 12, 2026, 02:27 PM UTC

   Traffic appears to be back to normal levels now.

Read the full incident report →

Started Feb 02, 2026, 11:16 AM UTC· resolved Feb 02, 2026, 04:55 PM UTC

1. identified Feb 02, 2026, 11:16 AM UTC

   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.

2. monitoring Feb 02, 2026, 11:37 AM UTC

   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.

3. monitoring Feb 02, 2026, 12:30 PM UTC

   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. "incident.io.": http://incident.io./ We'll continue to monitor this until the issue is resolved.

4. monitoring Feb 02, 2026, 01:30 PM UTC

   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. "incident.io.": http://incident.io./ We'll continue to monitor this until the issue is resolved.

5. monitoring Feb 02, 2026, 02:37 PM UTC

   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. "incident.io.": http://incident.io./ We'll continue to monitor this and give an update in the next hour.

6. monitoring Feb 02, 2026, 03:41 PM UTC

   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. "incident.io.": http://incident.io./ We'll continue to monitor this and give an update in the next hour.

7. monitoring Feb 02, 2026, 04:06 PM UTC

   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. "incident.io.": http://incident.io./ We continue to monitor the issue until it is resolved.

8. resolved Feb 02, 2026, 04:56 PM UTC

   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.

Read the full incident report →

Started Jan 12, 2026, 03:36 PM UTC· resolved Jan 12, 2026, 03:59 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Dec 22, 2025, 10:29 AM UTC· resolved Dec 22, 2025, 01:57 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Dec 15, 2025, 10:31 AM UTC· resolved Dec 15, 2025, 02:41 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Dec 05, 2025, 09:07 AM UTC· resolved Dec 05, 2025, 09:30 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Nov 29, 2025, 11:33 AM UTC· resolved Nov 29, 2025, 03:20 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Nov 20, 2025, 11:47 AM UTC· resolved Nov 20, 2025, 12:14 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Nov 18, 2025, 12:18 PM UTC· resolved Nov 18, 2025, 03:58 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →