- 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 2023-02-21 18:00 UTC and 2023-02-21 18: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
We experienced a delay in delivery of notifications of incidents for a period of 15 minutes which has been resolved. We have identified the cause of this is an ongoing incident with one of our messaging vendors, and we have migrated all possible notification traffic to our alternate messaging vendors.
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-1f0e728e95
Is Atlassian Statuspage still down?
No, this incident was resolved 2023-02-21 18:00 UTC. For Atlassian Statuspage's live state, see https://down.guide/statuspage.
How long did it last?
0m, from 2023-02-21 18:00 UTC to 2023-02-21 18: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.