incident.io Outage History

incident.io is up right now

Pingoru has recorded 37 incidents for incident.io: 33 in the last 12 months and 5 in the last 90 days.

Source: status.incident.io

37incidents recorded

33last 12 months

5last 90 days

3 hourstypical duration

Incidents per month

Share of hours with an open incident, any severity

Pingoru began tracking incident.io in April 2026, so earlier months are not shown. Hover a bar for its value.

Show as a table

Month	Incidents	Hours with an open incident
April 2026	3	1 of 720 (0%)
May 2026	4	10 of 744 (1%)
June 2026	1	40 of 720 (6%)
July 2026	1	2 of 744 (0%)
August 2026	4	6 of 744 (1%)
September 2026	0	0 of 720 (0%)
October 2026	1	1 of 577 (0%)

Incidents, newest first

Minor October 2, 2026 Login errors for subset of Slack Enterprise Grid customers 1h 13m Slack app

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

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.
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 →

Minor August 20, 2026 Increased latency in Microsoft Teams 1h 48m Microsoft Teams app

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

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.
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.
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 →

Minor August 18, 2026 Issue with listing alerts in the public API and dashboard 13m Alert ingestion, processing and paging

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

identified Aug 18, 2026, 11:24 AM UTC

We've identified an issue listing alerts. Regular alerting and paging is unaffected.
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 →

Minor August 3, 2026 Delays in webhooks from Opsgenie 1h 7m Opsgenie

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

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.
resolved Aug 03, 2026, 05:04 PM UTC

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

Read the full incident report →

Minor August 1, 2026 AI features degraded 2h 37m Confluence, Okta, Datadog, Vanta and 36 more

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

investigating Aug 01, 2026, 12:08 AM UTC

We detected increased error rates with some AI features.
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 →

Minor July 16, 2026 Issues affecting login with SAML 2h 22m SAML login

Started Jul 16, 2026, 08:32 AM UTC· resolved Jul 16, 2026, 10:54 AM UTC

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.
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.
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.
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.
monitoring Jul 16, 2026, 10:29 AM UTC

SAML logins are now performing as normal. We'll continue to monitor for any further issues.
resolved Jul 16, 2026, 10:54 AM UTC

SAML login has continued to perform as normal.

Read the full incident report →

Minor June 23, 2026 Intermittent dashboard errors 1d 16h Dashboard

Started Jun 23, 2026, 07:45 PM UTC· resolved Jun 25, 2026, 11:51 AM UTC

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.
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.
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.
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 →

Minor May 27, 2026 Issue with Slack integration 7h 47m Slack app

Started May 27, 2026, 10:42 PM UTC· resolved May 28, 2026, 06:29 AM UTC

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.
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.
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.
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.
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.
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 →

Major May 15, 2026 Delayed Slack messages 28m Slack, Slack app

Started May 15, 2026, 11:20 AM UTC· resolved May 15, 2026, 11:48 AM UTC

identified May 15, 2026, 11:20 AM UTC

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

Read the full incident report →

Minor May 7, 2026 Web dashboard unavailable 13m Confluence, Okta, Datadog, Vanta and 36 more

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

identified May 07, 2026, 07:12 AM UTC

The web dashboard is unavailable due to a JavaScript deployment issue.
resolved May 07, 2026, 07:25 AM UTC

The website is now up and working as normal.

Read the full incident report →

Minor April 9, 2026 Intermittent errors posting to Atlassian Statuspages 21m Atlassian Statuspage

Started Apr 09, 2026, 07:33 AM UTC· resolved Apr 09, 2026, 07:55 AM UTC

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.
resolved Apr 09, 2026, 07:55 AM UTC

Error rates have returned to normal levels.

Read the full incident report →

Minor March 24, 2026 Increased error rates from Microsoft Teams 4h 22m Microsoft Teams app

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

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.
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.
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.
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.
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 →

Minor March 24, 2026 Scribe performance degraded 1h 31m

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

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.
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.
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.
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 →

Minor March 13, 2026 Some users unable to sign in via Slack 2h 21m

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

investigating Mar 13, 2026, 02:19 PM UTC

We are currently investigating reports that users are unable to login using Slack.
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.
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.
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 →

Minor March 12, 2026 Opsgenie integration performance is degraded 1h 6m Opsgenie

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

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.
resolved Mar 12, 2026, 02:27 PM UTC

Traffic appears to be back to normal levels now.

Read the full incident report →

Minor February 2, 2026 Atlassian Statuspage integration degraded 5h 39m Atlassian Statuspage

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

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.
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.
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.
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.
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.
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.
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.
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.