Is Jira Align Down Right Now? Check if there is a current outage ongoing.

We were experiencing cases of degraded performance for outgoing emails from Confluence, Jira Work Management, Jira Service Management, Jira, Opsgenie, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas, Compass, and Loom Cloud customers. The system is recovering and mail is being processed normally as of 16:45 UTC. We will continue to monitor system performance and will provide more details within the next hour.

This incident has been resolved.

The database has been restored. We are monitoring the site to ensure there are no further connectivity issues. We have confirmed no data was lost during this outage.

RDS is currently experiencing an issue that has caused an outage in the production environment. AWS is investigating. In the meantime w will perform a database restore.

RDS is currently experiencing an issue that has caused an outage in the production environment. AWS is investigating. In the meantime w will perform a database restore.

The issue has been resolved, service has been returned to operational status.

Jira Align was experiencing intermittent issues across multiple sites between 19:30 UTC and 22:12 UTC. The issue is resolved and the service is operating normally. If you continue to experience issues, please clear your browser cache and restart all open browser windows.

Jira Align was experiencing intermittent issues across multiple sites between 19:30 UTC and 22:12 UTC. The issue is resolved and the service is operating normally. If you continue to experience issues, please clear your browser cache and restart all open browser windows.

This incident has been resolved.

The issue has been mitigated, service has been returned to operational status. If you continue to experience issues, clear cache and restart all open browser windows.

We have been able to reproduce the issue and are investigating the root cause.

For customers experiencing issues, incognito mode in your browser can be used as a work around.

Jira Align is experiencing intermittent outages across multiple sites. The team is currently investigating.

Jira Align is experiencing intermittent outages across multiple sites. The team is currently investigating.

This incident is resolved. Remaining sites have all been successfully updated with the fix.

A fix has been implemented to some sites. Based upon feedback throughout today, we will finalize the deployment to the remaining sites.

The issue has been identified and a fix is being implemented.

The following reports open with a blank page due to recent Internet browser updates: ART Allocation Action Items Report Cumulative Effort Dependency Maps Feature Audit Report Feature Forecast - Average Velocity Investment by Feature Points Accepted (by Sprint) Process Flow Cycle Time Program Increment Cleanup Report Program Increment Scope Change Program Increments BurnUp Program Predictability Report Progress By Objective Resource Allocation Retrospective Risk and Impediment Status Sprint Metrics (M1) Sprint Synchronization Standup Attendance Story Audit Report Story Link Report Team Details Team Velocity Theme Rank Velocity by Team (Program Increment) WIP by State

This incident has been resolved.

Connector syncs are re-enabled and we are monitoring a return to standard performance.

Possible performance degradation since 11/18/24 11:00:00 PM PST. Connector syncs are temporarily paused.

Between 22-Oct 09:00 AM UTC to 22-Oct 14:18 PM UTC, we experienced intermittent errors for Jira Cloud products. The issue has been resolved and the service is operating normally.

We continue to work on resolving the intermittent errors for Jira Cloud products. We have identified the root cause and expect full recovery shortly.

We are investigating reports of intermittent 'Too many requests or errors' messages showing up for some Jira Cloud customers. Once we identify the root cause, we will provide more details.

We experienced availability issues limited to a specific instance in AMER, resulting in Jira being temporarily unavailable. The issue began at 18:58 CET and was restored at 19:59 CET. All services are now fully operational

All customer databases in US Central are fully operational. Standard monitoring activities will resume.

We are continuing to monitor for any further issues.

A fix has been implemented by Azure, all internal dashboards are showing promising results and we are monitoring progress.

Azure team has identified the problem and has been working to restore service.

Enterprise Insights instances in US Central are impacted due to an Azure active incident. Teams are following the incident closely and taking the appropriate actions.

Between 03-07-2024 20:08 UTC to 03-07-2024 20:31 UTC, we experienced downtime for Jira Align. The issue has been resolved and the service is operating normally.

We have mitigated the problem and continue looking into the root cause. The outage was between 8:08pm 03/07 UTC - 08:31pm 03/07 UTC We are now monitoring closely.

We are investigating an issue with <FUNCTIONALITY IMPACTED> that is impacting <SOME/ALL> Atlassian, Atlassian Partners, Atlassian Support, Confluence, Jira Work Management, Jira Service Management, Jira, Opsgenie, Atlassian Developer, Atlassian (deprecated), Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas, Atlassian Analytics, and Rovo Cloud customers. We will provide more details within the next hour.

Between 6:30 AM UTC to 9:50 AM UTC, we experienced failures in accessing some features from the Admin Portal. The issue has been resolved, and the service is operating normally.

We are investigating an issue causing failures in accessing some features from the Admin Portal, which is impacting some of our Cloud customers. We have identified the root cause and anticipate recovery shortly.

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.

We are investigating an issue with new product purchasing that is impacting for all products. Customers adding new cloud products may have experienced a long waiting page or an error page after attempting to add a product. We have mitigated the root cause and are working to resolve impact for customers who attempted to add a product during the impact period. We will provide more details within the next hour.

### **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

We experienced increased errors on Confluence, Jira Work Management, Jira Service Management, Jira Software, Opsgenie, Trello, Atlassian Bitbucket, Atlassian Access, Jira Align, Jira Product Discovery, Atlas, Compass, and Atlassian Analytics. The issue has been resolved and the services are operating normally.

We have identified the root cause of the Service Disruptions affecting all Atlassian products and have mitigated the problem. We are now monitoring this closely.

We have identified the root cause of the increased errors and have mitigated the problem. We continue to work on resolving the issue and monitoring this closely.

We are investigating reports of intermittent errors for all Cloud Customers across all Atlassian products. We will provide more details once we identify the root cause.

It has been resolved. Atlassian's cross product user search is working.

Atlassian's cross product user search service is currently healthy. Searches for users within Atlassian products are working as expected. We are in the process of investigating the root cause of this incident.

Atlassian's cross product user search service is recovering. Searches for users within Atlassian products are returning to normal.

Atlassian's cross product user search service is recovering. Searches for users within Atlassian products are returning to normal.

Atlassian's cross product user search service is recovering. Searches for users within Atlassian products are returning to normal.

We are investigating reports of intermittent errors for <SOME/ALL> Atlassian, Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, Jira Align, Jira Product Discovery, Atlas, and Compass Cloud customers. We will provide more details once we identify the root cause.

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.

We are no longer seeing occurrences of the Atlassian Accounts login errors, all clients should be able to successfully login now. We will continue to monitor.

We can see a reduction in the Atlassian Accounts login issues after the mitigation actions were taken. We are still monitoring closely and will continue to provide updates.

We have identified the root cause of the Atlassian Accounts login issues impacting Cloud Customers and have mitigated the problem. We are now monitoring this closely.

We are investigating an issue with Atlassian Accounts login that is impacting some Cloud customers. We will provide more details within the next hour.

Between 08:50 UTC to 21:24 UTC, we experienced Enterprise Insights service unavailability for APAC region. The issue has now been resolved and the service is operating normally.

Fixed. Monitoring. We have fixed Enterprise Insights services and have mitigated the problem. We are now monitoring closely.

We continue to work on restoring Enterprise Insights services in partnership with our cloud provider. We have identified the root cause and are working to resolve it as quickly as possible. We will provide more details in one hour.

The hardware has been restored and services are slowly coming back online

Beginning at 08:30 UTC on 30-August the Enterprise Insights servers in the APAC regions were unavailable

We have resolved a case of degraded performance for Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, Atlassian Access, Jira Align, Jira Product Discovery, Atlas, and Compass Cloud customers. We will provide more details within the next hour.

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.

We are investigating reports of intermittent errors for some Jira Align Cloud customers. We will provide more details once we identify the root cause.

We mitigated the issue with Sign-ups, Product Activation, and Billing, and the systems are back to BAU, and all functionality is restored.

We have identified the root cause of the Sign-ups, Product Activation, and Billing not working and have mitigated the problem. We are now monitoring closely.

We are investigating an issue with Sign-ups, Product Activation, and Billing that is impacting all of our Cloud Customers. We will provide more details within the next hour.

### **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

We experienced performance issues and outages for several Atlassian Cloud Products. The issue has been resolved and the service is operating normally.

We have identified the root cause of an issue with an internal infrastructure component that has been impacting multiple Cloud products, including Jira Software, Jira Service Management and Confluence, and customers. This issue had lead to a performance impact and, in some cases, outages. We have implemented a fix to resolve the issue and recovery is in progress.

We are investigating an issue with an internal infrastructure component that is impacting multiple Cloud products, including Jira Software, Bitbucket, Jira Service Management and Confluence, and customers. These issues include performance impact and, in some cases, outages. Users may experience slow loading and uploading of attachments, login issues or inability for new customers to sign up. We have identified the root cause and are actively working on the service recovery.

Between 3:33PM UTC to 5:16PM UTC, Jira Align experienced intermittent service issues tied to a public cloud provider outage. All services have since been restored. For any further issues, kindly reach out to Atlassian Support.

Jira Align services are in the process of being restored. We're continuing to monitor the platform and will share any final updates at a later time.

We're experiencing an elevated level of errors and are currently monitoring the issue.

Between 2023-06-06 19:38 UTC to 2023-06-06 21:20 UTC , we experienced intermittent errors for Jira Align Cloud. The issue has been resolved and the service is operating normally.

We are investigating reports of intermittent errors for some JIRA Align Cloud customers. We will provide more details once we identify the root cause.

This incident has been resolved.

Jira Align sites in these pods are impacted by network issues at AWS in the US-EAST2 region.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

RCA is pending.

Connectivity issues were detected for this pod from 4:09pm to 4:22pm EST. Issue has been resolved. RCA is underway.

This incident has been resolved.

At this time, all Jira Align and Jira Align Launchpad sites have been restored. Our Failever worked as expected and restored site access in 5 to 10 minutes for all customers sites outside those hosted on Pod 10. Pod 10 customers encountered a 30 minute failover time frame due to high traffic loads. We will continue to monitor site activity and will post again to close out this incident.

Around 1PM EST an Cloud Outage impacted the availability of Jira Align & Jira Align Launchpad sites. Failover is currently rebooting the sites. We will provide additional updates hourly until a complete remediation is in place.

Between 12/Jul/22 4:18 UTC to 12/Jul/22 4:20 UTC, Confluence, Jira Work Management, Jira Service Management, Jira Software, and Jira Align Cloud customers were impacted by an issue affecting the service availability. This incident has been identified and resolved and the service is operating normally.

Between 06:30 UTC and 07:30 UTC, some Jira Align customers were unable to access the product. The issue has been resolved and the service is operating normally.

We have identified the root cause of the intermittent errors and the problem has been mitigated. We are now monitoring closely.

We are investigating reports of intermittent errors for some Jira Align Cloud customers.

This incident has been resolved.

maintenance has been completed, fix deployed.

We are actively applying an update to the Jira Align servers and you may experience momentary outage until this status is lifted

AWS RDS failed over the database from June 06, 2022, 4:13:21 PM UTC to June 06, 2022, 4:17:25 PM UTC for a multi-tenant environment. There is no specific action required by Atlassian or your team required.

AWS RDS failed over the database from February 04, 2022, 6:04:38 PM UTC to February 04, 2022, 6:09:22 PM UTC for a single multi-tenant environment. There is no specific action required by Atlassian or your team required

Jira Align customers in the US AWS data centers experienced a lag in connector synchronization from **23:05 Eastern 31-Jan and resumed at 08:48 1-Feb**. The Atlassian engineering team is working on a more robust solution to prevent a similar occurrence.

This incident has been resolved.

We are continuing to investigate this issue.

There was no data loss. This outage delayed the synchronization of data between Jira Align and the team services for Jira and Azure DevOps

Between 02:45 UTC to 03:58 UTC, we experienced degraded performance for Automation for Jira for Jira Cloud customers. The issue has been resolved and the service is operating normally.

We are investigating an issue with automation that is impacting Jira Cloud customers. We will provide more details within the next hour.

We are no longer having any issues with email.

We are continuing to monitor for any further issues.

We have started to see systems recover from this incident. We are now monitoring closely and expect recovery shortly.

We continue to work on resolving the incident with delayed email processing. We have identified the root cause and will provide additional updates as soon as possible.

We continue to work on resolving the incident with delayed email processing. We have identified the root cause and will provide additional updates as soon as possible.

There are potential delays in US customer email processing due to an ongoing AWS US East outage.

Cloudflare has reported: Elevated error rate for Firewall Rules Resolved - This incident has been resolved. Oct 14, 11:15 UTC Monitoring - A fix has been implemented and we are monitoring the results. Oct 14, 10:58 UTC Investigating - Cloudflare is aware of, and investigating an issue which is impacting multiple customers using firewall rules. Further detail will be provided as more information becomes available. Oct 14, 10:33 UTC

This incident has been resolved.

Jira Align users on pod 24 had degraded site and API performance from 4:15 PM to 8:30 PM US Eastern time zone. The SRE team has stubbed out the read-only calculation API which caused the issue, until a new code change can be applied

Between 1:02 PM UTC to 2:28 PM UTC, we experienced Jira Work Management, Jira Service Management, Jira Software, and Jira Align being unusable for some customers. The issue has been resolved and the service is operating normally.

We have identified the root cause of Jira being unusable for some customers and have mitigated the problem. We are now monitoring closely.

We are investigating an issue with Jira being unusable for some customers of Jira Work Management, Jira Service Management, Jira Software, and Jira Align Cloud. We will provide more details within the next hour.

This morning from at 08:58 to 09:06 Central time the AWS Relational database server failed over successfully

Issue resolved. Continuing to monitor.

Pod4 started experiencing 504 errors affecting a low volume of requests.

This incident has been resolved. We will be conducting a formal Post Incident Review (PIR) on this issue and provide a further update on Root Cause Analysis once the PIR is completed. Preliminary causation of the issue was a security configuration update and subsequent rollback. Please reach out to our support team at https://getsupport.atlassian.com/ with any questions. Thank you!

Between March 25, 2021, 10:13:28 (UTC-05:00)to March 25, 2021, 10:46:17 (UTC-05:00) we experienced application outage for some of our European customers. The issue has now been resolved and the service is operating normally.

Between 21:12 UTC to 21:35 UTC, we experienced major outage for Jira Align. The issue has been resolved and the service is operating normally.

We are investigating an issue with Jira Align that is impacting all Cloud customers due to issues with Cloudflare. We will provide more details within the next hour.

From 10:07 AM CST to 10:26 AM CST Pod 16 encountered degraded performance and normal services have been restored.

Our engineering teams have pushed a change to fix the issue. If you are still experiencing issues please contact Support.

Our engineering teams continue to look into this issue.

We are investigating reports of user sessions timing out for customers. We are investigating and have escalated to our engineering team.