- Level
- confirmed
- Worst impact
- Partial outage
- Components
- HTTP Pages, HTTPS Pages, Public API
- Down Index
- 26of 100
What to do
Check whether you use Atlassian Statuspage HTTP Pages, HTTPS Pages, Public API. 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 25m it lasted.
Anything that failed between 2023-10-28 07:36 UTC and 2023-10-28 08:01 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 4
- investigating
We are currently seeing intermittent errors in viewing public Statuspages. We are investigating this problem and will provide updates shortly
provider
- monitoring
Update: We have fixed the issue and are monitoring actively
provider
- resolved
Issue is now resolved and everything is back to normal working state.
provider
- postmortem
### **SUMMARY** From 06:00 UTC to 07:45 UTC on October 28, 2023, Atlassian customers using Statuspage had intermittent issues with all Statuspage functionality. The event occurred due to a database performance issue during a [scheduled database maintenance](https://metastatuspage.com/incidents/s21b66328h9j). This impacted customers in all regions. The incident was detected within one minute by monitoring the upgrade process and mitigated by rolling back to a known good snapshot which put Statuspage systems into a known good state. The total time to resolution was about one hour and 45 minutes. ### **IMPACT** The overall impact was between 06:00 UTC and 07:45 UTC October 28, 2023. This incident affected Statuspage customers from all regions and caused intermittent backend errors on all Statuspage activity including viewing pages, adding subscribers, and creating/updating events. We performed a rollback operation during recovery to return to a known good state. ### **ROOT CAUSE** The issue was caused by database performance issues after a routine database maintenance and upgrade. As a result, our backends returned intermittent errors to several user requests. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We take the utmost care to provide a highly reliable service. We will pursue several preventive measures to ensure that this situation does not occur in the future, including: * Fixing the cause of the performance issues before future upgrades; and * Improving our testing process for database upgrades to catch potential performance issues. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support
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-7b1dc2b506
Is Atlassian Statuspage still down?
No, this incident was resolved 2023-10-28 08:01 UTC. For Atlassian Statuspage's live state, see https://down.guide/statuspage.
How long did it last?
25m, from 2023-10-28 07:36 UTC to 2023-10-28 08:01 UTC, by the times Atlassian Statuspage posted.
What was affected?
Atlassian Statuspage named HTTP Pages, HTTPS Pages, Public API.
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.