Resolved after 5 hours 39 minutes, affecting Atlassian Statuspage, on February 2, 2026.
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.
Affected components
Update timeline
- identified Feb 02, 2026, 11:16 AM UTC
We have identified increased error rates with our Atlassian Statuspage integration. Atlassian have acknowledged an issue on their side (https://metastatuspage.com/incidents/ctw5xv6t643h). We'll continue to monitor this until the issue is resolved.
- monitoring Feb 02, 2026, 11:37 AM UTC
Atlassian's status page continues to show the issue with Statuspage (https://metastatuspage.com/incidents/ctw5xv6t643h). 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.
- monitoring Feb 02, 2026, 12:30 PM UTC
Atlassian's status page continues to show the issue with Statuspage (https://metastatuspage.com/incidents/ctw5xv6t643h). To restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in incident.io. "incident.io.": http://incident.io./ We'll continue to monitor this until the issue is resolved.
- monitoring Feb 02, 2026, 01:30 PM UTC
Atlassian's status page continues to show the issue with Statuspage (https://metastatuspage.com/incidents/ctw5xv6t643h). To restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in incident.io. "incident.io.": http://incident.io./ We'll continue to monitor this until the issue is resolved.
- monitoring Feb 02, 2026, 02:37 PM UTC
Atlassian's status page continues to show the issue with Statuspage (https://metastatuspage.com/incidents/ctw5xv6t643h). To restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in incident.io. "incident.io.": http://incident.io./ We'll continue to monitor this and give an update in the next hour.
- monitoring Feb 02, 2026, 03:41 PM UTC
Atlassian's status page continues to show the issue with Statuspage (https://metastatuspage.com/incidents/ctw5xv6t643h). To restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in incident.io. "incident.io.": http://incident.io./ We'll continue to monitor this and give an update in the next hour.
- monitoring Feb 02, 2026, 04:06 PM UTC
Atlassian's status page now reports that they are rolling out a fix (https://metastatuspage.com/incidents/ctw5xv6t643h). In the meantime, to restore the integration you can follow Atlassian's recommended workaround to regenerate your API key and reconnect in incident.io. "incident.io.": http://incident.io./ We continue to monitor the issue until it is resolved.
- resolved Feb 02, 2026, 04:56 PM UTC
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.
Your product runs on more than incident.io
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.