incident.io Outage History

incident.io is up right now

There were 6 incident.io outages since March 12, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.incident.io

Minor April 28, 2026

Delays in webhooks from Opsgenie

Detected by Pingoru
Apr 28, 2026, 12:14 AM UTC
Resolved
Apr 28, 2026, 12:14 AM UTC
Duration
—
Affected: Opsgenie
Timeline · 2 updates
  1. monitoring Apr 27, 2026, 11:58 PM UTC

    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)

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

    Status: Resolved Webhooks appear to arriving as normal again, so you should no longer see any delays. Affected components Opsgenie (Operational)

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 →

Looking to track incident.io downtime and outages?

Pingoru polls incident.io's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when incident.io reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track incident.io alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring incident.io for free

5 free monitors · No credit card required