Is there an Atlassian Support outage?
Atlassian Support status: Systems Active
Last checked: 4 minutes ago
Get notified about any outages, downtime or incidents for Atlassian Support and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 4 minutes ago
Get notified about any outages, downtime or incidents for Atlassian Support and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Atlassian Support.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| API Docs | Active |
| Blogs | Active |
| Careers | Active |
| Community | Active |
| Content Delivery | Active |
| Downloads Access | Active |
| Knowledge Base | Active |
| Preferences Center | Active |
| Public Issues Tracker | Active |
| Search | Active |
| Support Portal | Active |
| Ticketing | Active |
| Training | Active |
View the latest incidents for Atlassian Support and check for official updates:
Description: GSAC tickets are getting created post LD update LD has posted an update https://status.launchdarkly.com/incidents/br3ssf4zl33c that they have recovered.
Status: Resolved
Impact: Major | Started At: July 5, 2022, 8:08 p.m.
Description: ### **SUMMARY** On March 28, 2022 between 3:18 pm and 5:24 pm UTC, Atlassian customers using the Support Ticket Portal were unable to login to view support tickets. The event was triggered by a configuration change. The incident was detected within 60 minutes by staff and mitigated by restoring data from a database snapshot which put Atlassian systems into a known good state. The total time to resolution was about 2 hours & 6 minutes. ### **IMPACT** The overall impact was between March 28, 2022 between 3:18 pm UTC and March 28, 2022 5:24 pm UTC _affecting the Support Ticket Portal. The incident caused service disruption to customers trying to view support tickets. Customers were still able to respond to support issues through email. The outage only impacted customers trying to access_ [_getsupport.atlassian.com_](http://getsupport.atlassian.com) ### **ROOT CAUSE** The issue was caused by a change to [_getsupport.atlassian.com_](http://getsupport.atlassian.com/). As a result, the support system above could not authenticate new user sessions, and the users received an error when trying to login. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. We are prioritizing the following improvement actions to avoid repeating this type of incident: * Improve logging and alerting to detect improper configuration changes sooner. * Improve rollout procedures for configuration changes. 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
Status: Postmortem
Impact: Major | Started At: March 28, 2022, 4:26 p.m.
Description: ### **SUMMARY** On March 14, 2022, between 01:05pm and 01:47pm UTC, some Atlassian customers were unable to login to our products including Trello and Statuspage, and could not access some services including the ability to create support tickets. The underlying cause was a newly introduced configuration data store that did not scale up properly due to a misconfiguration of autoscaling. The incident was detected by Atlassian's automated monitoring system and mitigated by disabling the use of the new configuration datastore which put our systems into a known good state. The total time to resolution was approximately 42 minutes. ### **IMPACT** The overall impact was between March 14 2022, 01:05 PM UTC and March 14, 2022, 01:47 PM UTC across seven products and services. The bug impacted several of the key dependent services which resulted in an outage for end users, leading to failed logins across the following products and services: * **getsupport.atlassian.com** * **confluence.atlassian.com** * **jira.atlassian.com** * **partners-jira.atlassian.com** * **community.atlassian.com** * **manage.statuspage.io** * **trello.com** * **university.atlassian.com** ### **ROOT CAUSE** The issue was caused by an underlying configuration data store based on AWS DynamoDB failing to scale up. During post-setup fine-tuning it was identified that initial values for the read capacity units \(RCUs\) and write capacity units \(RCUs\) were over-provisioned. As a result a decision was made to decrease them however the resulting values proved to be insufficient to handle the increased traffic in our system. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We're prioritizing the following improvement actions to avoid repeating this type of incident: * Fix the configuration so that the new configuration data store dynamically scales-up regardless of the size of the incoming traffic. * Conduct more thorough capacity planning and load testing. * Improve the resilience of the system by adding fallbacks to our secondary data store. 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
Status: Postmortem
Impact: Major | Started At: March 14, 2022, 1 p.m.
Description: The issue has been resolved and the service is now operating normally.
Status: Resolved
Impact: Critical | Started At: Aug. 31, 2021, 6:12 p.m.
Description: Resolved - Between 1:57 to 16:25 UTC, we experienced an outage impacting our support portal. During this time customers were not able to submit support cases through normal channels. The issue has been resolved and the service is operating normally.
Status: Resolved
Impact: Major | Started At: May 10, 2021, 1:57 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
