Atlassian Outage History

Started Oct 21, 2026, 05:22 PM UTC· resolved Oct 21, 2026, 06:01 PM UTC

1. investigating Oct 21, 2026, 05:22 PM UTC

   We are actively investigating reports of a service disruption affecting Bitbucket. We will share updates here as more information is available.

2. investigating Oct 21, 2026, 05:39 PM UTC

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. We are seeing some recovery, and will continue to share additional updates here as more information is available.

3. monitoring Oct 21, 2026, 05:51 PM UTC

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

4. resolved Oct 21, 2026, 06:01 PM UTC

   On October 21, 2026, Bitbucket 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.

Read the full incident report →

Started Oct 21, 2026, 03:30 PM UTC· resolved Oct 21, 2026, 06:25 PM UTC

1. investigating Oct 21, 2026, 03:30 PM UTC

   We are actively investigating reports of performance degradation affecting Rovo MCP. We will share updates here as more information is available.

2. identified Oct 21, 2026, 04:35 PM UTC

   Our teams are diligently working on a mitigation. Affected users may experience performance degradation with Rovo MCP, including timeout issues. We will continue to share additional updates here as more information is available.

3. identified Oct 21, 2026, 05:06 PM UTC

   Fix deployment is in progress, and we are observing improvements with declining error rates. We will continue to share additional updates here as more information is available.

4. monitoring Oct 21, 2026, 06:16 PM UTC

   The performance degradation of Rovo MCP has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

5. resolved Oct 21, 2026, 06:25 PM UTC

   On October 21, 2026, users may have experienced performance degradation with Rovo MCP. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Oct 21, 2026, 02:28 PM UTC· resolved Oct 21, 2026, 03:45 PM UTC

1. investigating Oct 21, 2026, 02:28 PM UTC

   We are investigating an issue impacting the project sidebar and navigation in Jira Cloud. Users may encounter timeouts or missing menus when attempting to access project views. Teams are actively analyzing telemetry to identify a mitigation. We will provide our next update in 60 minutes, or sooner.

2. monitoring Oct 21, 2026, 03:01 PM UTC

   Mitigations are in place and we are seeing recovery across Jira Cloud navigation services. Project sidebars are now loading as expected. Our teams continue to monitor the situation, and we expect to confirm full resolution in our next update in 1 hour or sooner.

3. resolved Oct 21, 2026, 03:45 PM UTC

   On October 21, 2026, JIRA, JSM, JPD, and JWM users may have experienced performance degradation impacting the project sidebar and navigation. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Oct 21, 2026, 02:28 PM UTC· resolved Oct 21, 2026, 03:45 PM UTC

1. investigating Oct 21, 2026, 02:28 PM UTC

   We are investigating an issue impacting the project sidebar and navigation in Jira Cloud. Users may encounter timeouts or missing menus when attempting to access project views. Teams are actively analyzing telemetry to identify a mitigation. We will provide our next update in 60 minutes, or sooner.

2. monitoring Oct 21, 2026, 03:01 PM UTC

   Mitigations are in place and we are seeing recovery across Jira Cloud navigation services. Project sidebars are now loading as expected. Our teams continue to monitor the situation, and we expect to confirm full resolution in our next update in 1 hour or sooner.

3. resolved Oct 21, 2026, 03:45 PM UTC

   On October 21, 2026, JIRA, JSM, JPD, and JWM users may have experienced performance degradation impacting the project sidebar and navigation. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Oct 21, 2026, 02:28 PM UTC· resolved Oct 21, 2026, 03:45 PM UTC

1. investigating Oct 21, 2026, 02:28 PM UTC

   We are investigating an issue impacting the project sidebar and navigation in Jira Cloud. Users may encounter timeouts or missing menus when attempting to access project views. Teams are actively analyzing telemetry to identify a mitigation. We will provide our next update in 60 minutes, or sooner.

2. monitoring Oct 21, 2026, 03:01 PM UTC

   Mitigations are in place and we are seeing recovery across Jira Cloud navigation services. Project sidebars are now loading as expected. Our teams continue to monitor the situation, and we expect to confirm full resolution in our next update in 1 hour or sooner.

3. resolved Oct 21, 2026, 03:45 PM UTC

   On October 21, 2026, JIRA, JSM, JPD, and JWM users may have experienced performance degradation impacting the project sidebar and navigation. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Oct 21, 2026, 02:28 PM UTC· resolved Oct 21, 2026, 03:45 PM UTC

1. investigating Oct 21, 2026, 02:28 PM UTC

   We are investigating an issue impacting the project sidebar and navigation in Jira Cloud. Users may encounter timeouts or missing menus when attempting to access project views. Teams are actively analyzing telemetry to identify a mitigation. We will provide our next update in 60 minutes, or sooner.

2. monitoring Oct 21, 2026, 03:01 PM UTC

   Mitigations are in place and we are seeing recovery across Jira Cloud navigation services. Project sidebars are now loading as expected. Our teams continue to monitor the situation, and we expect to confirm full resolution in our next update in 1 hour or sooner.

3. resolved Oct 21, 2026, 03:45 PM UTC

   On October 21, 2026, JIRA, JSM, JPD, and JWM users may have experienced performance degradation impacting the project sidebar and navigation. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Oct 21, 2026, 02:28 PM UTC· resolved Oct 21, 2026, 03:45 PM UTC

1. investigating Oct 21, 2026, 02:28 PM UTC

   We are investigating an issue impacting the project sidebar and navigation in Jira Cloud. Users may encounter timeouts or missing menus when attempting to access project views. Teams are actively analyzing telemetry to identify a mitigation. We will provide our next update in 60 minutes, or sooner.

2. monitoring Oct 21, 2026, 03:01 PM UTC

   Mitigations are in place and we are seeing recovery across Jira Cloud navigation services. Project sidebars are now loading as expected. Our teams continue to monitor the situation, and we expect to confirm full resolution in our next update in 1 hour or sooner.

3. resolved Oct 21, 2026, 03:45 PM UTC

   On October 21, 2026, JIRA, JSM, JPD, and JWM users may have experienced performance degradation impacting the project sidebar and navigation. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Oct 21, 2026, 02:28 PM UTC· resolved Oct 21, 2026, 03:45 PM UTC

1. investigating Oct 21, 2026, 02:28 PM UTC

   We are investigating an issue impacting the project sidebar and navigation in Jira Cloud. Users may encounter timeouts or missing menus when attempting to access project views. Teams are actively analyzing telemetry to identify a mitigation. We will provide our next update in 60 minutes, or sooner.

2. monitoring Oct 21, 2026, 03:01 PM UTC

   Mitigations are in place and we are seeing recovery across Jira Cloud navigation services. Project sidebars are now loading as expected. Our teams continue to monitor the situation, and we expect to confirm full resolution in our next update in 1 hour or sooner.

3. resolved Oct 21, 2026, 03:45 PM UTC

   On October 21, 2026, JIRA, JSM, JPD, and JWM users may have experienced performance degradation impacting the project sidebar and navigation. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Oct 15, 2026, 02:22 PM UTC· resolved Oct 15, 2026, 05:08 PM UTC

1. investigating Oct 15, 2026, 02:22 PM UTC

   We are investigating reports of an issue affecting select Marketplace apps across our cloud products. Users may experience intermittent errors or delays with affected webhooks functionality of apps. Our teams are actively analysing the issue, and we will provide our next update in 60 minutes or sooner.

2. monitoring Oct 15, 2026, 03:23 PM UTC

   We have applied mitigations to resolve the disruption affecting select Marketplace apps. We are observing positive signs of recovery across app operations, though minor intermittent delays may persist as traffic stabilises. Teams remain engaged and are actively monitoring the environment to ensure full service restoration. We will share our next update in 60 minutes or sooner.

3. monitoring Oct 15, 2026, 04:19 PM UTC

   Recovery continues across app operations, although some users may experience intermittent delays. We will continue to share additional updates here as more information becomes available.

4. resolved Oct 15, 2026, 05:08 PM UTC

   On October 15, 2026, Marketplace app users in EU-West region may have experienced performance degradation. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Oct 15, 2026, 10:07 AM UTC· resolved Oct 15, 2026, 12:08 PM UTC

1. investigating Oct 15, 2026, 10:07 AM UTC

   We are actively investigating an issue affecting Bitbucket Cloud. Impacted users may experience connection errors, timeouts, or an inability to access the Bitbucket web interface and Pipelines. Our teams are actively investigating the cause to mitigate the impact and restore service as quickly as possible. We will provide our next update within 30 minutes, or sooner if there is a material update.

2. investigating Oct 15, 2026, 10:49 AM UTC

   We continue to actively investigate the issue impacting Bitbucket Cloud. Affected users may still experience errors, timeouts, or difficulty accessing the web interface, and Pipelines. Our teams are working through several recovery paths to mitigate the impact and restore full platform availability as quickly as possible. We will provide our next update in 60 minutes, or sooner.

3. monitoring Oct 15, 2026, 11:49 AM UTC

   A fix has been implemented, and core services have recovered. The Bitbucket-pipelines is currently clearing backlogged builds and continuing to recover. We are monitoring performance closely before declaring full resolution. Next update in 60 minutes, or sooner.

4. resolved Oct 15, 2026, 12:08 PM UTC

   On October 15th, 2026, between 10:42 UTC to 11:14 UTC, some Bitbucket Cloud users may have experienced disruptions accessing the web interface and running Pipelines. The issue has now been resolved and the service is operating normally for all the customers.

Read the full incident report →

Started Oct 01, 2026, 07:01 AM UTC· resolved Oct 01, 2026, 07:51 AM UTC

1. identified Oct 01, 2026, 07:01 AM UTC

   Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. There is also an impact to the new support tickets created in terms of missing SLA component, notifications which may be affecting the response times and backlog management of some tickets.

2. resolved Oct 01, 2026, 07:51 AM UTC

   On 01st Oct 2026, between 01:00 UTC and 07:25 UTC, users may have seen missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected. We have now implemented a fix and and services have been restored to normal operation for affected customers. The impact to support tickets with missing SLA component and delayed notifications have also confirmed recovery. Note: For Bitbucket customers, if there was any scheduled pipelines that did not run during the incident window, you may wait for the next scheduled execution or trigger them manually.

3. postmortem Oct 09, 2026, 06:24 PM UTC

   ### Summary On October 1, 2026, between 01:00 and 07:25 UTC, degraded job processing and scheduling impacted Atlassian products including Bitbucket Cloud, Confluence, Forge apps, Jira, and Jira Service Management in all commercial cloud regions. This caused delayed or missed background tasks, such as email-to-ticket processing and scheduled pipelines; interactive product use was not affected. The event was triggered when an unexpected volume of scheduled tasks became due simultaneously, overwhelming our shared job scheduling platform. Automated monitoring detected the incident within three minutes. Recovery began around 03:45 UTC as engineering scaled capacity and the platform worked through the backlog, with full resolution reached in 6 hours and 25 minutes. ### IMPACT Most scheduled tasks stopped running at 01:00 UTC and resumed from about 03:45 UTC. Most delayed work had caught up by about 06:00 UTC, and the remaining delays had cleared by 07:25 UTC. Across affected products: - Recurring scheduled tasks skipped or delayed runs due during the incident; skipped runs were not automatically re-run, and tasks resumed at their next scheduled time. - Most one-time scheduled tasks ran late; a small number may not have run. - Automation rules, including scheduled rules, ran normally, except as noted below. Bitbucket Cloud Scheduled pipelines due between 01:00 and about 03:50 UTC did not run. If a scheduled pipeline did not run during the incident, you can wait for the next scheduled execution or trigger it manually. Other pipeline runs were not affected. Confluence Some calendar event reminders due between 01:00 and about 03:45 UTC were not sent. Forge apps Scheduled triggers stopped at 01:00 UTC and resumed from about 04:00 UTC; missed invocations were not replayed. Goals Start of the month email reminders to update goals could be delayed. Jira and Jira Service Management Incoming emails stayed in their mailboxes and were processed automatically after recovery. Scheduled notifications, such as filter subscriptions, were delayed. In some service projects, automation rules and notifications triggered by SLAs or time in status ran late. SLA timer data remained intact. Atlassian Support Until 07:25 UTC, issues with our support tools may have slowed some of our responses. Based on our investigation to date, we have not identified any loss of work items, pages, repositories, or incoming emails. ### ROOT CAUSE Our shared job scheduling platform operates at high scale under normal conditions. One of the platform consumers scheduled an abnormally high volume of tasks to be executed at the same time on October 1st at 01:00 UTC. This order-of-magnitude surge exceeded our architectural and scaling limits, creating a processing backlog across dependent services. Engineering manually increased capacity to handle the abnormal load, enabling the service to process the backlog and return to normal operations. ### REMEDIAL ACTIONS PLAN & NEXT STEPS We know that delayed and missed work affects your productivity. We are prioritizing these actions to help reduce the likelihood and impact of similar incidents: - **Enhance workload isolation:** Implement fair scheduling guardrails so volume surges from a single source do not starve or delay tasks across other products. - **Strengthen surge controls:** Add operational capabilities to quickly throttle or pause scheduled workloads from specific sources during unexpected traffic spikes. - **Improve system scaling and recovery:** Enhance platform capacity and optimize scaling processes to handle extreme demand spikes and recover more rapidly. We apologize to customers whose services were impacted during this incident. Thanks, Atlassian

Read the full incident report →

Started Oct 01, 2026, 04:03 AM UTC· resolved Oct 01, 2026, 07:51 AM UTC

1. identified Oct 01, 2026, 04:03 AM UTC

   Our teams have taken corrective steps to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered.

2. identified Oct 01, 2026, 05:00 AM UTC

   Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. Along with impact to scheduled and asynchronous work across several products, we also identified SLA component in Jira Service Management is not appearing as expected.

3. identified Oct 01, 2026, 07:01 AM UTC

   Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. There is also an impact to the new support tickets created in terms of missing SLA component, notifications which may be affecting the response times and backlog management of some tickets.

4. resolved Oct 01, 2026, 07:51 AM UTC

   On 01st Oct 2026, between 01:00 UTC and 07:25 UTC, users may have seen missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected. We have now implemented a fix and and services have been restored to normal operation for affected customers. The impact to support tickets with missing SLA component and delayed notifications have also confirmed recovery. Note: For Bitbucket customers, if there was any scheduled pipelines that did not run during the incident window, you may wait for the next scheduled execution or trigger them manually.

5. postmortem Oct 09, 2026, 06:24 PM UTC

   ### Summary On October 1, 2026, between 01:00 and 07:25 UTC, degraded job processing and scheduling impacted Atlassian products including Bitbucket Cloud, Confluence, Forge apps, Jira, and Jira Service Management in all commercial cloud regions. This caused delayed or missed background tasks, such as email-to-ticket processing and scheduled pipelines; interactive product use was not affected. The event was triggered when an unexpected volume of scheduled tasks became due simultaneously, overwhelming our shared job scheduling platform. Automated monitoring detected the incident within three minutes. Recovery began around 03:45 UTC as engineering scaled capacity and the platform worked through the backlog, with full resolution reached in 6 hours and 25 minutes. ### IMPACT Most scheduled tasks stopped running at 01:00 UTC and resumed from about 03:45 UTC. Most delayed work had caught up by about 06:00 UTC, and the remaining delays had cleared by 07:25 UTC. Across affected products: - Recurring scheduled tasks skipped or delayed runs due during the incident; skipped runs were not automatically re-run, and tasks resumed at their next scheduled time. - Most one-time scheduled tasks ran late; a small number may not have run. - Automation rules, including scheduled rules, ran normally, except as noted below. Bitbucket Cloud Scheduled pipelines due between 01:00 and about 03:50 UTC did not run. If a scheduled pipeline did not run during the incident, you can wait for the next scheduled execution or trigger it manually. Other pipeline runs were not affected. Confluence Some calendar event reminders due between 01:00 and about 03:45 UTC were not sent. Forge apps Scheduled triggers stopped at 01:00 UTC and resumed from about 04:00 UTC; missed invocations were not replayed. Goals Start of the month email reminders to update goals could be delayed. Jira and Jira Service Management Incoming emails stayed in their mailboxes and were processed automatically after recovery. Scheduled notifications, such as filter subscriptions, were delayed. In some service projects, automation rules and notifications triggered by SLAs or time in status ran late. SLA timer data remained intact. Atlassian Support Until 07:25 UTC, issues with our support tools may have slowed some of our responses. Based on our investigation to date, we have not identified any loss of work items, pages, repositories, or incoming emails. ### ROOT CAUSE Our shared job scheduling platform operates at high scale under normal conditions. One of the platform consumers scheduled an abnormally high volume of tasks to be executed at the same time on October 1st at 01:00 UTC. This order-of-magnitude surge exceeded our architectural and scaling limits, creating a processing backlog across dependent services. Engineering manually increased capacity to handle the abnormal load, enabling the service to process the backlog and return to normal operations. ### REMEDIAL ACTIONS PLAN & NEXT STEPS We know that delayed and missed work affects your productivity. We are prioritizing these actions to help reduce the likelihood and impact of similar incidents: - **Enhance workload isolation:** Implement fair scheduling guardrails so volume surges from a single source do not starve or delay tasks across other products. - **Strengthen surge controls:** Add operational capabilities to quickly throttle or pause scheduled workloads from specific sources during unexpected traffic spikes. - **Improve system scaling and recovery:** Enhance platform capacity and optimize scaling processes to handle extreme demand spikes and recover more rapidly. We apologize to customers whose services were impacted during this incident. Thanks, Atlassian

Read the full incident report →

Started Oct 01, 2026, 02:55 AM UTC· resolved Oct 01, 2026, 07:51 AM UTC

1. investigating Oct 01, 2026, 02:55 AM UTC

   Job processing and job scheduling is degraded, which is affecting scheduled and asynchronous work across several products, including Jira, Confluence and Bitbucket Cloud. Affected users may see delayed or missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected.

2. identified Oct 01, 2026, 03:47 AM UTC

   Our teams have identified the root cause of this incident and is now actively working on mitigating the issue. We will provide further updates within an hour or sooner if we have any significant progress to share.

3. identified Oct 01, 2026, 04:03 AM UTC

   Our teams have taken corrective steps to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered.

4. identified Oct 01, 2026, 05:00 AM UTC

   Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. Along with impact to scheduled and asynchronous work across several products, we also identified SLA component in Jira Service Management is not appearing as expected.

5. identified Oct 01, 2026, 07:01 AM UTC

   Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. There is also an impact to the new support tickets created in terms of missing SLA component, notifications which may be affecting the response times and backlog management of some tickets.

6. resolved Oct 01, 2026, 07:51 AM UTC

   On 01st Oct 2026, between 01:00 UTC and 07:25 UTC, users may have seen missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected. We have now implemented a fix and and services have been restored to normal operation for affected customers. The impact to support tickets with missing SLA component and delayed notifications have also confirmed recovery. Note: For Bitbucket customers, if there was any scheduled pipelines that did not run during the incident window, you may wait for the next scheduled execution or trigger them manually.

7. postmortem Oct 09, 2026, 06:24 PM UTC

   ### Summary On October 1, 2026, between 01:00 and 07:25 UTC, degraded job processing and scheduling impacted Atlassian products including Bitbucket Cloud, Confluence, Forge apps, Jira, and Jira Service Management in all commercial cloud regions. This caused delayed or missed background tasks, such as email-to-ticket processing and scheduled pipelines; interactive product use was not affected. The event was triggered when an unexpected volume of scheduled tasks became due simultaneously, overwhelming our shared job scheduling platform. Automated monitoring detected the incident within three minutes. Recovery began around 03:45 UTC as engineering scaled capacity and the platform worked through the backlog, with full resolution reached in 6 hours and 25 minutes. ### IMPACT Most scheduled tasks stopped running at 01:00 UTC and resumed from about 03:45 UTC. Most delayed work had caught up by about 06:00 UTC, and the remaining delays had cleared by 07:25 UTC. Across affected products: - Recurring scheduled tasks skipped or delayed runs due during the incident; skipped runs were not automatically re-run, and tasks resumed at their next scheduled time. - Most one-time scheduled tasks ran late; a small number may not have run. - Automation rules, including scheduled rules, ran normally, except as noted below. Bitbucket Cloud Scheduled pipelines due between 01:00 and about 03:50 UTC did not run. If a scheduled pipeline did not run during the incident, you can wait for the next scheduled execution or trigger it manually. Other pipeline runs were not affected. Confluence Some calendar event reminders due between 01:00 and about 03:45 UTC were not sent. Forge apps Scheduled triggers stopped at 01:00 UTC and resumed from about 04:00 UTC; missed invocations were not replayed. Goals Start of the month email reminders to update goals could be delayed. Jira and Jira Service Management Incoming emails stayed in their mailboxes and were processed automatically after recovery. Scheduled notifications, such as filter subscriptions, were delayed. In some service projects, automation rules and notifications triggered by SLAs or time in status ran late. SLA timer data remained intact. Atlassian Support Until 07:25 UTC, issues with our support tools may have slowed some of our responses. Based on our investigation to date, we have not identified any loss of work items, pages, repositories, or incoming emails. ### ROOT CAUSE Our shared job scheduling platform operates at high scale under normal conditions. One of the platform consumers scheduled an abnormally high volume of tasks to be executed at the same time on October 1st at 01:00 UTC. This order-of-magnitude surge exceeded our architectural and scaling limits, creating a processing backlog across dependent services. Engineering manually increased capacity to handle the abnormal load, enabling the service to process the backlog and return to normal operations. ### REMEDIAL ACTIONS PLAN & NEXT STEPS We know that delayed and missed work affects your productivity. We are prioritizing these actions to help reduce the likelihood and impact of similar incidents: - **Enhance workload isolation:** Implement fair scheduling guardrails so volume surges from a single source do not starve or delay tasks across other products. - **Strengthen surge controls:** Add operational capabilities to quickly throttle or pause scheduled workloads from specific sources during unexpected traffic spikes. - **Improve system scaling and recovery:** Enhance platform capacity and optimize scaling processes to handle extreme demand spikes and recover more rapidly. We apologize to customers whose services were impacted during this incident. Thanks, Atlassian

Read the full incident report →

Started Oct 01, 2026, 02:55 AM UTC· resolved Oct 01, 2026, 07:51 AM UTC

1. investigating Oct 01, 2026, 02:55 AM UTC

   Job processing and job scheduling is degraded, which is affecting scheduled and asynchronous work across several products, including Jira, Confluence and Bitbucket Cloud. Affected users may see delayed or missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected.

2. identified Oct 01, 2026, 03:47 AM UTC

   Our teams have identified the root cause of this incident and is now actively working on mitigating the issue. We will provide further updates within an hour or sooner if we have any significant progress to share.

3. identified Oct 01, 2026, 04:03 AM UTC

   Our teams have taken corrective steps to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered.

4. identified Oct 01, 2026, 05:00 AM UTC

   Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. Along with impact to scheduled and asynchronous work across several products, we also identified SLA component in Jira Service Management is not appearing as expected.

5. identified Oct 01, 2026, 07:01 AM UTC

   Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. There is also an impact to the new support tickets created in terms of missing SLA component, notifications which may be affecting the response times and backlog management of some tickets.

6. resolved Oct 01, 2026, 07:51 AM UTC

   On 01st Oct 2026, between 01:00 UTC and 07:25 UTC, users may have seen missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected. We have now implemented a fix and and services have been restored to normal operation for affected customers. The impact to support tickets with missing SLA component and delayed notifications have also confirmed recovery. Note: For Bitbucket customers, if there was any scheduled pipelines that did not run during the incident window, you may wait for the next scheduled execution or trigger them manually.

7. postmortem Oct 09, 2026, 06:24 PM UTC

   ### Summary On October 1, 2026, between 01:00 and 07:25 UTC, degraded job processing and scheduling impacted Atlassian products including Bitbucket Cloud, Confluence, Forge apps, Jira, and Jira Service Management in all commercial cloud regions. This caused delayed or missed background tasks, such as email-to-ticket processing and scheduled pipelines; interactive product use was not affected. The event was triggered when an unexpected volume of scheduled tasks became due simultaneously, overwhelming our shared job scheduling platform. Automated monitoring detected the incident within three minutes. Recovery began around 03:45 UTC as engineering scaled capacity and the platform worked through the backlog, with full resolution reached in 6 hours and 25 minutes. ### IMPACT Most scheduled tasks stopped running at 01:00 UTC and resumed from about 03:45 UTC. Most delayed work had caught up by about 06:00 UTC, and the remaining delays had cleared by 07:25 UTC. Across affected products: - Recurring scheduled tasks skipped or delayed runs due during the incident; skipped runs were not automatically re-run, and tasks resumed at their next scheduled time. - Most one-time scheduled tasks ran late; a small number may not have run. - Automation rules, including scheduled rules, ran normally, except as noted below. Bitbucket Cloud Scheduled pipelines due between 01:00 and about 03:50 UTC did not run. If a scheduled pipeline did not run during the incident, you can wait for the next scheduled execution or trigger it manually. Other pipeline runs were not affected. Confluence Some calendar event reminders due between 01:00 and about 03:45 UTC were not sent. Forge apps Scheduled triggers stopped at 01:00 UTC and resumed from about 04:00 UTC; missed invocations were not replayed. Goals Start of the month email reminders to update goals could be delayed. Jira and Jira Service Management Incoming emails stayed in their mailboxes and were processed automatically after recovery. Scheduled notifications, such as filter subscriptions, were delayed. In some service projects, automation rules and notifications triggered by SLAs or time in status ran late. SLA timer data remained intact. Atlassian Support Until 07:25 UTC, issues with our support tools may have slowed some of our responses. Based on our investigation to date, we have not identified any loss of work items, pages, repositories, or incoming emails. ### ROOT CAUSE Our shared job scheduling platform operates at high scale under normal conditions. One of the platform consumers scheduled an abnormally high volume of tasks to be executed at the same time on October 1st at 01:00 UTC. This order-of-magnitude surge exceeded our architectural and scaling limits, creating a processing backlog across dependent services. Engineering manually increased capacity to handle the abnormal load, enabling the service to process the backlog and return to normal operations. ### REMEDIAL ACTIONS PLAN & NEXT STEPS We know that delayed and missed work affects your productivity. We are prioritizing these actions to help reduce the likelihood and impact of similar incidents: - **Enhance workload isolation:** Implement fair scheduling guardrails so volume surges from a single source do not starve or delay tasks across other products. - **Strengthen surge controls:** Add operational capabilities to quickly throttle or pause scheduled workloads from specific sources during unexpected traffic spikes. - **Improve system scaling and recovery:** Enhance platform capacity and optimize scaling processes to handle extreme demand spikes and recover more rapidly. We apologize to customers whose services were impacted during this incident. Thanks, Atlassian

Read the full incident report →

Started Oct 01, 2026, 02:55 AM UTC· resolved Oct 01, 2026, 07:51 AM UTC

1. investigating Oct 01, 2026, 02:55 AM UTC

   Job processing and job scheduling is degraded, which is affecting scheduled and asynchronous work across several products, including Jira, Confluence and Bitbucket Cloud. Affected users may see delayed or missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected.

2. identified Oct 01, 2026, 03:47 AM UTC

   Our teams have identified the root cause of this incident and is now actively working on mitigating the issue. We will provide further updates within an hour or sooner if we have any significant progress to share.

3. identified Oct 01, 2026, 04:03 AM UTC

   Our teams have taken corrective steps to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered.

4. identified Oct 01, 2026, 05:00 AM UTC

   Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. Along with impact to scheduled and asynchronous work across several products, we also identified SLA component in Jira Service Management is not appearing as expected.

5. identified Oct 01, 2026, 07:01 AM UTC

   Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. There is also an impact to the new support tickets created in terms of missing SLA component, notifications which may be affecting the response times and backlog management of some tickets.

6. resolved Oct 01, 2026, 07:51 AM UTC

   On 01st Oct 2026, between 01:00 UTC and 07:25 UTC, users may have seen missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected. We have now implemented a fix and and services have been restored to normal operation for affected customers. The impact to support tickets with missing SLA component and delayed notifications have also confirmed recovery. Note: For Bitbucket customers, if there was any scheduled pipelines that did not run during the incident window, you may wait for the next scheduled execution or trigger them manually.

7. postmortem Oct 09, 2026, 06:24 PM UTC

   ### Summary On October 1, 2026, between 01:00 and 07:25 UTC, degraded job processing and scheduling impacted Atlassian products including Bitbucket Cloud, Confluence, Forge apps, Jira, and Jira Service Management in all commercial cloud regions. This caused delayed or missed background tasks, such as email-to-ticket processing and scheduled pipelines; interactive product use was not affected. The event was triggered when an unexpected volume of scheduled tasks became due simultaneously, overwhelming our shared job scheduling platform. Automated monitoring detected the incident within three minutes. Recovery began around 03:45 UTC as engineering scaled capacity and the platform worked through the backlog, with full resolution reached in 6 hours and 25 minutes. ### IMPACT Most scheduled tasks stopped running at 01:00 UTC and resumed from about 03:45 UTC. Most delayed work had caught up by about 06:00 UTC, and the remaining delays had cleared by 07:25 UTC. Across affected products: - Recurring scheduled tasks skipped or delayed runs due during the incident; skipped runs were not automatically re-run, and tasks resumed at their next scheduled time. - Most one-time scheduled tasks ran late; a small number may not have run. - Automation rules, including scheduled rules, ran normally, except as noted below. Bitbucket Cloud Scheduled pipelines due between 01:00 and about 03:50 UTC did not run. If a scheduled pipeline did not run during the incident, you can wait for the next scheduled execution or trigger it manually. Other pipeline runs were not affected. Confluence Some calendar event reminders due between 01:00 and about 03:45 UTC were not sent. Forge apps Scheduled triggers stopped at 01:00 UTC and resumed from about 04:00 UTC; missed invocations were not replayed. Goals Start of the month email reminders to update goals could be delayed. Jira and Jira Service Management Incoming emails stayed in their mailboxes and were processed automatically after recovery. Scheduled notifications, such as filter subscriptions, were delayed. In some service projects, automation rules and notifications triggered by SLAs or time in status ran late. SLA timer data remained intact. Atlassian Support Until 07:25 UTC, issues with our support tools may have slowed some of our responses. Based on our investigation to date, we have not identified any loss of work items, pages, repositories, or incoming emails. ### ROOT CAUSE Our shared job scheduling platform operates at high scale under normal conditions. One of the platform consumers scheduled an abnormally high volume of tasks to be executed at the same time on October 1st at 01:00 UTC. This order-of-magnitude surge exceeded our architectural and scaling limits, creating a processing backlog across dependent services. Engineering manually increased capacity to handle the abnormal load, enabling the service to process the backlog and return to normal operations. ### REMEDIAL ACTIONS PLAN & NEXT STEPS We know that delayed and missed work affects your productivity. We are prioritizing these actions to help reduce the likelihood and impact of similar incidents: - **Enhance workload isolation:** Implement fair scheduling guardrails so volume surges from a single source do not starve or delay tasks across other products. - **Strengthen surge controls:** Add operational capabilities to quickly throttle or pause scheduled workloads from specific sources during unexpected traffic spikes. - **Improve system scaling and recovery:** Enhance platform capacity and optimize scaling processes to handle extreme demand spikes and recover more rapidly. We apologize to customers whose services were impacted during this incident. Thanks, Atlassian

Read the full incident report →

Started Oct 01, 2026, 02:55 AM UTC· resolved Oct 01, 2026, 07:51 AM UTC

1. investigating Oct 01, 2026, 02:55 AM UTC

   Job processing and job scheduling is degraded, which is affecting scheduled and asynchronous work across several products, including Jira, Confluence and Bitbucket Cloud. Affected users may see delayed or missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected.

2. identified Oct 01, 2026, 03:47 AM UTC

   Our teams have identified the root cause of this incident and is now actively working on mitigating the issue. We will provide further updates within an hour or sooner if we have any significant progress to share.

3. identified Oct 01, 2026, 04:03 AM UTC

   Our teams have taken corrective steps to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered.

4. identified Oct 01, 2026, 05:00 AM UTC

   Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. Along with impact to scheduled and asynchronous work across several products, we also identified SLA component in Jira Service Management is not appearing as expected.

5. identified Oct 01, 2026, 07:01 AM UTC

   Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. There is also an impact to the new support tickets created in terms of missing SLA component, notifications which may be affecting the response times and backlog management of some tickets.

6. resolved Oct 01, 2026, 07:51 AM UTC

   On 01st Oct 2026, between 01:00 UTC and 07:25 UTC, users may have seen missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected. We have now implemented a fix and and services have been restored to normal operation for affected customers. The impact to support tickets with missing SLA component and delayed notifications have also confirmed recovery. Note: For Bitbucket customers, if there was any scheduled pipelines that did not run during the incident window, you may wait for the next scheduled execution or trigger them manually.

7. postmortem Oct 09, 2026, 06:24 PM UTC

   ### Summary On October 1, 2026, between 01:00 and 07:25 UTC, degraded job processing and scheduling impacted Atlassian products including Bitbucket Cloud, Confluence, Forge apps, Jira, and Jira Service Management in all commercial cloud regions. This caused delayed or missed background tasks, such as email-to-ticket processing and scheduled pipelines; interactive product use was not affected. The event was triggered when an unexpected volume of scheduled tasks became due simultaneously, overwhelming our shared job scheduling platform. Automated monitoring detected the incident within three minutes. Recovery began around 03:45 UTC as engineering scaled capacity and the platform worked through the backlog, with full resolution reached in 6 hours and 25 minutes. ### IMPACT Most scheduled tasks stopped running at 01:00 UTC and resumed from about 03:45 UTC. Most delayed work had caught up by about 06:00 UTC, and the remaining delays had cleared by 07:25 UTC. Across affected products: - Recurring scheduled tasks skipped or delayed runs due during the incident; skipped runs were not automatically re-run, and tasks resumed at their next scheduled time. - Most one-time scheduled tasks ran late; a small number may not have run. - Automation rules, including scheduled rules, ran normally, except as noted below. Bitbucket Cloud Scheduled pipelines due between 01:00 and about 03:50 UTC did not run. If a scheduled pipeline did not run during the incident, you can wait for the next scheduled execution or trigger it manually. Other pipeline runs were not affected. Confluence Some calendar event reminders due between 01:00 and about 03:45 UTC were not sent. Forge apps Scheduled triggers stopped at 01:00 UTC and resumed from about 04:00 UTC; missed invocations were not replayed. Goals Start of the month email reminders to update goals could be delayed. Jira and Jira Service Management Incoming emails stayed in their mailboxes and were processed automatically after recovery. Scheduled notifications, such as filter subscriptions, were delayed. In some service projects, automation rules and notifications triggered by SLAs or time in status ran late. SLA timer data remained intact. Atlassian Support Until 07:25 UTC, issues with our support tools may have slowed some of our responses. Based on our investigation to date, we have not identified any loss of work items, pages, repositories, or incoming emails. ### ROOT CAUSE Our shared job scheduling platform operates at high scale under normal conditions. One of the platform consumers scheduled an abnormally high volume of tasks to be executed at the same time on October 1st at 01:00 UTC. This order-of-magnitude surge exceeded our architectural and scaling limits, creating a processing backlog across dependent services. Engineering manually increased capacity to handle the abnormal load, enabling the service to process the backlog and return to normal operations. ### REMEDIAL ACTIONS PLAN & NEXT STEPS We know that delayed and missed work affects your productivity. We are prioritizing these actions to help reduce the likelihood and impact of similar incidents: - **Enhance workload isolation:** Implement fair scheduling guardrails so volume surges from a single source do not starve or delay tasks across other products. - **Strengthen surge controls:** Add operational capabilities to quickly throttle or pause scheduled workloads from specific sources during unexpected traffic spikes. - **Improve system scaling and recovery:** Enhance platform capacity and optimize scaling processes to handle extreme demand spikes and recover more rapidly. We apologize to customers whose services were impacted during this incident. Thanks, Atlassian

Read the full incident report →

Started Oct 01, 2026, 02:55 AM UTC· resolved Oct 01, 2026, 07:51 AM UTC

1. investigating Oct 01, 2026, 02:55 AM UTC

   Job processing and job scheduling is degraded, which is affecting scheduled and asynchronous work across several products, including Jira, Confluence and Bitbucket Cloud. Affected users may see delayed or missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected.

2. identified Oct 01, 2026, 03:47 AM UTC

   Our teams have identified the root cause of this incident and is now actively working on mitigating the issue. We will provide further updates within an hour or sooner if we have any significant progress to share.

3. identified Oct 01, 2026, 04:03 AM UTC

   Our teams have taken corrective steps to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered.

4. identified Oct 01, 2026, 05:00 AM UTC

   Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. Along with impact to scheduled and asynchronous work across several products, we also identified SLA component in Jira Service Management is not appearing as expected.

5. identified Oct 01, 2026, 07:01 AM UTC

   Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. There is also an impact to the new support tickets created in terms of missing SLA component, notifications which may be affecting the response times and backlog management of some tickets.

6. resolved Oct 01, 2026, 07:51 AM UTC

   On 01st Oct 2026, between 01:00 UTC and 07:25 UTC, users may have seen missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected. We have now implemented a fix and and services have been restored to normal operation for affected customers. The impact to support tickets with missing SLA component and delayed notifications have also confirmed recovery. Note: For Bitbucket customers, if there was any scheduled pipelines that did not run during the incident window, you may wait for the next scheduled execution or trigger them manually.

7. postmortem Oct 09, 2026, 06:24 PM UTC

   ### Summary On October 1, 2026, between 01:00 and 07:25 UTC, degraded job processing and scheduling impacted Atlassian products including Bitbucket Cloud, Confluence, Forge apps, Jira, and Jira Service Management in all commercial cloud regions. This caused delayed or missed background tasks, such as email-to-ticket processing and scheduled pipelines; interactive product use was not affected. The event was triggered when an unexpected volume of scheduled tasks became due simultaneously, overwhelming our shared job scheduling platform. Automated monitoring detected the incident within three minutes. Recovery began around 03:45 UTC as engineering scaled capacity and the platform worked through the backlog, with full resolution reached in 6 hours and 25 minutes. ### IMPACT Most scheduled tasks stopped running at 01:00 UTC and resumed from about 03:45 UTC. Most delayed work had caught up by about 06:00 UTC, and the remaining delays had cleared by 07:25 UTC. Across affected products: - Recurring scheduled tasks skipped or delayed runs due during the incident; skipped runs were not automatically re-run, and tasks resumed at their next scheduled time. - Most one-time scheduled tasks ran late; a small number may not have run. - Automation rules, including scheduled rules, ran normally, except as noted below. Bitbucket Cloud Scheduled pipelines due between 01:00 and about 03:50 UTC did not run. If a scheduled pipeline did not run during the incident, you can wait for the next scheduled execution or trigger it manually. Other pipeline runs were not affected. Confluence Some calendar event reminders due between 01:00 and about 03:45 UTC were not sent. Forge apps Scheduled triggers stopped at 01:00 UTC and resumed from about 04:00 UTC; missed invocations were not replayed. Goals Start of the month email reminders to update goals could be delayed. Jira and Jira Service Management Incoming emails stayed in their mailboxes and were processed automatically after recovery. Scheduled notifications, such as filter subscriptions, were delayed. In some service projects, automation rules and notifications triggered by SLAs or time in status ran late. SLA timer data remained intact. Atlassian Support Until 07:25 UTC, issues with our support tools may have slowed some of our responses. Based on our investigation to date, we have not identified any loss of work items, pages, repositories, or incoming emails. ### ROOT CAUSE Our shared job scheduling platform operates at high scale under normal conditions. One of the platform consumers scheduled an abnormally high volume of tasks to be executed at the same time on October 1st at 01:00 UTC. This order-of-magnitude surge exceeded our architectural and scaling limits, creating a processing backlog across dependent services. Engineering manually increased capacity to handle the abnormal load, enabling the service to process the backlog and return to normal operations. ### REMEDIAL ACTIONS PLAN & NEXT STEPS We know that delayed and missed work affects your productivity. We are prioritizing these actions to help reduce the likelihood and impact of similar incidents: - **Enhance workload isolation:** Implement fair scheduling guardrails so volume surges from a single source do not starve or delay tasks across other products. - **Strengthen surge controls:** Add operational capabilities to quickly throttle or pause scheduled workloads from specific sources during unexpected traffic spikes. - **Improve system scaling and recovery:** Enhance platform capacity and optimize scaling processes to handle extreme demand spikes and recover more rapidly. We apologize to customers whose services were impacted during this incident. Thanks, Atlassian

Read the full incident report →

Started Sep 28, 2026, 06:48 AM UTC· resolved Sep 28, 2026, 07:59 AM UTC

1. investigating Sep 28, 2026, 06:48 AM UTC

   Impact Marketplace app publishing is failing for some users in the Marketplace console. Affected users may see a generic Version publish failed message when trying to make a new app or app version public. Dozens of app publish attempts have been affected. Current Status The team is working to restore the approval flow used by the Marketplace console and is validating the service after redeployment. The issue is being investigated alongside recent changes made in internal support services. Next Steps Next communication will be sent in 60 minutes, or sooner if there is a significant update.

2. resolved Sep 28, 2026, 07:59 AM UTC

   The issue impacting Marketplace app and version publishing in the Atlassian Marketplace has been resolved. The publishing and approval workflows are now fully restored, and all services are operating normally. Root Cause: During scheduled maintenance over the weekend, the Marketplace app publishing workflow was impacted due to a service account permission issue that prevented automated ticket creation required for approvals. The necessary permissions have since been restored, and the app publishing and submission flows are now operating normally. Impact Window: Start: 12:30 AM UTC (28 Sep 2026) End: 07:30 AM UTC (28 Sep 2026) Next Steps for Affected Users: If you previously encountered a Version publish failed error, please retry publishing your app version now. If you continue to experience any issues, please reach out to our team at Developer and marketplace support https://developer.atlassian.com/support . Thank you for your patience and understanding while we resolved this issue.

Read the full incident report →

Started Sep 24, 2026, 01:54 PM UTC· resolved Sep 24, 2026, 03:53 PM UTC

1. investigating Sep 24, 2026, 01:54 PM UTC

   We continue to investigate the issue impacting Jira issue creation, issue viewing, and board loading. Our teams remain engaged on identifying a resolution. We will provide the next update in 1 hour, or sooner if there is material progress.

2. monitoring Sep 24, 2026, 02:58 PM UTC

   Mitigations have been deployed and we are seeing positive signs of recovery across Jira. Issues viewing work items, loading boards, and creating tickets are subsiding. We are continuing to monitor system health to ensure full stability and will share our next update within 60 minutes.

3. resolved Sep 24, 2026, 03:53 PM UTC

   On September 24th 2026, some Jira and JSM users in the US region may have experienced a performance degradation impacting Jira issue creation, issue viewing, and board loading. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Sep 24, 2026, 01:54 PM UTC· resolved Sep 24, 2026, 03:53 PM UTC

1. investigating Sep 24, 2026, 01:54 PM UTC

   We continue to investigate the issue impacting Jira issue creation, issue viewing, and board loading. Our teams remain engaged on identifying a resolution. We will provide the next update in 1 hour, or sooner if there is material progress.

2. monitoring Sep 24, 2026, 02:58 PM UTC

   Mitigations have been deployed and we are seeing positive signs of recovery across Jira. Issues viewing work items, loading boards, and creating tickets are subsiding. We are continuing to monitor system health to ensure full stability and will share our next update within 60 minutes.

3. resolved Sep 24, 2026, 03:53 PM UTC

   On September 24th 2026, some Jira and JSM users in the US region may have experienced a performance degradation impacting Jira issue creation, issue viewing, and board loading. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Sep 24, 2026, 01:54 PM UTC· resolved Sep 24, 2026, 03:53 PM UTC

1. investigating Sep 24, 2026, 01:54 PM UTC

   We continue to investigate the issue impacting Jira issue creation, issue viewing, and board loading. Our teams remain engaged on identifying a resolution. We will provide the next update in 1 hour, or sooner if there is material progress.

2. monitoring Sep 24, 2026, 02:58 PM UTC

   Mitigations have been deployed and we are seeing positive signs of recovery across Jira. Issues viewing work items, loading boards, and creating tickets are subsiding. We are continuing to monitor system health to ensure full stability and will share our next update within 60 minutes.

3. resolved Sep 24, 2026, 03:53 PM UTC

   On September 24th 2026, some Jira and JSM users in the US region may have experienced a performance degradation impacting Jira issue creation, issue viewing, and board loading. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Sep 24, 2026, 08:52 AM UTC· resolved Sep 24, 2026, 11:46 AM UTC

1. monitoring Sep 24, 2026, 08:52 AM UTC

   We have been tracking an issue impacting Jira where users may have encountered errors or degraded performance accessing Jira and viewing issues. Mitigations are in place and we are seeing positive signs of recovery. Our teams are continuing to monitor the situation, and we expect to confirm resolution within the next 60 minutes.

2. monitoring Sep 24, 2026, 10:34 AM UTC

   We are continuing to closely monitor the situation to ensure full stability across Jira. Recovery signs remain steady. Our next update will be shared in 60 minutes, or sooner.

3. resolved Sep 24, 2026, 11:46 AM UTC

   On Sept 24th, 2026, between 07:28 to 08:08 UTC, some Jira users may have experienced errors or degraded performance when accessing Jira and viewing issues. The issue has now been resolved and the service is operating normally for all customers.

Read the full incident report →

Started Sep 23, 2026, 12:44 PM UTC· resolved Sep 23, 2026, 08:14 PM UTC

1. identified Sep 23, 2026, 12:44 PM UTC

   We have identified an issue affecting access to Jira Product Discovery community and support resources on Atlassian Community. Impacted users may encounter errors or broken links when attempting to access the Jira Product Discovery discussion group, articles, FAQs, or related documentation. Our engineering teams are actively working on a resolution. We will provide our next update in 2 hours, or as soon as we have a material update.

2. identified Sep 23, 2026, 02:41 PM UTC

   We have deployed a configuration fix, which has restored access to key Jira Product Discovery articles, FAQs, the public roadmap, and the product handbook. Our engineering team is continuing to work on resolving access for the remaining community group and discussion links. We will provide another update in 2 hours, or sooner if we make further progress.

3. identified Sep 23, 2026, 04:47 PM UTC

   Our teams continue to work on a mitigation. Affected users may experience access issues for community group and discussion links. We will continue to share additional updates here as more information becomes available.

4. identified Sep 23, 2026, 07:07 PM UTC

   Our teams have engaged a third-party vendor to mitigate the issue, and we will provide updates here as more information becomes available.

5. resolved Sep 23, 2026, 08:14 PM UTC

   On September 23, 2026, affected users may have experienced some service disruption on Atlassian Community. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Sep 17, 2026, 12:59 PM UTC· resolved Sep 17, 2026, 03:22 PM UTC

1. identified Sep 17, 2026, 12:59 PM UTC

   We have identified the cause of the issue affecting the Developer Console where app versions and statuses in the Installation tab appear outdated. Please note that app installations and auto-upgrades continue to function normally in the background; this is isolated to the display in the Developer Console. We are actively deploying a fix to correct the display. We will provide the next update in 1 - hour or sooner.

2. identified Sep 17, 2026, 01:57 PM UTC

   The fix to correct the display discrepancy in the Developer Console Installation tab remains underway. Core app installations and upgrades are unaffected. We will provide the next update in 2 hours, or sooner.

3. resolved Sep 17, 2026, 03:22 PM UTC

   On September 17, 2026, some Developer Console users may have experienced performance degradation where versions and statuses in the Installation tab were outdated. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Sep 16, 2026, 09:32 AM UTC· resolved Sep 16, 2026, 10:15 AM UTC

1. monitoring Sep 16, 2026, 09:32 AM UTC

   We have identified and resolved the underlying issue causing delays and stuck builds in Bitbucket Pipelines. System recovery is in progress, and we are actively monitoring the pipeline queues to ensure builds are processing normally. Action Recommended: If you have pipelines or builds that remain queued or are stalled, we recommend rerunning them or triggering a new build. We will continue to monitor the service closely and provide a final update once stability is confirmed.

2. resolved Sep 16, 2026, 10:15 AM UTC

   The incident affecting Bitbucket Pipelines has been fully resolved and the pipeline backlog has cleared. Pipeline scheduling and build executions are now operating normally. Note: If you have any older builds that were queued or stalled during the incident window and did not automatically resume, please re-run or trigger a new build.

Read the full incident report →