Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Jan 4, 2024

  1. incident.ioincident.io is unavailable

    Between 10:43 and 10:46 GMT our app was unavailable. This will have meant both the web UI and Slack app were unusable. Sorry for any inconvenience this caused.

    Resolved

  2. incident.ioSlack app is failing

    Final update to say Slack officially closed their incident at 7:24 PM GMT, while we saw our last errors at 3:45 PM GMT. We don't expect any further interruption to incident.io products as a result of this incident.

    Resolved

  3. incident.ioApplication outage

    Our API, dashboard, Slack app and any background services have experienced an outage. This incident is being logged retrospectively, as we are now back to full service.

    Resolved

  4. incident.ioInsights are unavailable

    The upstream service we use for data visualisations has now resolved their issue, and insights are available once again.

    Resolved

  5. incident.ioWe're seeing intermittent issues with our app

    We’ve shared a technical write-up about the causes of this incident and steps we’ve taken to improve reliability here: [https://incident.io/blog/intermittent-downtime](https://incident.io/blog/intermittent-downtime)

    Resolved

  6. incident.ioElevated Platform Errors

    We were seeing infrequent bursts of errors due to running out of resources when talking with our database. This is now resolved, with the team having increased our capacity to handle these requests. We've also made changes to improve the performance of the feature that created this pressure, and don't expect the problem to reoccur.

    Resolved

  7. incident.ioDelayed updating of escalation status when using PagerDuty

    We're no longer seeing errors from the PagerDuty endpoint and have confirmed escalations are polling successfully, meaning escalation messages (created in response to `/inc escalate`) are working once more. We've followed up with PagerDuty to understand what caused this, and improved our retrying logic to make us more robust to future flakiness.

    Resolved

  8. incident.ioApp is unavailable due to Slack downtime

    We're no longer seeing any issues when making requests to Slack. From our logs, we see a period of time between 9:55-10:05am BST during which requests to Slack were failing and we received no webhooks. We expect the incident.io app was functional outside this period, and it appears Slack have now fixed the issue on their side so don't expect this to reoccur.

    Resolved

  9. incident.ioIssues with our app

    We've identified the cause of the issue and have deployed a change that ensures the dashboard now loads correctly. We do not expect any further disruption.

    Resolved

  10. incident.ioConnectivity issues with Atlassian Cloud

    We’ve now contacted everyone we believe were affected by this incident. If you’re still having connection issues with Atlassian integrations, you can reconnect by visiting Settings > Integrations (https://app.incident.io/~/settings/integrations) and following the instructions. If you require further support, please get in touch via https://help.incident.io/

    Resolved

  11. incident.ioIssues with Slack

    Slack has been stable for a while now, so we're resolving this incident. If you have any questions, or you are still seeing issues, please get in touch.

    Resolved

  12. incident.ioOur app is partially degraded

    We are confident that this issue is now resolved. Our app was in a degraded state between 13:38 and 13:52. During this time, the following product areas were affected: * Workflows did not run * Incidents were not auto-created from external sources * Incidents weren’t announced through Slack * Slack messages from our incident.io bot were not posted * Postmortem exports failed Workflows, incident autocreation, and Slack messages will now have processed in the background, so you do not need to retry these actions. During this time, the Slack app and the dashboard were both working as expected.

    Resolved

Jan 2, 2024

Jan 1, 2024

  1. KeeperVault login errors (Resolved)

    AWS RDS cluster instances were automatically rebooted at approximately 09:27 Central (04:27 UTC). We are investigating the issue with the AWS team and will update our statuspage with the findings.

    Resolved

Dec 31, 2023

Older incidents