incident.io Outage History
27 incidents recorded over the last 365 days, 27 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded incident.io Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 2, 2026 | Sentry integration degradedWe'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… | 1h 56m | Resolved |
| Oct 2, 2026 | Login errors for subset of Slack Enterprise Grid customersThis incident has been resolved. Login via Slack is operating normally again, and no further action is required. | 1h 13m | Resolved |
| Aug 20, 2026 | Increased latency in Microsoft TeamsLatency 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… | 1h 48m | Resolved |
| Aug 18, 2026 | Issue with listing alerts in the public API and dashboardWe've now rolled back and listing alerts is working normally again. | -138 min | Resolved |
| Aug 3, 2026 | Delays in webhooks from OpsgenieOpsgenie webhook delivery returned to normal at around 17:48 BST | 1h 7m | Resolved |
| Aug 1, 2026 | AI features degradedBetween around 00:00 and 02:44 UTC, some AI features returned increased error rates. We are now seeing full recovery. | -1 min | Resolved |
| Jul 16, 2026 | Issues affecting login with SAMLSAML login has continued to perform as normal. | 2h 22m | Resolved |
| Jun 23, 2026 | Intermittent dashboard errorsWe 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… | 40 min | Resolved |
| May 27, 2026 | Issue with Slack integrationSlack 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… | 7h 47m | Resolved |
| May 14, 2026 | Issue with Slack integrationThe issue has been resolved on Slack's side and we've confirmed that things look normal on our side too. | 1h 37m | Resolved |
| May 7, 2026 | Web dashboard unavailableThe website is now up and working as normal. | -12 min | Resolved |
| Apr 27, 2026 | Delays in webhooks from OpsgenieWebhooks appear to arriving as normal again, so you should no longer see any delays. | 15 min | Resolved |
| Apr 9, 2026 | Intermittent errors posting to Atlassian StatuspagesError rates have returned to normal levels. | 21 min | Resolved |
| Mar 24, 2026 | Increased error rates from Microsoft TeamsWe are no longer seeing elevated latency and error rates from Microsoft Teams. | 4h 22m | Resolved |
| Mar 24, 2026 | Scribe performance degradedWe continue to use the failover region, and Scribe performance has returned to expected levels. | 1h 31m | Resolved |
| Mar 13, 2026 | Some users unable to sign in via SlackSlack have confirmed that the issue has been fully resolved, and affected customers have verified that they can log in successfully. | 2h 21m | Resolved |
| Mar 12, 2026 | Opsgenie integration performance is degradedTraffic appears to be back to normal levels now. | 1h 6m | Resolved |
| Feb 2, 2026 | Atlassian Statuspage integration degradedAtlassian have confirmed that the issues with Statuspage have been resolved. You should now be able to reuse your original API key in our integration. | 5h 39m | Resolved |
| Jan 12, 2026 | Sentry integration degradedWe've not seen any errors from Sentry since 15:35 UTC so we're closing this out. Please see Sentry's status page for any further details. | 23 min | Resolved |
| Dec 22, 2025 | Increased rate of disconnections from SentryWe have managed to re-establish a connection to Sentry for almost all of the affected customers. If Sentry is still showing up as disconnected, you will need to remove the incident.io integration from the Sentry side… | 3h 28m | Resolved |
| Dec 15, 2025 | Delayed insights dataThe team have resolved this issue, and Insights are now syncing as expected. | 4h 10m | Resolved |
| Dec 5, 2025 | Integration failures due to Cloudflare outage[Cloudflare have resolved](https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q) the incident. We've seen a recovery in system health - all integrations have returned to normal. | 23 min | Resolved |
| Nov 29, 2025 | Elevated error rate from SentrySentry has resolved the incident. | 3h 47m | Resolved |
| Nov 20, 2025 | Degraded performance with @incident chatWe have resolved the degraded performance affecting @incident chat. This issue was caused by an overload from one of our AI model providers, which led to intermittent errors when using AI actions such as generating… | 27 min | Resolved |
| Nov 18, 2025 | Minor impact from Cloudflare outageCloudflare have [confirmed](https://www.cloudflarestatus.com/incidents/8gmgl950y3h7) that majority of impact has now resolved, and we’ve seen no impact on our systems over the last hour. | 3h 40m | Resolved |
| Nov 14, 2025 | Web dashboard and API unavailableBetween 12:46 and 12:50 UTC, some requests to our web dashboard and API failed. Some interactions via Slack, Teams and the mobile app were also affected by this. Critical areas of our application were **unaffected**… | -97 min | Resolved |
| Nov 7, 2025 | Slack integration degraded performanceSlack have confirmed on their [status page](https://slack-status.com/2025-11-06) that the issue has been resolved, and we have confirmed that Slack errors and latency are back to expected levels. If you are still… | 5h 1m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next incident.io incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This incident.io Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before incident.io acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single incident.io outage in this window ran 7h 47m, against a mean recovery of 2h 25m. If you depend on incident.io in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.