Is there an Jira Align outage?
Jira Align status: Systems Active
Last checked: 9 minutes ago
Get notified about any outages, downtime or incidents for Jira Align and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 9 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 28th Feb 2024 23:15 UTC to 29th Feb 2024 00:05 UTC, we experienced issue with new product purchasing for all products. All new sign up products have been successfully provision and confirmed issue has been resolved and the service is operating normally.
Status: Resolved
Impact: None | Started At: Feb. 29, 2024, 1:27 a.m.
Description: ### **Summary** On February 14, 2024, between 20:05 UTC and 23:03 UTC, Atlassian customers on the following cloud products encountered a service disruption: Access, Atlas, Atlassian Analytics, Bitbucket, Compass, Confluence, Ecosystem apps, Jira Service Management, Jira Software, Jira Work Management, Jira Product Discovery, Opsgenie, StatusPage, and Trello. As part of a security and compliance uplift, we had scheduled the deletion of unused and legacy domain names used for internal service-to-service connections. Active domain names were incorrectly deleted during this event. This impacted all cloud customers across all regions. The issue was identified and resolved through the rollback of the faulty deployment to restore the domain names and Atlassian systems to a stable state. The time to resolution was two hours and 58 minutes. ### **IMPACT** External customers started reporting issues with Atlassian cloud products at 20:52 UTC. The impact of the failed change led to performance degradation or in some cases, complete service disruption. Symptoms experienced by end-users were unsuccessful page loads and/or failed interactions with our cloud products. ### **ROOT CAUSE** As part of a security and compliance uplift, we had scheduled the deletion of unused and legacy domain names that were being used for internal service-to-service connections. Active domain names were incorrectly deleted during this operation. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. The detection was delayed because existing testing & monitoring focused on service health rather than the entire system’s availability. To prevent a recurrence of this type of incident, we are implementing the following improvement measures: * Canary checks to monitor the entire system availability. * Faster rollback procedures for this type of service impact. * Stricter change control procedures for infrastructure modifications. * Migration of all DNS records to centralised management and stricter access controls on modification to DNS records. 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: None | Started At: Feb. 14, 2024, 9:57 p.m.
Description: ### **Summary** On February 14, 2024, between 20:05 UTC and 23:03 UTC, Atlassian customers on the following cloud products encountered a service disruption: Access, Atlas, Atlassian Analytics, Bitbucket, Compass, Confluence, Ecosystem apps, Jira Service Management, Jira Software, Jira Work Management, Jira Product Discovery, Opsgenie, StatusPage, and Trello. As part of a security and compliance uplift, we had scheduled the deletion of unused and legacy domain names used for internal service-to-service connections. Active domain names were incorrectly deleted during this event. This impacted all cloud customers across all regions. The issue was identified and resolved through the rollback of the faulty deployment to restore the domain names and Atlassian systems to a stable state. The time to resolution was two hours and 58 minutes. ### **IMPACT** External customers started reporting issues with Atlassian cloud products at 20:52 UTC. The impact of the failed change led to performance degradation or in some cases, complete service disruption. Symptoms experienced by end-users were unsuccessful page loads and/or failed interactions with our cloud products. ### **ROOT CAUSE** As part of a security and compliance uplift, we had scheduled the deletion of unused and legacy domain names that were being used for internal service-to-service connections. Active domain names were incorrectly deleted during this operation. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. The detection was delayed because existing testing & monitoring focused on service health rather than the entire system’s availability. To prevent a recurrence of this type of incident, we are implementing the following improvement measures: * Canary checks to monitor the entire system availability. * Faster rollback procedures for this type of service impact. * Stricter change control procedures for infrastructure modifications. * Migration of all DNS records to centralised management and stricter access controls on modification to DNS records. 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: None | Started At: Feb. 14, 2024, 9:57 p.m.
Description: It has been resolved. Atlassian's cross product user search is working.
Status: Resolved
Impact: None | Started At: Dec. 18, 2023, 3:04 p.m.
Description: Between 12:45 UTC to 15:30 UTC, we experienced login and signup issues for Atlassian Accounts. The issue has been resolved and the service is operating normally. We will publish a post-incident review with the details of the incident and the actions we are taking to prevent similar problem in the future.
Status: Resolved
Impact: None | Started At: Sept. 13, 2023, 2:08 p.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.
