Atlassian Outage History

Started Oct 15, 2025, 01:43 PM UTC· resolved Oct 15, 2025, 04:16 PM UTC

1. investigating Oct 15, 2025, 01:43 PM UTC

   UI based Customer interactions are currently degraded and our team is actively investigating the same. We shall keep you informed of the progress in next 2 hours.

2. investigating Oct 15, 2025, 02:34 PM UTC

   Atlassian team is actively investigating the issue with UI based Customer interactions. Existing automation rules continue to run without any issue. Accessing automation rules and creating new automation rules could lead to intermittent failures. We shall keep you informed of the progress in next 2 hours, if not sooner.

3. monitoring Oct 15, 2025, 03:26 PM UTC

   We have recovered from a issue which saw degraded Automation experience. Impact Some Customers using Jira, Confluence, and Jira Service Management were not able to create or update Automation rules, and some Automation rules which triggered webhooks might have been throttled and require re-running. Current Status The incident has been mitigated and we continue to investigate the cause of this incident Next Steps We are continuing to monitor the service, and will provide further updates in the next two hours

4. resolved Oct 15, 2025, 04:16 PM UTC

   Between 14:00 UTC to 16:00 UTC, we experienced automation rule functionality degradation for Confluence, Jira Work Management, Jira Service Management, and Jira. Impact Some customers using Jira, Confluence, and Jira Service Management were not able to create or update Automation rules, and some Automation rules which triggered webhooks might have been throttled and require re-running. Approximately 50 percent of Automation API calls were affected in the us-east-1 region with customers receiving 429 status codes. Current Status The incident has been mitigated by increasing the API Gateway rate limit service quota and disabling the internal service that was causing high traffic volume. Next Steps We are conducting a root cause analysis of the internal service. A post incident review will be conducted.

Read the full incident report →

Started Oct 12, 2025, 03:25 PM UTC· resolved Oct 12, 2025, 07:25 PM UTC

1. investigating Oct 12, 2025, 03:25 PM UTC

   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.

2. investigating Oct 12, 2025, 05:19 PM UTC

   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.

3. monitoring Oct 12, 2025, 06:33 PM UTC

   We have identified the root cause of the intermittent errors and have mitigated the problem by putting in a temporary measure. We are now monitoring closely.

4. resolved Oct 12, 2025, 07:25 PM UTC

   Between 06:58 12 Oct UTC to 18:30 12 Oct UTC, we experienced calls from a some forge apps to external services (outside of Atlassian) intermittently fail. The issue has been resolved and the service is operating normally.

Read the full incident report →

Started Oct 08, 2025, 10:20 PM UTC· resolved Oct 09, 2025, 08:00 PM UTC

1. identified Oct 08, 2025, 10:20 PM UTC

   We have identified an issue starting at 17:00 UTC on Monday, October 6th, 2025 affecting all Loom users who record videos with the Chrome Extension, causing unexpected delays when saving videos. If the browser is closed before the video is playable, the recording may be lost. To address this, we have developed an updated version of the extension, which is currently under review by Google. We anticipate the fix to be published by 20:00 UTC on October 15th, 2025, or sooner. In the meantime, users will see an in-browser message if their video has not yet been saved, advising them not to close the browser session. We will provide an update again when the fix is available.

2. resolved Oct 09, 2025, 08:00 PM UTC

   We have resolved the incident. A new version of the Loom chrome extension has been approved and published to the Chrome Extension store. Update to the latest version(v5.5.142) of the extension.

Read the full incident report →

Started Oct 06, 2025, 01:10 AM UTC· resolved Oct 08, 2025, 02:18 AM UTC

1. investigating Oct 06, 2025, 01:10 AM UTC

   We are investigating cases of degraded performance for attachments in the Customer Support portal. We will provide more details within the next hour.

2. monitoring Oct 06, 2025, 01:37 AM UTC

   We have identified the root cause of the performance degraded service and have mitigated the problem. We are now monitoring closely.

3. investigating Oct 06, 2025, 04:32 AM UTC

   On further monitoring, we see the issue resurfacing so our team is actively investigating with urgency and we will provide an update as soon as possible. We apologise for any inconvenience caused by this issue.

4. monitoring Oct 06, 2025, 04:49 AM UTC

   We identified that there was a temporary regression in our backend service health and we have mitigated the problem. We will continue to monitor the issue.

5. investigating Oct 06, 2025, 06:08 AM UTC

   We are continuing to investigate the regression issue and we will provide more details once we identify the root cause.

6. investigating Oct 06, 2025, 07:04 AM UTC

   We are continuing to see issues with customers uploading new attachments and viewing existing attachments. We have identified the root cause and work is underway to resolve the issue.

7. investigating Oct 06, 2025, 08:21 AM UTC

   We are investigating the issue of being unable to view Support tickets and uploading attachments in Atlassian support portal. We will provide more details within the next hour.

8. investigating Oct 06, 2025, 09:02 AM UTC

   We are continuing to investigate issues with our Customer Support portal. Please note that support ticket creation is still working as expected. You can continue to interact with us by replying to the email you received when your support ticket was created.

9. investigating Oct 06, 2025, 10:01 AM UTC

   Our team is actively engaged and continuing to investigate issues with our Customer Support portal. Please note that support ticket creation is still working as expected. You can continue to interact with us by replying to the email you received when your support ticket was created.

10. investigating Oct 06, 2025, 11:01 AM UTC

    Atlassian team continues to investigate the issue with utmost importance. Please note that support ticket creation is still working as expected. You can continue to interact with us by replying to the email you received when your support ticket was created.

11. investigating Oct 06, 2025, 12:01 PM UTC

    Our team continues to investigate the issue on priority. Please note that support ticket creation is still working as expected. You can continue to interact with us by replying to the email you received when your support ticket was created.

12. identified Oct 06, 2025, 01:02 PM UTC

    We have identified the cause of the issue and expect recovery shortly.

13. monitoring Oct 06, 2025, 01:13 PM UTC

    We have identified the root cause of partially impacting Atlassian support portal that led to the issue of visibility of the Support tickets and customers being unable to upload attachments. We have mitigated the problem and continue to monitoring the services closely. There will be no further updates here until the status is changed to 'Resolved' unless the issue recurs.

14. investigating Oct 06, 2025, 02:02 PM UTC

    We are again seeing issues with uploading new attachments and viewing existing attachments. We will provide more details within the 2 hours.

15. investigating Oct 06, 2025, 03:01 PM UTC

    Atlassian team is investigating the issues with viewing existing attachments and uploading attachments. We will provide more details within the next hour.

16. investigating Oct 06, 2025, 04:15 PM UTC

    We continue to investigate to identify root cause of the issue. We have made changes to contain the issue to listing attachments for tickets. As a result of some mitigation changes, rest of the support portal is working as expected. New attachments are getting uploaded and a comment is added in the support ticket indicating successful upload of the attachment. From the comment, customers can view the attachment (if required). Customers don't need to upload the attachment again. Currently, the table/list of attachments to the support ticket is not visible to our customers and we continue to work to restore this functionality. We will provide more details within the next hour.

17. investigating Oct 06, 2025, 05:54 PM UTC

    No change since our last update. We are continuing to work to restore full attachment functionality. Customers can upload attachments, but may receive an error message when doing so, and will not be able to view the attachment list at this time. However, soon after uploading, they will see a comment on their ticket that the attachment was added. Customers do not need to take additional upload steps, and our Support team will be able to access the attachment. The rest of the support portal is working as expected. Thank you for your patience. We will provide an update by 19:00 UTC, if not sooner.

18. investigating Oct 06, 2025, 06:58 PM UTC

    No change since our last update. We are continuing to work to restore full attachment functionality. Customers can upload attachments, but may receive an error message when doing so, and will not be able to view the attachment list at this time. However, soon after uploading, they will see a comment on their ticket that the attachment was added. Customers do not need to take additional upload steps, and our Support team will be able to access the attachment. The rest of the support portal is working as expected. Thank you for your patience. We will provide an update by 22:00 UTC, if not sooner.

19. investigating Oct 06, 2025, 10:00 PM UTC

    No change since our last update. We are continuing to work to restore full attachment functionality. Customers can upload attachments, but may receive an error message when doing so, and will not be able to view the attachment list at this time. However, soon after uploading, they will see a comment on their ticket that the attachment was added. Customers do not need to take additional upload steps, and our Support team will be able to access the attachment. The rest of the support portal is working as expected. Thank you for your patience. We will provide an update by October 7th 04:00 UTC, if not sooner.

20. investigating Oct 07, 2025, 04:01 AM UTC

    No change since our previous update. Our team is continuing to work to restore full attachment functionality. Customers can upload attachments, but may receive an error message when doing so, and will not be able to view the attachment list at this time. Soon after uploading, they will see a comment on their ticket that the attachment was added. Customers do not need to take additional upload steps, and our Support team will be able to access the attachment. The rest of the support portal is working as expected. Thank you for your patience. We will provide further update by October 7th 08:00 UTC, if not sooner.

21. investigating Oct 07, 2025, 08:28 AM UTC

    We don't have any new update to share at this point. However, please be rest assured that out team is continuing to work to restore full attachment functionality. Customers can upload attachments, but may receive an error message when doing so, and will not be able to view the attachment list at this time. Soon after uploading, they will see a comment on their ticket that the attachment was added. Customers do not need to take additional upload steps, and our Support team will be able to access the attachment. The rest of the support portal is working as expected. Thank you for your patience. We will provide further update by October 7th 12:00 UTC, if not sooner.

22. investigating Oct 07, 2025, 11:59 AM UTC

    Atlassian teams have identified some likely root causes and are testing and simulating to confirm them. Once the root cause is confirmed, our teams will carefully conduct thorough checks before making any changes. Meanwhile, customers can upload attachments but may see an error message and cannot view the attachment list. Shortly after uploading, they will see a comment on their ticket confirming the attachment was added. Customers do not need to take extra steps; our Support team can access the attachments. The rest of the support portal is working normally. We appreciate your patience. We will provide further update by October 7th 18:00 UTC, if not sooner.

23. identified Oct 07, 2025, 06:04 PM UTC

    Our teams are continuing to make progress and are in the final stages of validating potential fixes to address this issue. Meanwhile, customers can upload attachments but may see an error message and cannot view the attachment list. Shortly after uploading, they will see a comment on their ticket confirming the attachment was added. Customers do not need to take extra steps; our Support team can access the attachments. The rest of the support portal is working normally. We appreciate your patience and will provide a further update by October 7th, 21:00 UTC, if not sooner.

24. identified Oct 07, 2025, 09:02 PM UTC

    Our teams are continuing to make progress and are actively working on finalizing the deployment plan for fixes to address this issue. Meanwhile, customers can upload attachments but may see an error message and cannot view the attachment list. Shortly after uploading, they will see a comment on their ticket confirming the attachment was added. Customers do not need to take extra steps; our Support team can access the attachments. The rest of the support portal is working normally. We appreciate your patience and will provide a further update by October 8th, 01:00 UTC, if not sooner.

25. resolved Oct 08, 2025, 02:18 AM UTC

    We are closing this incident on Statuspage as the Atlassian Support portal functionality has been restored. We are aware that the ticket attachments panel remains unavailable and that some customers may be receiving a 'Something went wrong!' error message despite successfully uploading ticket attachments. We are working to resolve these UX issues. Atlassian Support is available for customers needing further assistance.

Read the full incident report →

Started Oct 03, 2025, 03:43 AM UTC· resolved Oct 03, 2025, 06:24 AM UTC

1. identified Oct 03, 2025, 03:43 AM UTC

   We are currently experiencing an issue where some Forge app users are seeing unexpected Allow access OAuth consent prompts when first using the app UI. There is no security impact; affected users can proceed by approving the prompt and continue using the app normally. This primarily affects apps that use auto‑consent with UI, including newly installed apps and upgraded apps where permissions changed and the user does not already have a consent grant. Our engineering team has identified the cause and is deploying a fix. We will provide our next update by 06:00 UTC. We apologize for the inconvenience and appreciate your patience.

2. monitoring Oct 03, 2025, 06:04 AM UTC

   We identified the root cause of the unexpected Allow access prompts in Forge app UI and have mitigated the problem. We are now monitoring closely.

3. resolved Oct 03, 2025, 06:24 AM UTC

   Between 29 Sep 2025 07:10 UTC and 03 Oct 2025 06:00 UTC, some customers experienced unexpected Allow access OAuth consent prompts when using the Forge app UI. The issue has been resolved, and the service is operating normally.

Read the full incident report →

Started Sep 30, 2025, 05:15 PM UTC· resolved Oct 01, 2025, 05:15 PM UTC

1. resolved Oct 08, 2025, 09:46 PM UTC

   On September 29-30 2025, for about 24 hours, Confluence Cloud experienced an incident due to the unintended deprecation of ACJS methods (https://developer.atlassian.com/cloud/confluence/about-the-connect-javascript-api/#connect-javascript-api) linked to retired V1 APIs (https://developer.atlassian.com/cloud/confluence/rest/v1/), resulting in 410 errors affecting partners reliant on these APIs. This issue is resolved, we will be working on a longer-term solution to prevent a similar incident from occurring again.

Read the full incident report →

Started Sep 30, 2025, 02:07 PM UTC· resolved Sep 30, 2025, 02:32 PM UTC

1. investigating Sep 30, 2025, 02:07 PM UTC

   We are observing delays in Opsgenie, JSM ops and Compass ops notification flows. No alert has been lost and our team is actively working on it to mitigate the delays. We'll keep you posted with further updates.

2. identified Sep 30, 2025, 02:09 PM UTC

   We continue to work on resolving the notification delays for Jira Service Management, Opsgenie, and Compass. We have identified the root cause and expect recovery shortly.

3. monitoring Sep 30, 2025, 02:22 PM UTC

   We have identified the root cause of the notification delay for Opsgenie, JSM Ops and Compass Ops and have mitigated the problem. We are now monitoring closely.

4. resolved Sep 30, 2025, 02:32 PM UTC

   Between 13:10 UTC to 14:00 UTC, we experienced notification delay for Jira Service Management, Opsgenie, and Compass in only EU-region. The issue has been resolved and the service is operating normally.

Read the full incident report →

Started Sep 30, 2025, 02:07 PM UTC· resolved Sep 30, 2025, 02:32 PM UTC

1. investigating Sep 30, 2025, 02:07 PM UTC

   We are observing delays in Opsgenie, JSM ops and Compass ops notification flows. No alert has been lost and our team is actively working on it to mitigate the delays. We'll keep you posted with further updates.

2. identified Sep 30, 2025, 02:09 PM UTC

   We continue to work on resolving the notification delays for Jira Service Management, Opsgenie, and Compass. We have identified the root cause and expect recovery shortly.

3. monitoring Sep 30, 2025, 02:22 PM UTC

   We have identified the root cause of the notification delay for Opsgenie, JSM Ops and Compass Ops and have mitigated the problem. We are now monitoring closely.

4. resolved Sep 30, 2025, 02:32 PM UTC

   Between 13:10 UTC to 14:00 UTC, we experienced notification delay for Jira Service Management, Opsgenie, and Compass in only EU-region. The issue has been resolved and the service is operating normally.

Read the full incident report →

Started Sep 29, 2025, 03:32 PM UTC· resolved Sep 29, 2025, 05:07 PM UTC

1. identified Sep 29, 2025, 03:32 PM UTC

   We are investigating cases of degraded performance of log delivery for some app developers. We are working on implementing a fix. We will provide more details within the next hour.

2. resolved Sep 29, 2025, 05:07 PM UTC

   Between 08:30 AM UTC to 16:30 UTC on September 29, 2025, some developers experienced delays of log delivery for the Dev Console. The root cause was an unexpected spike in volume that required updates to autoscaling configurations to address. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The conditions that cause the bug have been addressed and we’re actively working on a permanent fix. The issue has been resolved and the service is processing logs normally. We are currently processing the delayed logs and anticipate completion by 17:00 UTC today, September 29, 2025.

Read the full incident report →

Started Sep 26, 2025, 10:09 AM UTC· resolved Sep 26, 2025, 10:45 AM UTC

1. identified Sep 26, 2025, 10:09 AM UTC

   We are currently experiencing technical difficulties with our internal data pipelines, resulting in 5XX errors for Marketplace Reporting APIs. Consequently, Marketplace partners are unable to access reporting APIs, and users of the Partner Portal may experience degraded performance. Our engineering team is actively investigating the issue and working diligently to resolve it as quickly as possible. We will provide regular updates as more information becomes available. We apologize for the inconvenience and appreciate your patience and understanding

2. identified Sep 26, 2025, 10:10 AM UTC

   We are continuing to work on a fix for this issue.

3. monitoring Sep 26, 2025, 10:28 AM UTC

   A fix has been implemented and monitoring the fix.

4. resolved Sep 26, 2025, 10:45 AM UTC

   Issues affecting Marketplace Reporting APIs and Partner Portal have been resolved. Both services are now back up and running normally. This incident has been resolved.

Read the full incident report →

Started Sep 25, 2025, 08:14 AM UTC· resolved Sep 25, 2025, 08:14 AM UTC

1. resolved Sep 25, 2025, 08:14 AM UTC

   We experienced a disruption affecting all JSM assets APIs using Connect JWT and user impersonation for connect apps, starting on September 13th at 2:05 AM UTC and lasting until September 17th at 3:36 PM UTC. This issue was caused by an internal routing change within Atlassian systems. During this time, all Assets API calls using Connect authentications were disrupted. The issue has now been resolved, and all affected APIs are fully operational again. We sincerely apologise for any inconvenience caused and thank you for your patience and understanding.

Read the full incident report →

Started Sep 22, 2025, 05:59 AM UTC· resolved Sep 22, 2025, 07:17 AM UTC

1. identified Sep 22, 2025, 05:59 AM UTC

   Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

2. monitoring Sep 22, 2025, 06:55 AM UTC

   Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

3. resolved Sep 22, 2025, 07:17 AM UTC

   A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

4. postmortem Oct 01, 2025, 06:22 AM UTC

   ### **SUMMARY** On September 22, 2025, between 04:38 and 04:48 UTC, Atlassian customers experienced connection errors preventing access to their [atlassian.net](http://atlassian.net/) sites. Some customers observed intermittent errors as services gradually recovered until 06:17 UTC. The event was triggered by a faulty configuration change to our Content Delivery Network \(CDN\). The change included an invalid hostname which prevented customers from successfully connecting to [atlassian.net](http://atlassian.net/) domains. The incident was detected within 1 minute by our monitoring systems and mitigated by rolling back the change, which put Atlassian systems into a known good state. The acute impact was resolved in 10 minutes and all lingering errors resolved in 1 hour 38 minutes. ### **IMPACT** The acute impact occurred on September 22, 2025, between 04:38 UTC and 04:48 UTC to Confluence, Compass and Jira, including Jira Service Management. The incident caused service disruption to customers when they attempted to load those products in their browser or interact with APIs. Between 04:48 UTC and 06:17 UTC some customers continued to observe intermittent errors as services gradually recovered. ### **ROOT CAUSE** The issue was caused by a change to the hostname configuration of our Content Delivery Network \(CDN\). As a result, the products mentioned could not receive connections, and the users received TLS handshake errors, followed by HTTP 503 and 403 errors. More specifically a new CDN configuration contained a resource name which conflicted with the existing customer-serving CDN resource, and was able to be deployed, overwriting it. The root cause of the incident was the failure in the detection of the bug by our pre-deployment validations and tests. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that you rely on our products for your daily operations and productivity, and we sincerely apologize for any impact this disruption has had on you, your team or your organisation. We are prioritizing the following improvement actions to help avoid repeating this type of incident: * Improved pre-deployment change controls and testing. * Improved validation of target configurations before deployment to ensure customer-serving CDN resources cannot their hostnames changed. * Sharding of our CDN configuration to enable progressive changes. We sincerely appreciate your understanding and patience as we improve our processes to provide a better customer experience. Thank you, Atlassian Customer Support

Read the full incident report →

Started Sep 22, 2025, 05:59 AM UTC· resolved Sep 22, 2025, 07:17 AM UTC

1. identified Sep 22, 2025, 05:59 AM UTC

   Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

2. monitoring Sep 22, 2025, 06:55 AM UTC

   Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

3. resolved Sep 22, 2025, 07:17 AM UTC

   A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

4. postmortem Oct 01, 2025, 06:23 AM UTC

   ### **SUMMARY** On September 22, 2025, between 04:38 and 04:48 UTC, Atlassian customers experienced connection errors preventing access to their [atlassian.net](http://atlassian.net/) sites. Some customers observed intermittent errors as services gradually recovered until 06:17 UTC. The event was triggered by a faulty configuration change to our Content Delivery Network \(CDN\). The change included an invalid hostname which prevented customers from successfully connecting to [atlassian.net](http://atlassian.net/) domains. The incident was detected within 1 minute by our monitoring systems and mitigated by rolling back the change, which put Atlassian systems into a known good state. The acute impact was resolved in 10 minutes and all lingering errors resolved in 1 hour 38 minutes. ### **IMPACT** The acute impact occurred on September 22, 2025, between 04:38 UTC and 04:48 UTC to Confluence, Compass and Jira, including Jira Service Management. The incident caused service disruption to customers when they attempted to load those products in their browser or interact with APIs. Between 04:48 UTC and 06:17 UTC some customers continued to observe intermittent errors as services gradually recovered. ### **ROOT CAUSE** The issue was caused by a change to the hostname configuration of our Content Delivery Network \(CDN\). As a result, the products mentioned could not receive connections, and the users received TLS handshake errors, followed by HTTP 503 and 403 errors. More specifically a new CDN configuration contained a resource name which conflicted with the existing customer-serving CDN resource, and was able to be deployed, overwriting it. The root cause of the incident was the failure in the detection of the bug by our pre-deployment validations and tests. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that you rely on our products for your daily operations and productivity, and we sincerely apologize for any impact this disruption has had on you, your team or your organisation. We are prioritizing the following improvement actions to help avoid repeating this type of incident: * Improved pre-deployment change controls and testing. * Improved validation of target configurations before deployment to ensure customer-serving CDN resources cannot their hostnames changed. * Sharding of our CDN configuration to enable progressive changes. We sincerely appreciate your understanding and patience as we improve our processes to provide a better customer experience. Thank you, Atlassian Customer Support

Read the full incident report →

Started Sep 22, 2025, 05:59 AM UTC· resolved Sep 22, 2025, 07:17 AM UTC

1. identified Sep 22, 2025, 05:59 AM UTC

   Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

2. monitoring Sep 22, 2025, 06:55 AM UTC

   Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

3. resolved Sep 22, 2025, 07:17 AM UTC

   A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

4. postmortem Oct 01, 2025, 06:23 AM UTC

   ### **SUMMARY** On September 22, 2025, between 04:38 and 04:48 UTC, Atlassian customers experienced connection errors preventing access to their [atlassian.net](http://atlassian.net/) sites. Some customers observed intermittent errors as services gradually recovered until 06:17 UTC. The event was triggered by a faulty configuration change to our Content Delivery Network \(CDN\). The change included an invalid hostname which prevented customers from successfully connecting to [atlassian.net](http://atlassian.net/) domains. The incident was detected within 1 minute by our monitoring systems and mitigated by rolling back the change, which put Atlassian systems into a known good state. The acute impact was resolved in 10 minutes and all lingering errors resolved in 1 hour 38 minutes. ### **IMPACT** The acute impact occurred on September 22, 2025, between 04:38 UTC and 04:48 UTC to Confluence, Compass and Jira, including Jira Service Management. The incident caused service disruption to customers when they attempted to load those products in their browser or interact with APIs. Between 04:48 UTC and 06:17 UTC some customers continued to observe intermittent errors as services gradually recovered. ### **ROOT CAUSE** The issue was caused by a change to the hostname configuration of our Content Delivery Network \(CDN\). As a result, the products mentioned could not receive connections, and the users received TLS handshake errors, followed by HTTP 503 and 403 errors. More specifically a new CDN configuration contained a resource name which conflicted with the existing customer-serving CDN resource, and was able to be deployed, overwriting it. The root cause of the incident was the failure in the detection of the bug by our pre-deployment validations and tests. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that you rely on our products for your daily operations and productivity, and we sincerely apologize for any impact this disruption has had on you, your team or your organisation. We are prioritizing the following improvement actions to help avoid repeating this type of incident: * Improved pre-deployment change controls and testing. * Improved validation of target configurations before deployment to ensure customer-serving CDN resources cannot their hostnames changed. * Sharding of our CDN configuration to enable progressive changes. We sincerely appreciate your understanding and patience as we improve our processes to provide a better customer experience. Thank you, Atlassian Customer Support

Read the full incident report →

Started Sep 22, 2025, 05:59 AM UTC· resolved Sep 22, 2025, 07:17 AM UTC

1. identified Sep 22, 2025, 05:59 AM UTC

   Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

2. monitoring Sep 22, 2025, 06:55 AM UTC

   Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

3. resolved Sep 22, 2025, 07:17 AM UTC

   A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

4. postmortem Oct 01, 2025, 06:22 AM UTC

   ### **SUMMARY** On September 22, 2025, between 04:38 and 04:48 UTC, Atlassian customers experienced connection errors preventing access to their [atlassian.net](http://atlassian.net/) sites. Some customers observed intermittent errors as services gradually recovered until 06:17 UTC. The event was triggered by a faulty configuration change to our Content Delivery Network \(CDN\). The change included an invalid hostname which prevented customers from successfully connecting to [atlassian.net](http://atlassian.net/) domains. The incident was detected within 1 minute by our monitoring systems and mitigated by rolling back the change, which put Atlassian systems into a known good state. The acute impact was resolved in 10 minutes and all lingering errors resolved in 1 hour 38 minutes. ### **IMPACT** The acute impact occurred on September 22, 2025, between 04:38 UTC and 04:48 UTC to Confluence, Compass and Jira, including Jira Service Management. The incident caused service disruption to customers when they attempted to load those products in their browser or interact with APIs. Between 04:48 UTC and 06:17 UTC some customers continued to observe intermittent errors as services gradually recovered. ### **ROOT CAUSE** The issue was caused by a change to the hostname configuration of our Content Delivery Network \(CDN\). As a result, the products mentioned could not receive connections, and the users received TLS handshake errors, followed by HTTP 503 and 403 errors. More specifically a new CDN configuration contained a resource name which conflicted with the existing customer-serving CDN resource, and was able to be deployed, overwriting it. The root cause of the incident was the failure in the detection of the bug by our pre-deployment validations and tests. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that you rely on our products for your daily operations and productivity, and we sincerely apologize for any impact this disruption has had on you, your team or your organisation. We are prioritizing the following improvement actions to help avoid repeating this type of incident: * Improved pre-deployment change controls and testing. * Improved validation of target configurations before deployment to ensure customer-serving CDN resources cannot their hostnames changed. * Sharding of our CDN configuration to enable progressive changes. We sincerely appreciate your understanding and patience as we improve our processes to provide a better customer experience. Thank you, Atlassian Customer Support

Read the full incident report →

Started Sep 22, 2025, 05:59 AM UTC· resolved Sep 22, 2025, 07:17 AM UTC

1. identified Sep 22, 2025, 05:59 AM UTC

   Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

2. monitoring Sep 22, 2025, 06:55 AM UTC

   Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

3. resolved Sep 22, 2025, 07:17 AM UTC

   A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

4. postmortem Oct 01, 2025, 06:24 AM UTC

   ### **SUMMARY** On September 22, 2025, between 04:38 and 04:48 UTC, Atlassian customers experienced connection errors preventing access to their [atlassian.net](http://atlassian.net/) sites. Some customers observed intermittent errors as services gradually recovered until 06:17 UTC. The event was triggered by a faulty configuration change to our Content Delivery Network \(CDN\). The change included an invalid hostname which prevented customers from successfully connecting to [atlassian.net](http://atlassian.net/) domains. The incident was detected within 1 minute by our monitoring systems and mitigated by rolling back the change, which put Atlassian systems into a known good state. The acute impact was resolved in 10 minutes and all lingering errors resolved in 1 hour 38 minutes. ### **IMPACT** The acute impact occurred on September 22, 2025, between 04:38 UTC and 04:48 UTC to Confluence, Compass and Jira, including Jira Service Management. The incident caused service disruption to customers when they attempted to load those products in their browser or interact with APIs. Between 04:48 UTC and 06:17 UTC some customers continued to observe intermittent errors as services gradually recovered. ### **ROOT CAUSE** The issue was caused by a change to the hostname configuration of our Content Delivery Network \(CDN\). As a result, the products mentioned could not receive connections, and the users received TLS handshake errors, followed by HTTP 503 and 403 errors. More specifically a new CDN configuration contained a resource name which conflicted with the existing customer-serving CDN resource, and was able to be deployed, overwriting it. The root cause of the incident was the failure in the detection of the bug by our pre-deployment validations and tests. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that you rely on our products for your daily operations and productivity, and we sincerely apologize for any impact this disruption has had on you, your team or your organisation. We are prioritizing the following improvement actions to help avoid repeating this type of incident: * Improved pre-deployment change controls and testing. * Improved validation of target configurations before deployment to ensure customer-serving CDN resources cannot their hostnames changed. * Sharding of our CDN configuration to enable progressive changes. We sincerely appreciate your understanding and patience as we improve our processes to provide a better customer experience. Thank you, Atlassian Customer Support

Read the full incident report →

Started Sep 22, 2025, 05:59 AM UTC· resolved Sep 22, 2025, 07:17 AM UTC

1. identified Sep 22, 2025, 05:59 AM UTC

   Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

2. monitoring Sep 22, 2025, 06:55 AM UTC

   Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

3. resolved Sep 22, 2025, 07:17 AM UTC

   A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

4. postmortem Oct 01, 2025, 06:23 AM UTC

   ### **SUMMARY** On September 22, 2025, between 04:38 and 04:48 UTC, Atlassian customers experienced connection errors preventing access to their [atlassian.net](http://atlassian.net/) sites. Some customers observed intermittent errors as services gradually recovered until 06:17 UTC. The event was triggered by a faulty configuration change to our Content Delivery Network \(CDN\). The change included an invalid hostname which prevented customers from successfully connecting to [atlassian.net](http://atlassian.net/) domains. The incident was detected within 1 minute by our monitoring systems and mitigated by rolling back the change, which put Atlassian systems into a known good state. The acute impact was resolved in 10 minutes and all lingering errors resolved in 1 hour 38 minutes. ### **IMPACT** The acute impact occurred on September 22, 2025, between 04:38 UTC and 04:48 UTC to Confluence, Compass and Jira, including Jira Service Management. The incident caused service disruption to customers when they attempted to load those products in their browser or interact with APIs. Between 04:48 UTC and 06:17 UTC some customers continued to observe intermittent errors as services gradually recovered. ### **ROOT CAUSE** The issue was caused by a change to the hostname configuration of our Content Delivery Network \(CDN\). As a result, the products mentioned could not receive connections, and the users received TLS handshake errors, followed by HTTP 503 and 403 errors. More specifically a new CDN configuration contained a resource name which conflicted with the existing customer-serving CDN resource, and was able to be deployed, overwriting it. The root cause of the incident was the failure in the detection of the bug by our pre-deployment validations and tests. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that you rely on our products for your daily operations and productivity, and we sincerely apologize for any impact this disruption has had on you, your team or your organisation. We are prioritizing the following improvement actions to help avoid repeating this type of incident: * Improved pre-deployment change controls and testing. * Improved validation of target configurations before deployment to ensure customer-serving CDN resources cannot their hostnames changed. * Sharding of our CDN configuration to enable progressive changes. We sincerely appreciate your understanding and patience as we improve our processes to provide a better customer experience. Thank you, Atlassian Customer Support

Read the full incident report →

Started Sep 22, 2025, 05:38 AM UTC· resolved Sep 22, 2025, 07:17 AM UTC

1. identified Sep 22, 2025, 05:38 AM UTC

   Our team is continuing to monitor Jira and Confluence products following the earlier issues relating to an erroneous certificate change. We are assessing all impacted products to ensure that services are fully restored and we will provide further update within the hour.

2. identified Sep 22, 2025, 05:59 AM UTC

   Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

3. monitoring Sep 22, 2025, 06:55 AM UTC

   Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

4. resolved Sep 22, 2025, 07:17 AM UTC

   A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

5. postmortem Oct 01, 2025, 06:21 AM UTC

   ### **SUMMARY** On September 22, 2025, between 04:38 and 04:48 UTC, Atlassian customers experienced connection errors preventing access to their [atlassian.net](http://atlassian.net/) sites. Some customers observed intermittent errors as services gradually recovered until 06:17 UTC. The event was triggered by a faulty configuration change to our Content Delivery Network \(CDN\). The change included an invalid hostname which prevented customers from successfully connecting to [atlassian.net](http://atlassian.net/) domains. The incident was detected within 1 minute by our monitoring systems and mitigated by rolling back the change, which put Atlassian systems into a known good state. The acute impact was resolved in 10 minutes and all lingering errors resolved in 1 hour 38 minutes. ### **IMPACT** The acute impact occurred on September 22, 2025, between 04:38 UTC and 04:48 UTC to Confluence, Compass and Jira, including Jira Service Management. The incident caused service disruption to customers when they attempted to load those products in their browser or interact with APIs. Between 04:48 UTC and 06:17 UTC some customers continued to observe intermittent errors as services gradually recovered. ### **ROOT CAUSE** The issue was caused by a change to the hostname configuration of our Content Delivery Network \(CDN\). As a result, the products mentioned could not receive connections, and the users received TLS handshake errors, followed by HTTP 503 and 403 errors. More specifically a new CDN configuration contained a resource name which conflicted with the existing customer-serving CDN resource, and was able to be deployed, overwriting it. The root cause of the incident was the failure in the detection of the bug by our pre-deployment validations and tests. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that you rely on our products for your daily operations and productivity, and we sincerely apologize for any impact this disruption has had on you, your team or your organisation. We are prioritizing the following improvement actions to help avoid repeating this type of incident: * Improved pre-deployment change controls and testing. * Improved validation of target configurations before deployment to ensure customer-serving CDN resources cannot their hostnames changed. * Sharding of our CDN configuration to enable progressive changes. We sincerely appreciate your understanding and patience as we improve our processes to provide a better customer experience. Thank you, Atlassian Customer Support

Read the full incident report →

Started Sep 22, 2025, 05:38 AM UTC· resolved Sep 22, 2025, 07:17 AM UTC

1. identified Sep 22, 2025, 05:38 AM UTC

   Our team is continuing to monitor Jira and Confluence products following the earlier issues relating to an erroneous certificate change. We are assessing all impacted products to ensure that services are fully restored and we will provide further update within the hour.

2. identified Sep 22, 2025, 05:59 AM UTC

   Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

3. monitoring Sep 22, 2025, 06:55 AM UTC

   Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

4. resolved Sep 22, 2025, 07:17 AM UTC

   A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

5. postmortem Oct 01, 2025, 06:20 AM UTC

   ### **SUMMARY** On September 22, 2025, between 04:38 and 04:48 UTC, Atlassian customers experienced connection errors preventing access to their [atlassian.net](http://atlassian.net/) sites. Some customers observed intermittent errors as services gradually recovered until 06:17 UTC. The event was triggered by a faulty configuration change to our Content Delivery Network \(CDN\). The change included an invalid hostname which prevented customers from successfully connecting to [atlassian.net](http://atlassian.net/) domains. The incident was detected within 1 minute by our monitoring systems and mitigated by rolling back the change, which put Atlassian systems into a known good state. The acute impact was resolved in 10 minutes and all lingering errors resolved in 1 hour 38 minutes. ### **IMPACT** The acute impact occurred on September 22, 2025, between 04:38 UTC and 04:48 UTC to Confluence, Compass and Jira, including Jira Service Management. The incident caused service disruption to customers when they attempted to load those products in their browser or interact with APIs. Between 04:48 UTC and 06:17 UTC some customers continued to observe intermittent errors as services gradually recovered. ### **ROOT CAUSE** The issue was caused by a change to the hostname configuration of our Content Delivery Network \(CDN\). As a result, the products mentioned could not receive connections, and the users received TLS handshake errors, followed by HTTP 503 and 403 errors. More specifically a new CDN configuration contained a resource name which conflicted with the existing customer-serving CDN resource, and was able to be deployed, overwriting it. The root cause of the incident was the failure in the detection of the bug by our pre-deployment validations and tests. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that you rely on our products for your daily operations and productivity, and we sincerely apologize for any impact this disruption has had on you, your team or your organisation. We are prioritizing the following improvement actions to help avoid repeating this type of incident: * Improved pre-deployment change controls and testing. * Improved validation of target configurations before deployment to ensure customer-serving CDN resources cannot their hostnames changed. * Sharding of our CDN configuration to enable progressive changes. We sincerely appreciate your understanding and patience as we improve our processes to provide a better customer experience. Thank you, Atlassian Customer Support

Read the full incident report →

Started Sep 22, 2025, 05:38 AM UTC· resolved Sep 22, 2025, 07:17 AM UTC

1. identified Sep 22, 2025, 05:38 AM UTC

   Our team is continuing to monitor Jira and Confluence products following the earlier issues relating to an erroneous certificate change. We are assessing all impacted products to ensure that services are fully restored and we will provide further update within the hour.

2. identified Sep 22, 2025, 05:59 AM UTC

   Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

3. monitoring Sep 22, 2025, 06:55 AM UTC

   Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

4. resolved Sep 22, 2025, 07:17 AM UTC

   A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

5. postmortem Oct 01, 2025, 06:21 AM UTC

   ### **SUMMARY** On September 22, 2025, between 04:38 and 04:48 UTC, Atlassian customers experienced connection errors preventing access to their [atlassian.net](http://atlassian.net/) sites. Some customers observed intermittent errors as services gradually recovered until 06:17 UTC. The event was triggered by a faulty configuration change to our Content Delivery Network \(CDN\). The change included an invalid hostname which prevented customers from successfully connecting to [atlassian.net](http://atlassian.net/) domains. The incident was detected within 1 minute by our monitoring systems and mitigated by rolling back the change, which put Atlassian systems into a known good state. The acute impact was resolved in 10 minutes and all lingering errors resolved in 1 hour 38 minutes. ### **IMPACT** The acute impact occurred on September 22, 2025, between 04:38 UTC and 04:48 UTC to Confluence, Compass and Jira, including Jira Service Management. The incident caused service disruption to customers when they attempted to load those products in their browser or interact with APIs. Between 04:48 UTC and 06:17 UTC some customers continued to observe intermittent errors as services gradually recovered. ### **ROOT CAUSE** The issue was caused by a change to the hostname configuration of our Content Delivery Network \(CDN\). As a result, the products mentioned could not receive connections, and the users received TLS handshake errors, followed by HTTP 503 and 403 errors. More specifically a new CDN configuration contained a resource name which conflicted with the existing customer-serving CDN resource, and was able to be deployed, overwriting it. The root cause of the incident was the failure in the detection of the bug by our pre-deployment validations and tests. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that you rely on our products for your daily operations and productivity, and we sincerely apologize for any impact this disruption has had on you, your team or your organisation. We are prioritizing the following improvement actions to help avoid repeating this type of incident: * Improved pre-deployment change controls and testing. * Improved validation of target configurations before deployment to ensure customer-serving CDN resources cannot their hostnames changed. * Sharding of our CDN configuration to enable progressive changes. We sincerely appreciate your understanding and patience as we improve our processes to provide a better customer experience. Thank you, Atlassian Customer Support

Read the full incident report →

Started Sep 22, 2025, 05:38 AM UTC· resolved Sep 22, 2025, 07:17 AM UTC

1. identified Sep 22, 2025, 05:38 AM UTC

   Our team is continuing to monitor Jira and Confluence products following the earlier issues relating to an erroneous certificate change. We are assessing all impacted products to ensure that services are fully restored and we will provide further update within the hour.

2. identified Sep 22, 2025, 05:59 AM UTC

   Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

3. monitoring Sep 22, 2025, 06:55 AM UTC

   Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

4. resolved Sep 22, 2025, 07:17 AM UTC

   A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

5. postmortem Oct 01, 2025, 06:21 AM UTC

   ### **SUMMARY** On September 22, 2025, between 04:38 and 04:48 UTC, Atlassian customers experienced connection errors preventing access to their [atlassian.net](http://atlassian.net/) sites. Some customers observed intermittent errors as services gradually recovered until 06:17 UTC. The event was triggered by a faulty configuration change to our Content Delivery Network \(CDN\). The change included an invalid hostname which prevented customers from successfully connecting to [atlassian.net](http://atlassian.net/) domains. The incident was detected within 1 minute by our monitoring systems and mitigated by rolling back the change, which put Atlassian systems into a known good state. The acute impact was resolved in 10 minutes and all lingering errors resolved in 1 hour 38 minutes. ### **IMPACT** The acute impact occurred on September 22, 2025, between 04:38 UTC and 04:48 UTC to Confluence, Compass and Jira, including Jira Service Management. The incident caused service disruption to customers when they attempted to load those products in their browser or interact with APIs. Between 04:48 UTC and 06:17 UTC some customers continued to observe intermittent errors as services gradually recovered. ### **ROOT CAUSE** The issue was caused by a change to the hostname configuration of our Content Delivery Network \(CDN\). As a result, the products mentioned could not receive connections, and the users received TLS handshake errors, followed by HTTP 503 and 403 errors. More specifically a new CDN configuration contained a resource name which conflicted with the existing customer-serving CDN resource, and was able to be deployed, overwriting it. The root cause of the incident was the failure in the detection of the bug by our pre-deployment validations and tests. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that you rely on our products for your daily operations and productivity, and we sincerely apologize for any impact this disruption has had on you, your team or your organisation. We are prioritizing the following improvement actions to help avoid repeating this type of incident: * Improved pre-deployment change controls and testing. * Improved validation of target configurations before deployment to ensure customer-serving CDN resources cannot their hostnames changed. * Sharding of our CDN configuration to enable progressive changes. We sincerely appreciate your understanding and patience as we improve our processes to provide a better customer experience. Thank you, Atlassian Customer Support

Read the full incident report →

Started Sep 22, 2025, 05:09 AM UTC· resolved Sep 22, 2025, 07:17 AM UTC

1. investigating Sep 22, 2025, 05:09 AM UTC

   Our team is aware that access to Jira and Confluence cloud products was degraded between 04:39 and 04:52 UTC due to an erroneous certificate. The certificate has now been corrected and functionality has been restored. We are continuing to monitor the situation and will provide further update when available.

2. identified Sep 22, 2025, 05:38 AM UTC

   Our team is continuing to monitor Jira and Confluence products following the earlier issues relating to an erroneous certificate change. We are assessing all impacted products to ensure that services are fully restored and we will provide further update within the hour.

3. identified Sep 22, 2025, 05:59 AM UTC

   Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.

4. monitoring Sep 22, 2025, 06:55 AM UTC

   Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.

5. resolved Sep 22, 2025, 07:17 AM UTC

   A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.

6. postmortem Oct 01, 2025, 06:20 AM UTC

   ### **SUMMARY** On September 22, 2025, between 04:38 and 04:48 UTC, Atlassian customers experienced connection errors preventing access to their [atlassian.net](http://atlassian.net/) sites. Some customers observed intermittent errors as services gradually recovered until 06:17 UTC. The event was triggered by a faulty configuration change to our Content Delivery Network \(CDN\). The change included an invalid hostname which prevented customers from successfully connecting to [atlassian.net](http://atlassian.net/) domains. The incident was detected within 1 minute by our monitoring systems and mitigated by rolling back the change, which put Atlassian systems into a known good state. The acute impact was resolved in 10 minutes and all lingering errors resolved in 1 hour 38 minutes. ### **IMPACT** The acute impact occurred on September 22, 2025, between 04:38 UTC and 04:48 UTC to Confluence, Compass and Jira, including Jira Service Management. The incident caused service disruption to customers when they attempted to load those products in their browser or interact with APIs. Between 04:48 UTC and 06:17 UTC some customers continued to observe intermittent errors as services gradually recovered. ### **ROOT CAUSE** The issue was caused by a change to the hostname configuration of our Content Delivery Network \(CDN\). As a result, the products mentioned could not receive connections, and the users received TLS handshake errors, followed by HTTP 503 and 403 errors. More specifically a new CDN configuration contained a resource name which conflicted with the existing customer-serving CDN resource, and was able to be deployed, overwriting it. The root cause of the incident was the failure in the detection of the bug by our pre-deployment validations and tests. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that you rely on our products for your daily operations and productivity, and we sincerely apologize for any impact this disruption has had on you, your team or your organisation. We are prioritizing the following improvement actions to help avoid repeating this type of incident: * Improved pre-deployment change controls and testing. * Improved validation of target configurations before deployment to ensure customer-serving CDN resources cannot their hostnames changed. * Sharding of our CDN configuration to enable progressive changes. We sincerely appreciate your understanding and patience as we improve our processes to provide a better customer experience. Thank you, Atlassian Customer Support

Read the full incident report →

Started Sep 19, 2025, 02:23 PM UTC· resolved Sep 19, 2025, 03:26 PM UTC

1. identified Sep 19, 2025, 02:23 PM UTC

   We have identified an issue with creating or editing data lake connections in Atlassian Analytics and we're working to resolve.

2. resolved Sep 19, 2025, 03:26 PM UTC

   We have resolved the issue and restored the ability to create and edit data lake connections in Atlassian Analytics.

Read the full incident report →

Started Sep 16, 2025, 04:00 AM UTC· resolved Sep 16, 2025, 04:30 AM UTC

1. investigating Sep 16, 2025, 04:00 AM UTC

   We are investigating cases of degraded performance for Atlassian Bitbucket Cloud Pipelines customers. We will provide more details within the next hour. We have mitigated the impact on self-hosted runners but cloud users are continuing to see delays on pipelines starting.

2. identified Sep 16, 2025, 04:13 AM UTC

   We continue to work on resolving the delayed Pipelines for Atlassian Bitbucket. We have identified the root cause and expect recovery shortly.

3. monitoring Sep 16, 2025, 04:19 AM UTC

   We have identified the root cause of the Pipelines delays and have mitigated the problem. We are now monitoring closely.

4. resolved Sep 16, 2025, 04:30 AM UTC

   Between 03:30 UTC to 03:50 UTC, we experienced delyas in running pipelines for Atlassian Bitbucket. The issue has been resolved and the service is operating normally.

Read the full incident report →

Started Sep 12, 2025, 08:43 PM UTC· resolved Sep 12, 2025, 10:14 PM UTC

1. monitoring Sep 12, 2025, 08:43 PM UTC

   From 5:03 AM ET to 4:15 PM ET, some customers were unable to record Zoom meetings using Loom Meeting Recordings. Attempts made during this time may appear in your library but will not be playable, as no recording was captured. Unfortunately, these recordings cannot be recovered. We have released a fix and we are monitoring recovery.

2. resolved Sep 12, 2025, 10:14 PM UTC

   The issue has been resolved and the service is operating normally.

Read the full incident report →