Atlassian Developer Outage History

We are aware that customers are currently experiencing installation failures when attempting to install Connect on Forge apps into Confluence. Our team is investigating with urgency and we will provide an update within the hour.

We are aware that access to created Ecohelp support tickets is not available for some of our customers. Our team is investigating this issue. Repeat creation of tickets is not required as the created tickets are visible to the Atlassian teams. We will provide next update in 60 minutes.

Customers encounter a permission error when accessing tickets: No Access - You do not have permission to view this request. Ticket creation works and created tickets are visible to the Atlassian teams. The Atlassian team continues investigating. The root cause remains unclear. We will provide next update in 60 minutes.

Customers encounter a permission error when accessing tickets: No Access - You do not have permission to view this request. Ticket creation works and created tickets are visible to the Atlassian teams. The Atlassian team continues investigating. The root cause remains unclear. We will provide next update in 60 minutes.

Customers continue to encounter a permission error when accessing tickets: No Access - You do not have permission to view this request. Ticket creation works and created tickets are visible to the Atlassian teams. The Atlassian team is engaged and continues investigation. However, the root cause remains unclear. We will provide next update in 3 hours or sooner.

Impact Customers may experience degraded performance navigating logs, as there is an issue with log ingestion that could manifest as delays or incomplete data being visible. Current Status Support teams are actively engaged in diagnosing the situation and planning the steps necessary for service restoration. Next Steps The incident management team is focused on identifying the root cause of the performance degradation and implementing measures to restore normal operations. The next update will be communicated in 60 minutes or when an important milestone is reached.

Impact The issue is affecting Forge Egress within the Ecosystem, leading to intermittent failures in authenticated egress calls. This has impacted functionalities such as Jira Incoming Mail, causing delays in fetching emails from providers like Gmail and Microsoft, and consequently affecting work item creation. Additionally, Forge Compass apps are currently failing to send data to Compass. Current Status We have identified the root cause and are in the process of deploying a fix. Next Steps Post-deployment, we will continue to closely monitor the fix to ensure stability. The next update will be provided in 60 minutes.

We are deploying a fix that will alleviate some of the issues. We are still investigating the root cause behind the intermittent failures. Our team continues to closely monitor the errors and explore additional mitigations to ensure stability.

We have identified a networking issue that is impacting fetch requests originating from forge apps. All forge-enabled products are impacted. Impact start time: Thursday, September 4th Symptoms include: - product fetch call timeout - egress fetch call timeout - storage calls timeout - resolver timeout The following errors may be present in your app logs - UND ERR CONNECT TIMEOUT - ERR SOCKET TIMEOUT We are currently investigating the root cause - seeing evidence of unstable network connections between distributed infrastructure - Packet loss - TCP resends - Eventual timeout on fetch operations We will provide another update at Sep 15 7:00 AM UTC

We are continuing to investigate and mitigate the issue. Upto 0.1% of all requests originating from Forge apps could result in Connection Timeout errors We are continuing to diagnose the root cause and are attempting mitigation in affected regions. We will continue to monitor requests and report on any improvements. Next Steps: We will apply the mitigation in other regions and continue to monitor. Next update will be within 4 hours.

We are aware of an issue affecting one of our Confluence API Endpoints /wiki/api/v2/spaces/properties , causing it to return a 500 status code. Impact started on Thursday 11 September at 7.45 PM (UTC). Our team is investigating this issue with urgency and will provide further updates throughout the investigation. We will provide an update within the next hour.

We have potentially identified the issue but verification is still ongoing. We will provide another update in an hour.

We are investigating an issue where app invocations are intermittently failing primarily in Eu-Central at around 6:41 am UTC. Apps will not work correctly during this time. We will update once this issue is resolved.

We are aware of an issue that is currently impacting some customers where apps are being uninstalled unexpectedly. Re-installing the impacted Apps should restore expected functionality. For more information on how to install apps please see the following page: https://support.atlassian.com/organization-administration/docs/installing-and-managing-app-access/ Our team is investigating this issue with urgency and will provide further update when available.

We are investigating an issue with Forge invocations and Deployments failing for some customers. We will post another update in an hour.

We are investigating an incident where app users associated with new Forge installations and Connect to Forge upgrades are not being added to Jira permission groups. We will post the next update in 30 minutes.

We are investigating an incident causing app deployments to fail with the CLI error message 'Error: Deployment failed'. We will post next update in 30 minutes.