incident.io incident

Atlassian Statuspage integration degraded

Minor Resolved View vendor source →

incident.io experienced a minor incident on February 2, 2026 affecting Atlassian Statuspage, lasting —. The incident has been resolved; the full update timeline is below.

Started
Feb 02, 2026, 04:56 PM UTC
Resolved
Feb 02, 2026, 04:56 PM UTC
Duration
Detected by Pingoru
Feb 02, 2026, 04:56 PM UTC

Affected components

Atlassian Statuspage

Update timeline

  1. identified Feb 02, 2026, 11:16 AM UTC

    Status: Identified 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. Affected components Atlassian Statuspage (Degraded performance)

  2. monitoring Feb 02, 2026, 11:37 AM UTC

    Status: Monitoring 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. Affected components Atlassian Statuspage (Degraded performance)

  3. monitoring Feb 02, 2026, 12:30 PM UTC

    Status: Monitoring 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. Affected components Atlassian Statuspage (Degraded performance)

  4. monitoring Feb 02, 2026, 01:30 PM UTC

    Status: Monitoring 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. Affected components Atlassian Statuspage (Degraded performance)

  5. monitoring Feb 02, 2026, 02:37 PM UTC

    Status: Monitoring 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. Affected components Atlassian Statuspage (Degraded performance)

  6. monitoring Feb 02, 2026, 03:41 PM UTC

    Status: Monitoring 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. Affected components Atlassian Statuspage (Degraded performance)

  7. monitoring Feb 02, 2026, 04:06 PM UTC

    Status: Monitoring 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. Affected components Atlassian Statuspage (Degraded performance)

  8. resolved Feb 02, 2026, 04:56 PM UTC

    Status: 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. Affected components Atlassian Statuspage (Operational)