Last checked: 4 minutes ago
Get notified about any outages, downtime or incidents for Jira Align and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Jira Align.
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 |
---|---|
AWS ec2-ap-southeast-2 | Active |
AWS ec2-eu-central-1 | Active |
AWS ec2-us-east-2 | Active |
AWS elb-ap-southeast-2 | Active |
AWS elb-eu-central-1 | Active |
AWS elb-us-east-2 | Active |
AWS glue-ap-southeast-2 | Active |
AWS glue-eu-central-1 | Active |
AWS glue-us-east-2 | Active |
AWS rds-ap-southeast-2 | Active |
AWS rds-eu-central-1 | Active |
AWS rds-us-east-2 | Active |
AWS ses-ap-southeast-2 | Active |
AWS ses-eu-central-1 | Active |
AWS ses-us-east-1 | Active |
Pod 1 | Active |
Pod 10 | Active |
Pod 11 | Active |
Pod 12 | Active |
Pod 13 | Active |
Pod 14 | Active |
Pod 15 | Active |
Pod 16 | Active |
Pod 17 | Active |
Pod 18 | Active |
Pod 19 | Active |
Pod 2 | Active |
Pod 20 | Active |
Pod 21 | Active |
Pod 22 | Active |
Pod 23 | Active |
Pod 24 | Active |
Pod 25 | Active |
Pod 26 | Active |
Pod 27 | Active |
Pod 28 | Active |
Pod 29 | Active |
Pod 3 | Active |
Pod 30 | Active |
Pod 31 | Active |
Pod 32 | Active |
Pod 33 | Active |
Pod 34 | Active |
Pod 35 | Active |
Pod 36 | Active |
Pod 37 | Active |
Pod 38 | Active |
Pod 39 | Active |
Pod 4 | Active |
Pod 40 | Active |
Pod 41 | Active |
Pod 42 | Active |
Pod 43 | Active |
Pod 44 | Active |
Pod 44 | Active |
Pod 45 | Active |
Pod 46 | Active |
Pod 47 | Active |
Pod 48 | Active |
Pod 49 | Active |
Pod 5 | Active |
Pod 6 | Active |
Pod 7 | Active |
Pod 8 | Active |
Pod 9 | Active |
View the latest incidents for Jira Align and check for official updates:
Description: Between 10:25 UTC to 11:25 UTC we experienced degraded functionality for Jira Align. The issue has been resolved and the service is operating normally.
Status: Resolved
Impact: None | Started At: Aug. 11, 2023, 11:39 a.m.
Description: We mitigated the issue with Sign-ups, Product Activation, and Billing, and the systems are back to BAU, and all functionality is restored.
Status: Resolved
Impact: None | Started At: Aug. 2, 2023, 1:41 p.m.
Description: We mitigated the issue with Sign-ups, Product Activation, and Billing, and the systems are back to BAU, and all functionality is restored.
Status: Resolved
Impact: None | Started At: Aug. 2, 2023, 1:41 p.m.
Description: ### **SUMMARY** We understand the importance of providing reliable and consistent service to our valued customers. On July 6, 2023, from 03:52 to 15:11 UTC, we experienced an issue with an upgraded version of a third-party tool that functions as our internal artifact management system. Despite our monitoring system identifying the incident within two minutes, this issue led to the degradation of the scaling capabilities of our internal hosting platform, resulting in service degradation or outages for customers of Atlassian cloud. In response to this situation, we are taking immediate measures to enhance the stability of our system and prevent similar issues from re-occurring. ### **IMPACT** This incident affected multiple regions and products due to the diminished scaling capabilities of our internal hosting platform. In most products and offerings, customers faced reduced functionality, slower response times, and limited access to specific features. ### **ROOT CAUSE** The root cause of the incident was the introduction of new functionality in a third-party tool that functions as our internal artifact management system. It led to an unexpected increase in the load on the primary database of the artifact system. Upon identifying and localizing the problem, we promptly adjusted the system configuration to regain stability. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** Over the next months, we will enact a temporary freeze on non-critical upgrades of the artifact management system, and we will focus our efforts on three high-priority initiatives: 1. **Enhancing system scaling:** We prioritized work ensuring that downtime in a critical infrastructure component does not affect the scaling of other components. We expect to complete this initiative within the next two months. 2. **Reducing interdependencies:** We are working to mitigate the risk of potential cascading failures by ensuring that significant system components are able to operate independently in the case of issues. Initiatives 1 and 2 are already in progress but have been given priority to be completed as soon as possible. 3. **Strengthening testing procedures:** Alongside these initiatives, we are addressing the need for even more stringent testing procedures than we already have in place to prevent potential issues in future updates. We are committed to collaborating closely with our technology partners to ensure the most optimal experience for our customers. We apologize for any inconvenience caused by this incident and appreciate your understanding. Our team is dedicated to continually improving our systems and processes to provide you with the exceptional service you deserve. Thank you for your continued support and trust in us. Sincerely, Atlassian Customer Support
Status: Postmortem
Impact: None | Started At: July 6, 2023, 11:18 a.m.
Description: ### **SUMMARY** We understand the importance of providing reliable and consistent service to our valued customers. On July 6, 2023, from 03:52 to 15:11 UTC, we experienced an issue with an upgraded version of a third-party tool that functions as our internal artifact management system. Despite our monitoring system identifying the incident within two minutes, this issue led to the degradation of the scaling capabilities of our internal hosting platform, resulting in service degradation or outages for customers of Atlassian cloud. In response to this situation, we are taking immediate measures to enhance the stability of our system and prevent similar issues from re-occurring. ### **IMPACT** This incident affected multiple regions and products due to the diminished scaling capabilities of our internal hosting platform. In most products and offerings, customers faced reduced functionality, slower response times, and limited access to specific features. ### **ROOT CAUSE** The root cause of the incident was the introduction of new functionality in a third-party tool that functions as our internal artifact management system. It led to an unexpected increase in the load on the primary database of the artifact system. Upon identifying and localizing the problem, we promptly adjusted the system configuration to regain stability. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** Over the next months, we will enact a temporary freeze on non-critical upgrades of the artifact management system, and we will focus our efforts on three high-priority initiatives: 1. **Enhancing system scaling:** We prioritized work ensuring that downtime in a critical infrastructure component does not affect the scaling of other components. We expect to complete this initiative within the next two months. 2. **Reducing interdependencies:** We are working to mitigate the risk of potential cascading failures by ensuring that significant system components are able to operate independently in the case of issues. Initiatives 1 and 2 are already in progress but have been given priority to be completed as soon as possible. 3. **Strengthening testing procedures:** Alongside these initiatives, we are addressing the need for even more stringent testing procedures than we already have in place to prevent potential issues in future updates. We are committed to collaborating closely with our technology partners to ensure the most optimal experience for our customers. We apologize for any inconvenience caused by this incident and appreciate your understanding. Our team is dedicated to continually improving our systems and processes to provide you with the exceptional service you deserve. Thank you for your continued support and trust in us. Sincerely, Atlassian Customer Support
Status: Postmortem
Impact: None | Started At: July 6, 2023, 11:18 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.