- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 21of 100
What to do
Check whether your product depends on incident.io. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 5h 40m it lasted.
Anything that failed between 2026-02-02 11:16 UTC and 2026-02-02 16:56 UTC may need a replay.Subscribe to incident.io's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=incident-io works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from incident.io 8
- identified
We have identified increased error rates with our Atlassian Statuspage integration. Atlassian have acknowledged an issue on their side ( ). We'll continue to monitor this until the issue is resolved.
provider
- monitoring
Atlassian's status page continues to show the issue with Statuspage ( ). 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.
provider
- monitoring
Atlassian's status page continues to show the issue with Statuspage ( ). To restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in [incident.io.](http://incident.io./ "incident.io.") We'll continue to monitor this until the issue is resolved.
provider
- monitoring
Atlassian's status page continues to show the issue with Statuspage ( ). To restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in [incident.io.](http://incident.io./ "incident.io.") We'll continue to monitor this until the issue is resolved.
provider
- monitoring
Atlassian's status page continues to show the issue with Statuspage ( ). To restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in [incident.io.](http://incident.io./ "incident.io.") We'll continue to monitor this and give an update in the next hour.
provider
- monitoring
Atlassian's status page continues to show the issue with Statuspage ( ). To restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in [incident.io.](http://incident.io./ "incident.io.") We'll continue to monitor this and give an update in the next hour.
provider
- monitoring
Atlassian's status page now reports that they are rolling out a fix ( ). In the meantime, to restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in [incident.io.](http://incident.io./ "incident.io.") We continue to monitor the issue until it is resolved.
provider
- resolved
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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-270af437ce
Is incident.io still down?
No, this incident was resolved 2026-02-02 16:56 UTC. For incident.io's live state, see https://down.guide/incident-io.
How long did it last?
5h 40m, from 2026-02-02 11:16 UTC to 2026-02-02 16:56 UTC, by the times incident.io posted.
What caused it?
incident.io hasn't published a root cause. If it does, it shows here.
Where does this come from?
incident.io's official status page, https://status.incident.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.