# Atlassian Statuspage integration degraded

- Provider: [incident.io](https://down.guide/incident-io)
- Level: confirmed
- Impact: Degraded
- lasted 5h 40m
- started 2026-02-02 11:16 UTC
- id: DWN-270af437ce
- Official page: https://status.incident.io/incidents/01KGF13N88J78TFTW67BHP93TQ

## Updates from incident.io
### 2026-02-02 11:16 UTC: 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.

### 2026-02-02 11:37 UTC: 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.

### 2026-02-02 12:30 UTC: 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.

### 2026-02-02 13:30 UTC: 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.

### 2026-02-02 14:37 UTC: 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.

### 2026-02-02 15:41 UTC: 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.

### 2026-02-02 16:06 UTC: 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.

### 2026-02-02 16:56 UTC: 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.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).