incident.io Outage History

incident.io is up right now

incident.io had 27 outages in the last 2 years totaling 24h 47m of downtime — averaging 1.1 incidents per month.

There were 27 incident.io outages since October 14, 2025 totaling 24h 47m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.incident.io

Minor August 20, 2026

Increased latency in Microsoft Teams

Detected by Pingoru
Aug 20, 2026, 04:31 PM UTC
Resolved
Aug 20, 2026, 04:31 PM UTC
Duration
—
Affected: Microsoft Teams app
Timeline · 3 updates
  1. identified Aug 20, 2026, 02:42 PM UTC

    Status: Identified 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. Affected components Microsoft Teams app (Degraded performance)

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

    Status: Identified 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. Affected components Microsoft Teams app (Degraded performance)

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

    Status: Resolved 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. Affected components Microsoft Teams app (Operational)

Read the full incident report →

Minor August 18, 2026

Issue with listing alerts in the public API and dashboard

Detected by Pingoru
Aug 18, 2026, 11:37 AM UTC
Resolved
Aug 18, 2026, 11:37 AM UTC
Duration
—
Affected: Alert ingestion, processing and paging
Timeline · 2 updates
  1. identified Aug 18, 2026, 11:24 AM UTC

    Status: Identified We've identified an issue listing alerts. Regular alerting and paging is unaffected. Affected components Alerts (Degraded performance)

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

    Status: Resolved We've now rolled back and listing alerts is working normally again. Affected components Alerts (Operational)

Read the full incident report →

Minor August 3, 2026

Delays in webhooks from Opsgenie

Detected by Pingoru
Aug 03, 2026, 05:04 PM UTC
Resolved
Aug 03, 2026, 05:04 PM UTC
Duration
—
Affected: Opsgenie
Timeline · 2 updates
  1. identified Aug 03, 2026, 03:56 PM UTC

    Status: Identified 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. Affected components Opsgenie (Degraded performance)

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

    Status: Resolved Opsgenie webhook delivery returned to normal at around 17:48 BST Affected components Opsgenie (Operational)

Read the full incident report →

Minor August 1, 2026

AI features degraded

Detected by Pingoru
Aug 01, 2026, 02:45 AM UTC
Resolved
Aug 01, 2026, 02:45 AM UTC
Duration
—
Affected: ConfluenceOktaDatadogVantaGoogle DocsPagerDutySMSAlert ingestion, processing and pagingPhoneSlackEmailAsanaAzure DevOpsClickUpGoogle CalendarGoogle MeetJiraLinearOpsLevelSentryShortcutZapierZendeskZoomStatus pagesWebsiteSAML loginPush notificationsOpsgenieDashboardAgentAPIMicrosoft Teams appInsightsMobile appSlack appCortexGitHubSplunkAtlassian Statuspage
Timeline · 2 updates

Read the full incident report →

Minor July 16, 2026

Issues affecting login with SAML

Detected by Pingoru
Jul 16, 2026, 10:54 AM UTC
Resolved
Jul 16, 2026, 10:54 AM UTC
Duration
—
Affected: SAML login
Timeline · 6 updates
  1. investigating Jul 16, 2026, 08:32 AM UTC

    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)

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

    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)

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

    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)

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

    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)

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

    Status: Monitoring SAML logins are now performing as normal. We'll continue to monitor for any further issues. Affected components SAML login (Operational)

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

    Status: Resolved SAML login has continued to perform as normal. Affected components SAML login (Operational)

Read the full incident report →

Minor June 25, 2026

Intermittent dashboard errors

Detected by Pingoru
Jun 25, 2026, 11:51 AM UTC
Resolved
Jun 25, 2026, 11:51 AM UTC
Duration
—
Affected: Dashboard
Timeline · 4 updates
  1. investigating Jun 23, 2026, 07:45 PM UTC

    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)

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

    Status: Monitoring Latency and error rates have returned to normal. We're continuing to monitor for any further issues. Affected components Dashboard (Operational)

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

    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)

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

    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)

Read the full incident report →

Minor May 28, 2026

Issue with Slack integration

Detected by Pingoru
May 28, 2026, 06:29 AM UTC
Resolved
May 28, 2026, 06:29 AM UTC
Duration
—
Affected: Slack app
Timeline · 6 updates
  1. identified May 27, 2026, 10:42 PM UTC

    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)

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

    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)

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

    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)

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

    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)

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

    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)

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

    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)

Read the full incident report →

Minor May 7, 2026

Web dashboard unavailable

Detected by Pingoru
May 07, 2026, 07:25 AM UTC
Resolved
May 07, 2026, 07:25 AM UTC
Duration
—
Affected: ConfluenceOktaDatadogVantaGoogle DocsPagerDutySMSAlert ingestion, processing and pagingPhoneSlackEmailAsanaAzure DevOpsClickUpGoogle CalendarGoogle MeetJiraLinearOpsLevelSentryShortcutZapierZendeskZoomStatus pagesWebsiteSAML loginPush notificationsOpsgenieDashboardAgentAPIMicrosoft Teams appInsightsMobile appSlack appCortexGitHubSplunkAtlassian Statuspage
Timeline · 2 updates

Read the full incident report →

Minor April 9, 2026

Intermittent errors posting to Atlassian Statuspages

Detected by Pingoru
Apr 09, 2026, 07:55 AM UTC
Resolved
Apr 09, 2026, 07:55 AM UTC
Duration
—
Affected: Atlassian Statuspage
Timeline · 2 updates
  1. identified Apr 09, 2026, 07:33 AM UTC

    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)

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

    Status: Resolved Error rates have returned to normal levels. Affected components Atlassian Statuspage (Operational)

Read the full incident report →

Minor March 24, 2026

Increased error rates from Microsoft Teams

Detected by Pingoru
Mar 24, 2026, 08:52 PM UTC
Resolved
Mar 24, 2026, 08:52 PM UTC
Duration
—
Affected: Microsoft Teams app
Timeline · 5 updates
  1. identified Mar 24, 2026, 04:30 PM UTC

    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)

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

    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)

  3. monitoring Mar 24, 2026, 06:33 PM UTC

    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)

  4. monitoring Mar 24, 2026, 07:30 PM UTC

    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)

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

    Status: Resolved We are no longer seeing elevated latency and error rates from Microsoft Teams. Affected components Microsoft Teams app (Operational)

Read the full incident report →

Minor March 24, 2026

Scribe performance degraded

Detected by Pingoru
Mar 24, 2026, 05:02 PM UTC
Resolved
Mar 24, 2026, 05:02 PM UTC
Duration
—
Timeline · 4 updates
  1. identified Mar 24, 2026, 03:31 PM UTC

    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.

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

    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.

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

    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.

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

    Status: Resolved 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

Detected by Pingoru
Mar 13, 2026, 04:40 PM UTC
Resolved
Mar 13, 2026, 04:40 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Mar 13, 2026, 02:19 PM UTC

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

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

    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.

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

    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.

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

    Status: Resolved 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

Detected by Pingoru
Mar 12, 2026, 02:27 PM UTC
Resolved
Mar 12, 2026, 02:27 PM UTC
Duration
—
Affected: Opsgenie
Timeline · 2 updates
  1. identified Mar 12, 2026, 01:20 PM UTC

    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)

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

    Status: Resolved Traffic appears to be back to normal levels now. Affected components Opsgenie (Operational)

Read the full incident report →