Atlassian Outage History

Started Nov 19, 2025, 10:32 PM UTC· resolved Nov 20, 2025, 05:39 AM UTC

1. identified Nov 19, 2025, 10:32 PM UTC

   We are aware of some customers that are experiencing no audio when viewing their Loom recordings. Our team has identified this issue and is working urgently to restore the audio for these recordings. Please rest assured that the audio has been recorded correctly, and we expect this to be fully available when this incident is resolved. New recordings are no longer impacted by this issue. We will provide an update within two hours with our progress as the team continues to investigate.

2. identified Nov 20, 2025, 12:33 AM UTC

   Our team believes that we have identified the cause of the issue impacting audio during playback of videos for some customers. As mentioned in our previous updates, new recordings will be working as expected, however videos recorded between 19 Nov 16:51 UTC and 19 Nov 21:30 UTC are expected to be impacted by this issue. A fix for this issue to restore audio to these recordings is now being developed and tested, and we expect to have further update within 2 hours on progress for this resolution.

3. identified Nov 20, 2025, 02:30 AM UTC

   The fix to resolve issues on audio recordings impacted by this incident is now being prepared for deployment. Currently the expected duration of the rollout is 3 hours, at which point we expect the audio from the impacted recordings to be fully restored. We will provide further update at that time with the progress of the restoration and provide any additional information that may be required.

4. resolved Nov 20, 2025, 05:39 AM UTC

   The rollout of the fix for impacted videos without audio has now completed. Customers should now be able to review existing videos without audio and see that it has been properly restored. If you are continuing to see any issues with playback of your videos, please reach out to Loom support for assistance. We apologize for any inconvenience caused by this issue.

Read the full incident report →

Started Nov 18, 2025, 02:43 PM UTC· resolved Nov 18, 2025, 05:29 PM UTC

1. investigating Nov 18, 2025, 02:43 PM UTC

   We are aware that customers are receiving message NO SUCH TRACK intermittently when opening Jira issues. Our team is investigating this issue and we will share next update in 60 mins if not sooner.

2. monitoring Nov 18, 2025, 03:23 PM UTC

   Impact Users of Jira and Jira Service Management are facing intermittent issues when attempting to open Jira issues. They encounter an error message stating No such track. This issue randomly affects the user ability to utilize Jira functionalities. Current Status We are seeing some recoveries at the moment. We are actively monitoring to check for re-occurrences. We are also working on establishing a detailed root cause for the incident. Next Steps Further updates will be communicated in 60 minutes.

3. resolved Nov 18, 2025, 05:29 PM UTC

   On November 18, 2025, some Jira Service Management users may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Nov 18, 2025, 02:43 PM UTC· resolved Nov 18, 2025, 05:29 PM UTC

1. investigating Nov 18, 2025, 02:43 PM UTC

   We are aware that customers are receiving message NO SUCH TRACK intermittently when opening Jira issues. Our team is investigating this issue and we will share next update in 60 mins if not sooner.

2. monitoring Nov 18, 2025, 03:23 PM UTC

   Impact Users of Jira and Jira Service Management are facing intermittent issues when attempting to open Jira issues. They encounter an error message stating No such track. This issue randomly affects the user ability to utilize Jira functionalities. Current Status We are seeing some recoveries at the moment. We are actively monitoring to check for re-occurrences. We are also working on establishing a detailed root cause for the incident. Next Steps Further updates will be communicated in 60 minutes.

3. resolved Nov 18, 2025, 05:29 PM UTC

   On November 18, 2025, some Jira Service Management users may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Nov 18, 2025, 02:43 PM UTC· resolved Nov 18, 2025, 05:29 PM UTC

1. investigating Nov 18, 2025, 02:43 PM UTC

   We are aware that customers are receiving message NO SUCH TRACK intermittently when opening Jira issues. Our team is investigating this issue and we will share next update in 60 mins if not sooner.

2. monitoring Nov 18, 2025, 03:23 PM UTC

   Impact Users of Jira and Jira Service Management are facing intermittent issues when attempting to open Jira issues. They encounter an error message stating No such track. This issue randomly affects the user ability to utilize Jira functionalities. Current Status We are seeing some recoveries at the moment. We are actively monitoring to check for re-occurrences. We are also working on establishing a detailed root cause for the incident. Next Steps Further updates will be communicated in 60 minutes.

3. resolved Nov 18, 2025, 05:29 PM UTC

   On November 18, 2025, some Jira users may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Nov 18, 2025, 01:32 PM UTC· resolved Nov 18, 2025, 04:57 PM UTC

1. investigating Nov 18, 2025, 01:32 PM UTC

   We are aware of a global Cloudflare issue affecting Confluence Whiteboards and are currently looking into the issue.

2. investigating Nov 18, 2025, 01:35 PM UTC

   We are aware of a global Cloudflare issue affecting Confluence Whiteboards and are currently looking into the issue.

3. investigating Nov 18, 2025, 01:37 PM UTC

   We are aware of a global Cloudflare issue affecting Confluence Whiteboards and are currently looking into the issue.

4. investigating Nov 18, 2025, 02:40 PM UTC

   We are aware of a global Cloudflare issue that is currently impacting Confluence. You may notice elevated server errors in Confluence Whiteboards and Databases. Cloudflare is actively working to restore its services, and we are closely monitoring its progress. We understand how disruptive this can be and truly appreciate your patience as we monitor the situation. We will continue to provide updates as we learn more.

5. identified Nov 18, 2025, 03:58 PM UTC

   We are aware of a global Cloudflare issue that is currently impacting Confluence. Cloudflare is reporting that a fix has been implemented and services are restoring. Our engineering teams continue to monitor the restoration of services. It is possible that you may still encounter some errors or issues. We will update you when services are fully restored. We will continue to provide updates as we learn more.

6. resolved Nov 18, 2025, 04:57 PM UTC

   Elevated Errors in Confluence Whiteboards and Databases Due to Cloudflare Outage Cloudflare successfully deployed a fix for the issue that was impacting Confluence. We are no longer seeing Confluence system performance degradation and Confluence systems have been fully restored. We will continue monitoring

Read the full incident report →

Started Nov 18, 2025, 12:23 PM UTC· resolved Nov 18, 2025, 05:53 PM UTC

1. investigating Nov 18, 2025, 12:23 PM UTC

   We're experiencing an elevated level of server errors and are currently looking into the issue.

2. investigating Nov 18, 2025, 12:38 PM UTC

   We are aware of a CloudFlare issue affecting Jira Align and are investigating the situation.

3. investigating Nov 18, 2025, 01:22 PM UTC

   We are aware of a CloudFlare issue affecting Jira Align and we are investigating the situation.

4. investigating Nov 18, 2025, 02:42 PM UTC

   We’re aware of a global Cloudflare issue that is currently impacting Jira Align. Cloudflare is actively working on restoring their services, and we are closely tracking their progress. We understand how disruptive this can be and truly appreciate your patience as we monitor the situation. We’ll continue to provide updates as we learn more.

5. identified Nov 18, 2025, 03:59 PM UTC

   We are aware of a global Cloudflare issue that is currently impacting Jira Align. Cloudflare is reporting that a fix has been implemented and services are restoring. Our engineering teams continue to monitor the restoration of services. It is possible that you may still encounter some errors or issues. We will update you when services are fully restored. We will continue to provide updates as we learn more.

6. monitoring Nov 18, 2025, 05:00 PM UTC

   We are aware of a global Cloudflare issue that is currently impacting Jira Align. Cloudflare is reporting that a fix has been implemented and services are restoring. Our engineering teams continue to monitor the restoration of services. While system performance is improving, it is possible that you may still encounter some errors or issues. We will continue to monitor and update you when services are fully restored.

7. resolved Nov 18, 2025, 05:53 PM UTC

   Cloudflare services are currently operating normally. We are no longer observing elevated errors or latency across the network. Jira Align services have returned to normal operation and our engineering teams continue to closely monitor the platform.

8. postmortem Dec 17, 2025, 12:26 AM UTC

   ### Summary On November 18, 2025 between 11:30 UTC and 17:10 UTC, Atlassian customers using Jira Align and Confluence \(Whiteboards and Databases\) products experienced degraded performance. The event was triggered by an [outage impacting Cloudflare](https://blog.cloudflare.com/18-november-2025-outage/), our cloud CDN and edge network solution provider. The incident was detected within 4 minutes by our Pollinator network scanning solution. Systems were fully operational once the outage ended. ### **IMPACT** #### Jira Align * During the outage, users attempting to access Jira Align through the website or the public API may have received HTTP 5xx error codes. #### **Confluence Whiteboards and Databases** * For both Confluence Whiteboards and Databases, users had difficulty loading content and would see a blank board/database in the case of a failure. In cases where users were able to load content, they received an error stating that they are currently offline. Edits and updates were saved and synchronized to the server after the incident, once the locally cached changes could be sent. #### Atlassian Marketplace Apps * Some non-Atlassian Marketplace Apps utilizing the same third-party provider were also affected. As the infrastructure of those Marketplace Apps are not managed by Atlassian, they are not included as part of this post-incident review. ### **ROOT CAUSE** The issue was caused by an outage impacting our Cloud Delivery Network \(CDN\) and edge network solution provider. As a result, Jira Align and Confluence user requests could not reach our servers, and received HTTP 5xx errors. **Jira Align** * Jira Align passes all HTTPS requests through the edge network CDN. Since that solution was generating a high percentage of 5xx errors, the public API and the end user experience was significantly impacted. **Confluence Whiteboards and Databases** * Whiteboards and Databases use Cloudflare Durable Objects for collaborative editing of content. The outage caused failures during establishing of websocket connections to the relay worker of the durable objects, resulting in failures to load any content in the document, or communicate changes from client \(browser\) to the server. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** Acknowledging that access to our cloud services can be affected by outages of our underlying cloud providers, we continuously evaluate and improve our architecture to strengthen resilience of our applications against these issues. We are prioritizing the following improvement actions to help prevent repeating this type of incident: * Reviewing risk and likelihood of failure for our cloud service dependencies in Jira Align and Confluence Whiteboards/Databases technical stacks * Evaluating product improvements like secondary CDN or redundancy options to enable quick fallback in case of repeated outages, and mitigate a risk of failure. We apologize to customers whose services were impacted during this incident. Thanks, Atlassian Customer Support.

Read the full incident report →

Started Nov 18, 2025, 02:55 AM UTC· resolved Nov 18, 2025, 03:35 AM UTC

1. investigating Nov 18, 2025, 02:55 AM UTC

   We are aware of some customers being impacted by an error in Confluence while attempting to edit content stating 'We've lost our connection to you. Your changes will be saved when we reconnect. Trying to reconnect...'. Our team is investigating with urgency and will provide another update within an hour.

2. monitoring Nov 18, 2025, 03:16 AM UTC

   Our team has reverted a recent change that is suspected to have caused these errors, and have seen instances of these error messages to decrease. We are continuing to monitor and will update when this issue is confirmed to be resolved.

3. resolved Nov 18, 2025, 03:35 AM UTC

   Our team has been able to confirm that customers should no longer be experiencing the error while attempting to edit using Confluence. We apologize for any inconvenience this may have caused. This issue is now resolved.

Read the full incident report →

Started Nov 15, 2025, 04:29 PM UTC· resolved Nov 17, 2025, 11:50 AM UTC

1. identified Nov 15, 2025, 04:29 PM UTC

   We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

2. identified Nov 15, 2025, 09:36 PM UTC

   We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

3. monitoring Nov 15, 2025, 09:36 PM UTC

   We were experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This affected authentication for some users. After scaling our internal services, we have observed a reduction in timeout errors with reliability metrics returning to normal. We apologize for any inconvenience this may have caused.

4. resolved Nov 17, 2025, 11:50 AM UTC

   The issue has been resolved. All systems are healthy and fully operational, with no further problems observed in sending emails from Jira.

Read the full incident report →

Started Nov 15, 2025, 04:29 PM UTC· resolved Nov 17, 2025, 11:50 AM UTC

1. identified Nov 15, 2025, 04:29 PM UTC

   We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

2. identified Nov 15, 2025, 09:36 PM UTC

   We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

3. monitoring Nov 15, 2025, 09:36 PM UTC

   We were experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This affected authentication for some users. After scaling our internal services, we have observed a reduction in timeout errors with reliability metrics returning to normal. We apologize for any inconvenience this may have caused.

4. resolved Nov 17, 2025, 11:50 AM UTC

   The issue has been resolved. All systems are healthy and fully operational, with no further problems observed in sending emails from Jira.

Read the full incident report →

Started Nov 15, 2025, 04:29 PM UTC· resolved Nov 17, 2025, 11:50 AM UTC

1. identified Nov 15, 2025, 04:29 PM UTC

   We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

2. identified Nov 15, 2025, 09:36 PM UTC

   We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

3. monitoring Nov 15, 2025, 09:36 PM UTC

   We were experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This affected authentication for some users. After scaling our internal services, we have observed a reduction in timeout errors with reliability metrics returning to normal. We apologize for any inconvenience this may have caused.

4. resolved Nov 17, 2025, 11:50 AM UTC

   The issue has been resolved. All systems are healthy and fully operational, with no further problems observed in sending emails from Jira.

Read the full incident report →

Started Nov 15, 2025, 04:29 PM UTC· resolved Nov 17, 2025, 11:50 AM UTC

1. identified Nov 15, 2025, 04:29 PM UTC

   We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

2. identified Nov 15, 2025, 09:36 PM UTC

   We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

3. monitoring Nov 15, 2025, 09:36 PM UTC

   We were experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This affected authentication for some users. After scaling our internal services, we have observed a reduction in timeout errors with reliability metrics returning to normal. We apologize for any inconvenience this may have caused.

4. resolved Nov 17, 2025, 11:50 AM UTC

   The issue has been resolved. All systems are healthy and fully operational, with no further problems observed in sending emails from Jira.

Read the full incident report →

Started Nov 15, 2025, 04:29 PM UTC· resolved Nov 17, 2025, 11:50 AM UTC

1. identified Nov 15, 2025, 04:29 PM UTC

   We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

2. identified Nov 15, 2025, 09:36 PM UTC

   We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

3. monitoring Nov 15, 2025, 09:36 PM UTC

   We were experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This affected authentication for some users. After scaling our internal services, we have observed a reduction in timeout errors with reliability metrics returning to normal. We apologize for any inconvenience this may have caused.

4. resolved Nov 17, 2025, 11:50 AM UTC

   The issue has been resolved. All systems are healthy and fully operational, with no further problems observed in sending emails from Jira.

Read the full incident report →

Started Nov 14, 2025, 05:43 PM UTC· resolved Nov 14, 2025, 08:30 PM UTC

1. investigating Nov 14, 2025, 05:43 PM UTC

   We are actively investigating reports of performance degradation affecting Trello automations. We'll share updates here as more information is available.

2. identified Nov 14, 2025, 07:02 PM UTC

   We have identified the cause of the issue, and our teams are diligently working on applying mitigations. We are seeing good signs of recovery, however, some users may experience some delays in Trello Automations executing. We’ll share additional updates at 19:45 UTC, or sooner, as more information is available.

3. monitoring Nov 14, 2025, 07:49 PM UTC

   We have applied mitigations and continue to see improvements in Trello Automation processing times. However, some users may still experience delays in automation execution. We will provide another update by 20:45 UTC, or sooner if more information becomes available.

4. resolved Nov 14, 2025, 08:30 PM UTC

   On November 14, 2025 Trello users may have experienced delays on the execution of Trello automations. The issue has now been resolved, and the service is operating normally for all affected customers. Note: All automations identified as impacted by this incident will be automatically rerun, no customer actions are needed to rerun these automations.

Read the full incident report →

Started Nov 13, 2025, 06:56 PM UTC· resolved Nov 17, 2025, 12:11 AM UTC

1. investigating Nov 13, 2025, 06:56 PM UTC

   We are investigating reports that some customers using Guard are experiencing delays or non-receipt of one-time passwords (OTP), two-factor authentication (2FA), and password reset emails. Our investigations indicate that these emails are being delivered successfully, but are being quarantined or delayed by some customer's email service provider. If you are impacted, we recommend reaching out to your email server admins to check quarantine lists and release these emails. We are continuing to investigate the issue and will share updates here as more information becomes available.

2. monitoring Nov 14, 2025, 04:57 AM UTC

   Our investigation has indicated that the issues with email delivery are related to quarantine rules in effect within our customers email service providers. For customers that are continuing to experience this issue, we encourage you to reach out to your organizations email administrator to review emails placed into quarantine and to release those emails.

3. resolved Nov 17, 2025, 12:11 AM UTC

   Impacted customers have now confirmed that they are receiving their emails as expected. If you do continue to see these emails being missing or delayed, please check in with your organizations email admin to review and release them.

Read the full incident report →

Started Nov 13, 2025, 06:56 PM UTC· resolved Nov 17, 2025, 12:11 AM UTC

1. investigating Nov 13, 2025, 06:56 PM UTC

   We are investigating reports that some customers using Guard are experiencing delays or non-receipt of one-time passwords (OTP), two-factor authentication (2FA), and password reset emails. Our investigations indicate that these emails are being delivered successfully, but are being quarantined or delayed by some customer's email service provider. If you are impacted, we recommend reaching out to your email server admins to check quarantine lists and release these emails. We are continuing to investigate the issue and will share updates here as more information becomes available.

2. monitoring Nov 14, 2025, 04:57 AM UTC

   Our investigation has indicated that the issues with email delivery are related to quarantine rules in effect within our customers email service providers. For customers that are continuing to experience this issue, we encourage you to reach out to your organizations email administrator to review emails placed into quarantine and to release those emails.

3. resolved Nov 17, 2025, 12:11 AM UTC

   Impacted customers have now confirmed that they are receiving their emails as expected. If you do continue to see these emails being missing or delayed, please check in with your organizations email admin to review and release them.

Read the full incident report →

Started Nov 11, 2025, 04:59 PM UTC· resolved Nov 11, 2025, 09:10 PM UTC

1. investigating Nov 11, 2025, 04:59 PM UTC

   We are actively investigating reports of performance degradation affecting Bitbucket Cloud and git services. We'll share updates here as more information is available.

2. investigating Nov 11, 2025, 05:55 PM UTC

   We are continuing to investigate a service disruption affecting Bitbucket Cloud. We'll share updates in 60 minutes, or sooner as things progress.

3. investigating Nov 11, 2025, 07:01 PM UTC

   Our teams are continuing to address a service disruption affecting Bitbucket Cloud. We are now seeing signs of recovery, however, affected users may experience intermittent performance degradation. We'll share additional updates here in 60 minutes, or sooner as as more information is available.

4. monitoring Nov 11, 2025, 07:35 PM UTC

   The issue has now been resolved, and the service is operating normally for all affected customers. We will continue to monitor closely to confirm stability.

5. resolved Nov 11, 2025, 09:10 PM UTC

   On November 11th, 2025, Bitbucket Cloud experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers. We are committed to transparency and will publish our public post mortem on our Statuspage once this investigation is complete. We expect to publish this within the next 30 days.

6. postmortem Dec 05, 2025, 05:36 PM UTC

   ## Summary On November 11, 2025, between 16:25 and 19:13 UTC, Atlassian customers were unable to access Bitbucket Cloud services. Customers experienced a period of 1 hour and 16 minutes where performance was degraded and a period of 1 hour and 32 minutes where the Bitbucket Cloud website, APIs, and Git hosting were unavailable. The event was triggered by a code change that unintentionally impacted how we evaluate feature flags, impacting all customers. The incident was detected within 5 minutes by automated monitoring systems and mitigated by scaling multiple services and deploying a fix which put Atlassian systems into a known good state. The total time to full resolution was about 2 hours and 48 minutes. ### **IMPACT** The overall impact was between November 11, 2025, 16:25 UTC and November 11, 2025, 19:13 UTC on Bitbucket Cloud. Between 16:25 UTC and 16:50 UTC, users were seeing degraded experiences with both Git services and pull request experiences within the Bitbucket Cloud site. Starting at 16:50 UTC, users were unable to access Bitbucket Cloud and associated services entirely. ### **ROOT CAUSE** During a routine deployment, a code change had a negative impact on a component used for feature flag evaluation. To mitigate this issue the Bitbucket engineering team manually scaled up Git services. This inadvertently resulted in hitting a regional limit with our hosting provider, causing new Git service instances to fail. This ultimately led to degradation of multiple dependent services and an increased number of failed requests via Bitbucket Cloud’s website and public APIs. ### **ACTIONS TAKEN** Our team immediately began investigating the issue and testing various mitigations, including scaling the impacted services, in an effort to reduce the effects of the change. However, these efforts were unsuccessful due to an unexpected scaling limit imposed by our underlying hosting platform. Attempts to roll back the code change were also unsuccessful, as the platform’s scaling limit prevented new infrastructure from being provisioned during the rollback process. In particular, any attempts to provision new infrastructure caused a high volume of calls to occur in a short period, leading to failures, retries, and a feedback loop that worsened the situation. To address this, the team scaled down certain services to reduce load on the platform, which allowed for the successful deployment of a fix and restoration of service. Once the fix was in place, healthy services were scaled back up to meet customer demand. ### **REMEDIATION AND NEXT STEPS** We recognize the significant impact outages have on our customers’ productivity. Despite our robust testing and preventative measures, this particular issue related to feature flag evaluation was not detected in other environments and only became apparent under high load conditions that had not previously occurred. The incident has provided valuable information about our hosting platform’s scaling limits, and we are actively applying these learnings to enhance our resilience and response times. To help prevent similar incidents in the future, we have taken the following actions: * Enhanced the resiliency of the affected feature gate component to to prevent future changes from resulting in widespread service impact. * Updated application logic to prevent services from hitting these platform scaling limits. * Implemented additional safeguards to detect and handle platform-imposed limits proactively during deployment and rollback scenarios. 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

Read the full incident report →

Started Nov 10, 2025, 10:41 AM UTC· resolved Nov 10, 2025, 02:03 PM UTC

1. investigating Nov 10, 2025, 10:41 AM UTC

   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.

2. resolved Nov 10, 2025, 02:03 PM UTC

   Impact Customers experienced degraded performance in log ingestion services affecting the Ecosystem, particularly the Forge platform. Due to this issue, accessing logs ingested from the morning of the incident (starting 06:00 UTC) was impacted, leading to delays or incomplete data visibility through the Dev Console and related channels. Current Status This incident has been resolved, and Forge Logs are back in operational mode.

Read the full incident report →

Started Nov 06, 2025, 07:36 PM UTC· resolved Nov 10, 2025, 04:17 AM UTC

1. investigating Nov 06, 2025, 07:36 PM UTC

   Marketplace Community is experiencing slow load times and degraded performance on the Forums. We are actively investigating and hope to have a resolution as soon as possible.

2. investigating Nov 06, 2025, 07:50 PM UTC

   Atlassian Community is experiencing slow load times and degraded performance on the Forums. We are actively investigating and hope to have a resolution as soon as possible.

3. monitoring Nov 07, 2025, 02:10 PM UTC

   The incident has been fixed and continue to stay under monitoring.

4. resolved Nov 10, 2025, 04:17 AM UTC

   The issue has been resolved and there is no performance related slowness on Atlassian Community Forums now.

Read the full incident report →

Started Nov 03, 2025, 04:11 PM UTC· resolved Nov 03, 2025, 06:08 PM UTC

1. investigating Nov 03, 2025, 04:11 PM UTC

   We are investigating reports of degraded performance and intermittent errors for some Confluence, Jira Service Management, and Jira Cloud customers. We will provide more details in one hour, if not sooner.

2. investigating Nov 03, 2025, 05:15 PM UTC

   We are continuing to investigate the cause of degraded performance and intermittent errors impacting Automations and the Automation UI for some Confluence, Jira Service Management, and Jira Cloud customers. We will provide more details in one hour, if not sooner.

3. resolved Nov 03, 2025, 06:08 PM UTC

   On November 3, 2025, some Confluence, Jira Service Management, and Jira Cloud users may have experienced performance degradation and errors in the Global Automation UI page. Automation executions were not impacted by this incident. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Nov 03, 2025, 04:11 PM UTC· resolved Nov 03, 2025, 06:08 PM UTC

1. investigating Nov 03, 2025, 04:11 PM UTC

   We are investigating reports of degraded performance and intermittent errors for some Confluence, Jira Service Management, and Jira Cloud customers. We will provide more details in one hour, if not sooner.

2. investigating Nov 03, 2025, 05:15 PM UTC

   We are continuing to investigate the cause of degraded performance and intermittent errors impacting Automations and the Automation UI for some Confluence, Jira Service Management, and Jira Cloud customers. We will provide more details in one hour, if not sooner.

3. resolved Nov 03, 2025, 06:08 PM UTC

   On November 3, 2025, some Confluence, Jira Service Management, and Jira Cloud users may have experienced performance degradation and errors in the Global Automation UI page. Automation executions were not impacted by this incident. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Nov 03, 2025, 04:11 PM UTC· resolved Nov 03, 2025, 06:08 PM UTC

1. investigating Nov 03, 2025, 04:11 PM UTC

   We are investigating reports of degraded performance and intermittent errors for some Confluence, Jira Service Management, and Jira Cloud customers. We will provide more details in one hour, if not sooner.

2. investigating Nov 03, 2025, 05:15 PM UTC

   We are continuing to investigate the cause of degraded performance and intermittent errors impacting Automations and the Automation UI for some Confluence, Jira Service Management, and Jira Cloud customers. We will provide more details in one hour, if not sooner.

3. resolved Nov 03, 2025, 06:08 PM UTC

   On November 3, 2025, some Confluence, Jira Service Management, and Jira Cloud users may have experienced performance degradation and errors in the Global Automation UI page. Automation executions were not impacted by this incident. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Nov 03, 2025, 04:11 PM UTC· resolved Nov 03, 2025, 06:08 PM UTC

1. investigating Nov 03, 2025, 04:11 PM UTC

   We are investigating reports of degraded performance and intermittent errors for some Confluence, Jira Service Management, and Jira Cloud customers. We will provide more details in one hour, if not sooner.

2. investigating Nov 03, 2025, 05:15 PM UTC

   We are continuing to investigate the cause of degraded performance and intermittent errors impacting Automations and the Automation UI for some Confluence, Jira Service Management, and Jira Cloud customers. We will provide more details in one hour, if not sooner.

3. resolved Nov 03, 2025, 06:08 PM UTC

   On November 3, 2025, some Confluence, Jira Service Management, and Jira Cloud users may have experienced performance degradation and errors in the Global Automation UI page. Automation executions were not impacted by this incident. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Oct 31, 2025, 02:12 AM UTC· resolved Oct 31, 2025, 04:26 AM UTC

1. investigating Oct 31, 2025, 02:12 AM UTC

   Jira Service Management and Jira products are currently experiencing an issue with their Automation functionality. Customers may find that some rule conditions within Automation are not functioning as expected. Our team is working diligently to identify the cause and implement a resolution. Updates with further information will be sent in 60 minutes.

2. identified Oct 31, 2025, 03:07 AM UTC

   We continue to work on resolving the automation rules issue for Jira and Jira Service Management. We have identified the root cause and are working on mitigating the issue.

3. monitoring Oct 31, 2025, 03:40 AM UTC

   The team has identified the root cause and mitigated the issue. We are closely monitoring the rollout of the mitigation.

4. resolved Oct 31, 2025, 04:26 AM UTC

   Confirmed that the incident has been resolved and the automation rules are executing as expected.

Read the full incident report →

Started Oct 31, 2025, 02:12 AM UTC· resolved Oct 31, 2025, 04:26 AM UTC

1. investigating Oct 31, 2025, 02:12 AM UTC

   Jira Service Management and Jira products are currently experiencing an issue with their Automation functionality. Customers may find that some rule conditions within Automation are not functioning as expected. Our team is working diligently to identify the cause and implement a resolution. Updates with further information will be sent in 60 minutes.

2. identified Oct 31, 2025, 03:07 AM UTC

   We continue to work on resolving the automation rules issue for Jira and Jira Service Management. We have identified the root cause and are working on mitigating the issue.

3. monitoring Oct 31, 2025, 03:40 AM UTC

   The team has identified the root cause and mitigated the issue. We are closely monitoring the rollout of the mitigation.

4. resolved Oct 31, 2025, 04:26 AM UTC

   Confirmed that the incident has been resolved and the automation rules are executing as expected.

Read the full incident report →

Started Oct 31, 2025, 02:12 AM UTC· resolved Oct 31, 2025, 04:26 AM UTC

1. investigating Oct 31, 2025, 02:12 AM UTC

   Jira Service Management and Jira products are currently experiencing an issue with their Automation functionality. Customers may find that some rule conditions within Automation are not functioning as expected. Our team is working diligently to identify the cause and implement a resolution. Updates with further information will be sent in 60 minutes.

2. identified Oct 31, 2025, 03:07 AM UTC

   We continue to work on resolving the automation rules issue for Jira and Jira Service Management. We have identified the root cause and are working on mitigating the issue.

3. monitoring Oct 31, 2025, 03:40 AM UTC

   The team has identified the root cause and mitigated the issue. We are closely monitoring the rollout of the mitigation.

4. resolved Oct 31, 2025, 04:26 AM UTC

   Confirmed that the incident has been resolved and the automation rules are executing as expected.

Read the full incident report →