- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Atlassian Statuspage. 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 0m it lasted.
Anything that failed between 2025-10-29 10:37 UTC and 2025-10-29 10:00 UTC may need a replay.Subscribe to Atlassian Statuspage's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=statuspage works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Atlassian Statuspage 1
- resolved
On October 29th, between 9:50 UTC and 10:04 UTC, some Statuspage customers using custom domains may have experienced downtime. Once we identified the root cause of the issue, we took swift action to resolve it. We have verified that the service is now fully restored and operational. Our team is closely monitoring the situation to ensure continued stability. We will conduct an internal review of this incident and implement necessary improvements to our systems to prevent or reduce the likelihood of similar occurrences in the future.
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-a8179c02ad
Is Atlassian Statuspage still down?
No, this incident was resolved 2025-10-29 10:00 UTC. For Atlassian Statuspage's live state, see https://down.guide/statuspage.
How long did it last?
0m, from 2025-10-29 10:37 UTC to 2025-10-29 10:00 UTC, by the times Atlassian Statuspage posted.
What caused it?
Atlassian Statuspage hasn't published a root cause. If it does, it shows here.
Where does this come from?
Atlassian Statuspage's official status page, https://metastatuspage.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.