Jira Service Management Outage History

Started May 08, 2026, 01:31 AM UTC· resolved May 08, 2026, 07:45 PM UTC

1. investigating May 08, 2026, 01:31 AM UTC

   We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

2. identified May 08, 2026, 02:15 AM UTC

   We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

3. identified May 08, 2026, 03:00 AM UTC

   We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

4. identified May 08, 2026, 03:00 AM UTC

   Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

5. identified May 08, 2026, 04:10 AM UTC

   We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

6. identified May 08, 2026, 04:10 AM UTC

   Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

7. identified May 08, 2026, 04:10 AM UTC

   We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each product page.

8. monitoring May 08, 2026, 05:53 AM UTC

   The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared.

9. monitoring May 08, 2026, 08:03 AM UTC

   We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.

10. monitoring May 08, 2026, 11:12 AM UTC

    Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team. We apologise for the disruption and thank you for your patience.

11. resolved May 08, 2026, 07:45 PM UTC

    On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.

12. postmortem May 20, 2026, 06:48 AM UTC

    All dates and times below are in UTC unless stated otherwise. ### Summary On May 8, 2026 between 00:22 and 06:08, one of our hosting providers suffered a significant incident in a specific availability zone in prod-east which led to Atlassian customers experiencing degraded performance and delays of background operations and automation execution. The incident started on May 8, 2026 at 00:22 and was detected within 4 minutes by automated monitoring systems. Our teams worked to restore core access by 06:08. Final cleanup of backlogged processes and minor issues progressed in stages from there was completed iteratively by 19:15. ### **IMPACT** The primary infrastructure affected in this incident was the event processing pipeline in the prod-east region, which distributes events between Atlassian services and underpins background operations such as automation execution, search indexing, notifications, permission synchronisation. * Between 00:22 and 06:08, an infrastructure incident in our hosting provider triggered an ingestion failure in our event processing pipeline. * At 02:50, event ingestion was failed over to an unaffected availability zone, progressively restoring live event flows. * At 06:08, reliability for new ingestion in prod-east recovered to 100%. The remaining work was to drain the accumulated cross-region backlog of messages, which completed by 17:00. * By 18:48, Automation had processed their backlog of events that were created while processing **Automation** Between 00:22 and 02:50, customers with automation rules triggered by events originating from the prod-east region experienced a significant reduction in rule executions. During this window, event-triggered automation rules were not firing because the events that trigger them were not being delivered. Rule authoring, saving, and rules triggered manually, by schedules, or by webhooks were not affected. At 02:50, the event processing infrastructure failed over to an unaffected availability zone, restoring delivery of live events to Automation and allowing new event-triggered rules to begin executing normally. However, events generated during the impact window still needed to be replayed before delayed automations could be processed. Beginning at 08:28, upstream services replayed their queued events in a coordinated sequence, and all replayed events were processed by 18:48. During the replay window, customers may have experienced automation rules executing later than expected, a small number of rules reaching daily processing limits due to compressed replay, and time-sensitive rules not completing as expected if internal timeout thresholds were exceeded. **Jira and Jira Service Management** Between 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced disruption to Jira and Jira Service Management event-driven features like automation, along with a short period of elevated errors during infrastructure failover. Core Jira experiences, including issue view, boards, and project navigation, remained available throughout the incident. Jira event delivery was affected by the primary impact, preventing downstream services from receiving issue lifecycle events. This affected automation rules triggered by Jira events, AI agent orchestration in Jira, notifications for issue updates and transitions, search indexing for newly created or modified issues, and event-driven integrations between Jira and other Atlassian products. At 02:50, the event processing infrastructure failed over to an unaffected availability zone, restoring delivery of new events. All events generated during the impact window were retained in a recovery queue and required replaying. This began at 08:28 and completed at 12:00. During the replay window, customers may have experienced automation rules executing later than expected, delayed notifications arriving hours after the triggering action, temporary gaps in search results for content created or modified during the impact window, and AI agent workflows not completing as expected where internal timeout thresholds were exceeded. **Confluence** Between 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced disruptions to event-driven services in Confluence. This resulted in delays to search indexing, notifications, automation rule execution, and permission synchronisation. The underlying event processing infrastructure failed over to an unaffected availability zone, after which live Confluence operations resumed normally. However, events generated during the impact window were queued for replay, and some background services remained delayed until that replay and related validation work completed. Between 10:14 and 17:00, a bulk replay of all the queued tenant replay tasks was completed to restore data consistency. During and immediately after the replay window, customers may have experienced search results not reflecting content created or modified during the outage, delayed or missing notifications for page and comment activity, automation rules firing later than expected, and brief delays in permission synchronisation for tenants relying on incremental identity sync. **Bitbucket and Pipelines** Between 00:22 and 06:08, customers using Bitbucket and Pipelines experienced failures and degraded functionality across event-driven workflows. Core Git operations, including push, pull, and clone, were not affected and continued to operate normally throughout the incident. Automatic pipeline triggers initiated by push or pull request events were unavailable during the impact window. Merge queues, custom merge checks, Forge-based triggers, workspace permission changes, and some workspace provisioning flows were also affected. Customers using merge queues were unable to merge pull requests, and some pipeline steps failed because queued work contributed to elevated concurrency limits. At approximately 03:57, Pipelines was reconfigured to consume events through an alternative path, restoring automatic pipeline triggering. Merge queues, custom merge checks, Forge triggers, and other affected workflows were progressively restored as the underlying event processing infrastructure recovered. All Bitbucket and Pipelines services were confirmed fully operational by 06:08. After recovery, queued events were reviewed and replayed where safe to restore data consistency for billing, audit logging, and other background processes. **Identity Services** Between 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced delays in the propagation of identity and group membership changes to downstream Atlassian products. Core identity operations, including authentication, login, and direct group management actions, were not affected and continued to function normally throughout the incident. The impact was limited to asynchronous, event-driven operations that depend on the event processing pipeline. This included delays in delivering group membership and user profile changes to products such as Jira and Confluence, which affected downstream permission synchronisation and crowd sync flows. A small number of SCIM-based identity synchronisation and site provisioning workflows also experienced temporary delays. After the event processing infrastructure recovered, backed-up identity and group directory events were replayed where required, restoring downstream consistency for affected products. No identity data was lost. Group membership changes, user profile updates, and provisioning-related events that occurred during the impact window were retained and processed after recovery. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know outages impact your productivity. While our monitoring and recovery processes helped us respond quickly, this incident highlighted opportunities to further strengthen resilience for event-driven services. We are prioritizing improvements that will: * **Enhance failover coverage** so critical event processing can recover more smoothly during infrastructure disruptions. * **Strengthen recovery handling** so replayed events can be processed more quickly. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support.

Read the full incident report →

Started May 06, 2026, 09:35 AM UTC· resolved May 06, 2026, 11:17 AM UTC

1. investigating May 06, 2026, 09:35 AM UTC

   We are investigating reports of lookup objects in Automation for Jira Service Management are not functioning as expected. Our engineering teams are actively investigating and working to resolve the issue. We will provide further updates in next 1 hour.

2. monitoring May 06, 2026, 10:18 AM UTC

   A fix has been implemented to address the failures observed in the lookup objects within JSM Automation. We are actively monitoring the situation to ensure stability. We will share the final update within next 1 hour.

3. resolved May 06, 2026, 11:17 AM UTC

   The issue causing failures in the lookup objects within JSM Automation has been resolved. A fix was implemented to address the problem and the service is now operating normally for all affected customers.

Read the full incident report →

Started May 02, 2026, 12:55 AM UTC· resolved May 02, 2026, 02:48 AM UTC

1. investigating May 02, 2026, 12:55 AM UTC

   We are investigating an incident affecting Jira Software (viewBoard, viewIssue, createIssue). Our team is working to identify the cause and restore service to normal levels. We will provide the next update within 60 minutes.

2. investigating May 02, 2026, 01:38 AM UTC

   We are actively investigating reports of a service disruption affecting the issue viewing experience in Jira. This is also impacting the accessibility of support tickets. We will share updates here as more information becomes available.

3. investigating May 02, 2026, 02:00 AM UTC

   We are actively investigating reports of a service disruption affecting the Work Item viewing experience in Jira. This is also impacting the accessibility of support tickets. We will share updates here as more information becomes available.

4. resolved May 02, 2026, 02:48 AM UTC

   The Jira Work Item View experience has been restored to normal service. Our teams are continuing to investigate the root cause affecting this issue. We will provide more details once we identify the root cause

5. postmortem May 14, 2026, 07:44 PM UTC

   ### SUMMARY ### Between May 1, 2026 at 23:34 UTC and May 2, 2026 at 02:53 UTC Atlassian customers using Jira and Jira Service Management (JSM) across all Cloud tenants received an error page when attempting to open a work item due to a schema incompatibility, and editing work item fields was degraded for both products. Navigating to and interacting with boards were degraded for Jira specifically. On Jira mobile, users were unable to view work items and work item search was degraded. This was caused by a deployment of a schema configuration change that had only been validated against some production environments. The issue also affected Atlassian's customer support operations and temporarily impacted Atlassian’s ability to respond to incoming support requests. Customers were able to raise tickets as usual. Atlassian’s automated monitoring systems detected the issue on May 1, 2026 at 23:41 UTC, and engineering teams promptly began investigating. The issue was reported on Statuspage on May 2, 2026 at 00:55 UTC. The issue was resolved after 3 hours and 19 minutes on May 2, 2026 at 02:53 UTC when the previous version of the schema configuration was successfully redeployed to all regions. ### IMPACT ### - **Duration**: 3 hours 19 minutes (May 1, 2026 at 23:34 UTC – May 2, 2026 at 02:53 UTC) - **Affected regions**: All regions. - **Affected products**: Jira, JSM, Jira Mobile - **Customer experience**: - Users were unable to view work items using the work item view; consequently updating and creating work items from the work item view was affected. - Editing work items was degraded. - Boards did not show under Spaces in the Jira navigation. - Certain board interactions were affected. - Other areas of Jira not dependent on the broken schema configuration continued to operate normally. ### ### ROOT CAUSE ### The root cause was a deployment sequencing issue. A schema configuration change was deployed to the API gateway layer before the corresponding application-level change had been deployed across all production environments. This created a mismatch between the schema expected by the gateway and the schema served by the application servers. ### ### MITIGATIONS ### The engineering team identified the problematic schema change and initiated a rollback of the deployment. A deployment blocker was put in place to prevent further changes while the rollback was executed. The previous version of the schema configuration was redeployed, and service was restored across all regions. ### ### REMEDIAL ACTION PLAN & NEXT STEPS ### We understand that service disruptions impact your productivity. In addition to our existing testing and preventative processes, Atlassian is prioritizing the following actions to help reduce the likelihood and impact of similar incidents in the future and to speed up recovery when issues occur: - We are adding automated pre-deployment checks to verify that schema configurations are compatible across all production environments before changes are deployed. - We will streamline our incident communication processes, incident response training and tooling to reduce the time between incident detection and customer notification. - We are working to improve resilience of critical customer-facing support services to ensure SLA continuity during outages. We apologize to customers whose services were impacted during this incident. We are taking immediate steps to reduce the risk and impact of similar issues in future. Thanks, Atlassian

Read the full incident report →

Started Apr 14, 2026, 12:12 PM UTC· resolved Apr 14, 2026, 04:11 PM UTC

1. investigating Apr 14, 2026, 12:12 PM UTC

   We are actively investigating reports of a partial service disruption affecting Rovo, specifically for customers using automation rules that invoke Rovo agents. Some customers may find that these automations are not completing as expected. We'll share updates here as more information becomes available.

2. investigating Apr 14, 2026, 12:25 PM UTC

   We have identified that this incident also affects automation rules in Confluence that use Rovo agents. We are investigating and will provide updates as we learn more.

3. identified Apr 14, 2026, 02:11 PM UTC

   We have identified the issue, and our teams are working to resolve it and restore normal operations as quickly as possible. We will provide further updates as they become available.

4. monitoring Apr 14, 2026, 03:46 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.

5. resolved Apr 14, 2026, 04:11 PM UTC

   On April 14, 2026, affected users may have experienced some service disruption with automation rules that use Rovo agents. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Apr 13, 2026, 07:29 AM UTC· resolved Apr 13, 2026, 10:17 AM UTC

1. monitoring Apr 13, 2026, 07:29 AM UTC

   Our team is aware that some users were unable to log in to Atlassian products with their Atlassian accounts. While we believe this issue is now resolved, we are continuing to monitor all products and services for any ongoing impact. Our team is investigating with urgency, and we will provide an update within 1 hour.

2. monitoring Apr 13, 2026, 08:33 AM UTC

   Atlassian account login services are now operating as expected, and we are not observing new errors. We continue to closely monitor our systems to ensure they remain stable. We will provide another update within 60 minutes or sooner if we detect a change in status.

3. resolved Apr 13, 2026, 10:17 AM UTC

   On April 13, 2026, between 05:49 a.m. and 06:25 a.m. UTC, some users were unable to log in to Atlassian products with their Atlassian accounts. The underlying issue has been addressed, and authentication services have remained stable with no new impact observed.

4. postmortem Apr 21, 2026, 02:33 AM UTC

   ### Summary On April 13, 2026, between 05:49 and 06:29 UTC, customers experienced failures when attempting to log in, sign up, reset passwords, and complete multi-factor authentication flows across Atlassian cloud products. Approximately 90% of authentication requests failed during the peak impact window, affecting users in the US East and EU regions. The incident was mitigated within 40 minutes through manual intervention, and full service was restored by 06:29 UTC. ### **IMPACT** * **Duration**: ~40 minutes \(05:49–06:29 UTC, April 13, 2026\) * **Affected regions**: US East and EU \(authentication infrastructure serves EU traffic from US East, with traffic primarily from EU at this time of day\). * **Affected products**: All Atlassian cloud products requiring authentication, including Jira, Confluence, Jira Service Management, and Trello. * **Customer experience**: Users attempting to log in, sign up, reset passwords, or complete MFA flows received errors. Users already logged in with active sessions were unaffected. ### **ROOT CAUSE** This incident had several contributing factors that combined to produce a failure that the system could not recover from without manual intervention. **The primary cause** was a recently enabled change that caused our authentication infrastructure to retry requests to a downstream identity service when those requests were slow to respond. This retry behaviour was rolled out to 100% of traffic earlier the same day. Under normal conditions this would be benign, but it meant that any slowness in the downstream service was amplified. Since multiple upstream services were also independently retrying their own failed requests, the amplification compounded further into a retry storm. **The trigger** was a burst of legitimate user traffic. A pattern of many parallel link preview requests for a single user caused a concentrated load spike on a downstream identity service, pushing its response times above the retry threshold. On its own, this kind of spike had occurred many times before and always recovered. With the retry amplification now in effect, the spike instead created a runaway feedback loop: slow responses caused retries, retries increased load, increased load caused slower responses, preventing recovery. The incident was mitigated by manually scaling up the downstream identity service to provide sufficient capacity to absorb the amplified load. Once scaled, the service recovered immediately, bringing authentication error rates to zero within one minute. **REMEDIAL ACTIONS PLAN & NEXT STEPS** We are taking the following actions designed to prevent recurrence and improve our resilience: 1. **Immediate**: The retry-on-timeout change has been disabled. 2. **Load shedding and self-healing**: We are adding load shedding capabilities to our authentication services so that they can automatically shed excess load and self-recover during traffic spikes, without requiring action before automatic scaling starts. 3. **Reducing request fan-out**: We are reviewing patterns where a single user action can generate many parallel downstream requests, and will introduce methods where possible to reduce the amplification potential. We apologize to customers whose services were interrupted by this incident and we are taking immediate steps to improve the platform’s reliability. Thanks, Atlassian Customer Support

Read the full incident report →

Started Apr 08, 2026, 06:24 AM UTC· resolved Apr 08, 2026, 11:43 AM UTC

1. investigating Apr 08, 2026, 06:24 AM UTC

   Our team is aware that users are currently experiencing errors while attempting to search in Confluence and Jira. Our team is investigating with urgency and will be providing an update within 1 hour.

2. investigating Apr 08, 2026, 06:25 AM UTC

   Our team is aware that users are currently experiencing errors while attempting to search in Confluence and Jira. Our team is investigating with urgency and will be providing an update within 1 hour.

3. investigating Apr 08, 2026, 06:25 AM UTC

   The impact of this incident is now understood to also be impacting search in Jira and Confluence, as well as additional downstream impacts to Rovo Chat, User Management, Administration and Guard. Our team is continuing to investigate with urgency and we will provide further update within 1 hour.

4. identified Apr 08, 2026, 06:25 AM UTC

   We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus. Our team have identified the potential root cause of the issue and our teams are working with urgency on a resolution. We will provide further update within 1 hour.

5. identified Apr 08, 2026, 07:40 AM UTC

   We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus. Our team have identified the potential root cause of the issue and our teams are working with urgency on a resolution. We will provide further update within 1 hour.

6. identified Apr 08, 2026, 07:40 AM UTC

   Confluence and Jira search reliability is improving, and we expect full recovery shortly; we will continue to closely monitor the services to ensure they remain stable.

7. identified Apr 08, 2026, 08:33 AM UTC

   We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus. Our team have identified the potential root cause of the issue and our teams are working with urgency on a resolution. We will provide further update within 1 hour.

8. identified Apr 08, 2026, 08:33 AM UTC

   We have restored core search functionality and services are operating again, but some customers may still experience delays when searching for data changed within the last hour while new data continues to be indexed. We are actively working to complete reindexing and will update this page as performance fully recovers.

9. identified Apr 08, 2026, 09:03 AM UTC

   We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus. Our team have identified the potential root cause of the issue and our teams are working with urgency on a resolution. We will provide further update within 1 hour.

10. monitoring Apr 08, 2026, 09:03 AM UTC

    The issue has been resolved, and services are now operating normally. Some customers may still experience delays when searching for data changed within the last hour, while new data continues to be indexed. We'll continue to monitor closely to confirm stability.

11. resolved Apr 08, 2026, 11:43 AM UTC

    The issue has now been resolved, and the service is operating normally for all affected customers.

12. postmortem Apr 17, 2026, 04:23 PM UTC

    ### Summary On April 8, 2026, between 04:46 UTC and 12:09 UTC, search functionality was unavailable or degraded across several Atlassian Cloud products, including Jira, Confluence, Jira Service Management, Rovo, Rovo Dev, Loom, Guard Standard, Customer Service Management and Atlassian Administration. A configuration change increased the resources reserved for a core system component that runs on nodes in our compute platform. On a subset of clusters configured for high‑density workloads, the increased reservations exceeded available node capacity interrupting search and related experiences for affected customers. The root cause was identified and a rollback was merged at 05:42 UTC with some systems seeing recovery by 07:33 UTC**.** Core search functionality was restored approximately by 08:55 UTC, and full downstream recovery completed by 12:09 UTC. ### **IMPACT** During the impact period, some customers experienced outages or degradation in search across Jira, Confluence, Jira Service Management, Rovo, Rovo Dev, Loom, Guard Standard, Customer Service Management and Atlassian Administration. Other experiences that rely on search such as quick find, navigation, AI assistants, dashboards, were also intermittently affected during this period. Impacted customers may have been unable to find pages or recordings and experienced degraded performance in finding issues; received empty or delayed search results; or experienced AI assistants and dashboards that could not retrieve relevant context. **Jira, Jira Service Management and Customer Service Management:** Search and experiences that depend on search like finding issues and agent responses in CSM remained available but with degraded performance in fallback mode. By 12:09 UTC, search indexes and search performance was fully restored from fallback to full capacity across all regions. **Guard Standard and Atlassian Administration:** Search functionality was unavailable for parts of the incident window. As a result, Domain Claims, usage tracking, and managed accounts were degraded for portions of the window. These services were restored to operational status by 07:33 UTC. Guard Premium was not impacted by this issue. **Confluence:** Search functionality was unavailable for parts of the incident window. Recovery began at 07:30 UTC as backend search clusters were restored. Full recovery, including search index replay, completed at 11:37 UTC. **Loom:** Search functionality and some experiences that rely on Confluence Search, such as sharing to spaces\) was unavailable for portions of the window and fully restored at 11:37 UTC. **Rovo and Rovo Dev:** Rovo agents remained responsive but experienced degraded functionality due to loss of search capabilities in underlying services. They were unable to reliably return context about work items or pages. Functionality was fully restored at 11:37 UTC. ### **ROOT CAUSE** Atlassian products rely on OpenSearch clusters to power their search capabilities including issue search, content search, and AI-powered search features. An infrastructure configuration change increased resource reservations \(CPU & Memory\) for a system component that runs across our compute platform. On a subset of clusters configured for high-density workloads, the increased reservations exceeded available node capacity. This caused search workloads to be evicted and, in some clusters, could not reschedule onto any available nodes impacting search functionality across affected products. The change was deployed across multiple production clusters in a short time frame, limiting the opportunity to detect the capacity conflict in a smaller subset of clusters before it reached the wider fleet. Automated scaling systems attempted to recover by provisioning additional capacity but in the worst‑affected clusters this led to runaway node scaling and exhaustion of available network resources, prolonging recovery time. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We understand that service disruptions impact your productivity. In addition to our existing testing and preventative processes, Atlassian is prioritizing the following actions to help reduce the likelihood and impact of similar incidents in the future and to speed up recovery when issues occur: * **Enforce smaller deployment cohorts and larger soak for critical platform changes for these cluster types** Implement smaller deployment cohorts, mandatory soak periods between environments, and automated health gates so that changes are validated on a limited set of clusters before being promoted more broadly. * **Strengthen automated pre‑deploy validation for resource changes** Add validation checks to ensure resource changes for system components are compatible with node capacity and reserved headroom, preventing system workloads from crowding out customer workloads. * **Improve post‑deploy verification and alerting** Enhance monitoring and post‑deployment verification to detect patterns such as spikes in pending pods, runaway node scaling, and low pod‑IP headroom closely correlated with new configuration being rolled out. * **Align autoscaling behavior with capacity and safety limits** Align autoscaling capacity calculations with node reservations and introduce safeguards and circuit breakers to prevent runaway scaling and to enforce safe limits on node and pod IP counts. * **Enhance recovery automation** Improve automation and runbooks so we can safely disable autoscaling, remove empty nodes in bulk, and restore normal operations faster across multiple clusters in parallel. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability and to reduce the risk and impact of similar issues in future. Thanks, Atlassian Customer Support

Read the full incident report →

Started Mar 18, 2026, 11:32 AM UTC· resolved Mar 19, 2026, 04:08 AM UTC

1. investigating Mar 18, 2026, 11:32 AM UTC

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

2. investigating Mar 18, 2026, 11:32 AM UTC

   Some customers may experience automations not triggering for specific actions such as work item creation, updates, and comment additions. However, manually triggered automations are operating as expected.

3. investigating Mar 18, 2026, 12:24 PM UTC

   Customers using Jira and Jira Service Management are currently experiencing an issue where automations do not trigger for actions such as work item creation, field updates, and comment additions, although manual triggers remain functional. We'll share updates here as more information is available.

4. investigating Mar 18, 2026, 01:07 PM UTC

   We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

5. investigating Mar 18, 2026, 02:01 PM UTC

   We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

6. monitoring Mar 18, 2026, 02:03 PM UTC

   We have identified the cause of the issue and deployed changes that have restored automation processing for Jira and Jira Service Management. Automations are now triggering as expected. We will continue to monitor closely to confirm stability.

7. monitoring Mar 18, 2026, 02:53 PM UTC

   We are replaying historical events for affected customers to rerun Automation rules that failed to execute between March 18, 10:00 AM UTC and 1:45 PM UTC. We are closely monitoring the results of this replay and will post an update in a few hours when this work is complete.

8. monitoring Mar 18, 2026, 09:44 PM UTC

   We have successfully completed the replay for most regions, with remainder expected to finish in next 3 hours.

9. monitoring Mar 18, 2026, 11:44 PM UTC

   Processing of the historical events is still occurring with our team monitoring progress closely. We will be providing a further update either when these tasks are fully completed or within 4 hours, whichever is earlier.

10. resolved Mar 19, 2026, 04:08 AM UTC

    The vast majority of customers historical events have now all been processed successfully, with a small group of customers that have very high volume of automations still to process which are actively underway. We expect these remaining processes to be completed within approximately two hours, if not sooner.

11. postmortem Apr 02, 2026, 07:07 AM UTC

    ### Summary On March 18, 2026, between 10:06 and 13:47 UTC, customers experienced delays in Automation rules executing when triggered by Jira events such as Work Item creation, Work Item updates, and comments. Automation rules using other trigger types, including scheduled triggers, manual triggers, and incoming webhooks, continued to operate normally. The incident was caused by an internal configuration change that inadvertently disabled the event delivery pathway used to notify the automation platform of changes in Jira. The incident was identified through customer support tickets and verified through our monitoring; engineering teams were engaged for resolution. Once the root cause was identified, the configuration was corrected and normal automation processing resumed. Following restoration, the delayed events began flowing to the automation platform for processing. This backlog took approximately 14 hours to fully clear. During this recovery window, some automation rules ran on Work Items whose data had changed due to user actions, customer mitigation, or other causes. Since rule execution usually follows triggering events closely, many customer rules assume immediate execution on the Work Item. The delay allowed other changes —such as updates or customer actions to mitigate the incident's impact — to occur, causing unintended consequences when the rule executed later. ### **IMPACT** During the impact window, Jira Cloud customers were unable to rely on timely execution of event‑triggered automation rules. Rules that depended on Jira Work Item events - including Work Item created, Work Item updated, comment added, sprint changes, and version changes - ran with significant delays. This affected automated workflows responsible for Work Item routing, notifications, field updates, and other rule‑driven actions throughout the outage. Automation rules that used scheduled, manual, or incoming webhook triggers remained unaffected. Following mitigation, a recovery period of approximately 14 hours was required to process the backlog of delayed events. During this window, processing delays peaked at approximately 12 hours from event occurrence to rule completion. In some cases, rules executing against Work Item data several hours after the rule trigger occurred, caused problems due to the rules being built with the expectation in mind that little time would pass between trigger and execution. This resulted in Work Items ending up in an unintended state; especially as some customers undertook manual intervention given the situation. ### **ROOT CAUSE** The incident was caused by a configuration change to an internal feature flag used to control event delivery to the automation platform. A code change had been prepared to remove a feature flag from the event delivery system. However, this code change had not yet been deployed to production. When the feature flag was subsequently retired through our feature flag management system, the retirement process relied on usage telemetry that incorrectly indicated the flag was no longer active. This inadvertently created a blind spot where the flag appeared unused when it was in fact being actively evaluated. When the flag was retired, the event delivery system interpreted its absence as an instruction to stop delivering Jira events to the automation platform, causing all event-triggered automation rules to stop firing. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We understand that outages impact your productivity. In addition to our existing testing and preventative processes, Atlassian is prioritising the following actions to help reduce the likelihood and impact of similar incidents in the future: * **Strengthen feature flag lifecycle safety controls** * Address the telemetry gap by removing feature flagged code from the hot path of our event processing framework where it was being surpressed, ensuring we have good telemetry on feature flag use across our systems. This will prevent inadvertent archival of feature flags in future. * Refine feature flag retirement processes so that flags cannot be retired without verifying actual production usage, independent of standard telemetry signals. * **Improve event delivery monitoring and alerting** * Refine monitoring to detect drops in automation event delivery rates within minutes, and add automated alerting on automation execution volume anomalies to enable faster detection of disruptions. * **Improve our ability to clear delayed events faster and deliver controls for customers to decide alternative workflows for events based on delay.** * Refine replay infrastructure to recover faster from the pent up backlog that can be created due to delays. * Provide workflow components that allow users to decide what to do for varying delays between the triggering event and when the rule gets executed to reduce the risk of unintended changes during recovery. We recognise the importance of Jira Automation to our customers' workflows and are committed to ongoing improvements to the reliability and resilience of our platform. We sincerely apologize for the disruption this incident caused, and we will continue to invest in measures that support a stable and dependable service. Thanks, Atlassian Customer Support

Read the full incident report →

Started Mar 10, 2026, 12:06 AM UTC· resolved Mar 10, 2026, 12:59 AM UTC

1. investigating Mar 10, 2026, 12:06 AM UTC

   We are aware of customers experiencing delays with their automations within Jira, Jira Service Management, Jira Work Management, Jira Product Discovery and Confluence. Our team is investigating with urgency and we will provide an update within one hour.

2. identified Mar 10, 2026, 12:15 AM UTC

   Our team has now identified the cause of this issue relating to delayed automation events and has put a hotfix in place to help restore automation performance. We will continue to monitor performance as the backlog of issues is now being processed.

3. monitoring Mar 10, 2026, 12:51 AM UTC

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

4. resolved Mar 10, 2026, 12:59 AM UTC

   On 9 March UTC, Automation users in the APAC region may have experienced performance degradation within Jira, Jira Product Discovery, Jira Service Management, Jira Work Management, Confluence. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Feb 26, 2026, 01:22 PM UTC· resolved Feb 26, 2026, 06:55 PM UTC

1. investigating Feb 26, 2026, 01:22 PM UTC

   Atlassian Assist in Jira Service Management is currently unavailable. We are actively investigating the problem. We will share updates here as more information in next 60 mins or sooner.

2. investigating Feb 26, 2026, 02:25 PM UTC

   We are still actively investigating this issue and working to restore Atlassian Assist in Jira Service Management. We will share another update here within the next 2 hours or sooner.

3. investigating Feb 26, 2026, 04:21 PM UTC

   We continue to investigate the issue, and will share an update within next 2 hours or sooner.

4. identified Feb 26, 2026, 06:05 PM UTC

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience Atlassian Assist unavailability in JSM. We will continue to share additional updates here as more information is available.

5. monitoring Feb 26, 2026, 06:33 PM UTC

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

6. resolved Feb 26, 2026, 06:55 PM UTC

   On February 26, 2026, JSM experienced a disruption, and Atlassian Assist service was 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 Feb 20, 2026, 02:52 AM UTC· resolved Feb 20, 2026, 12:26 PM UTC

1. identified Feb 20, 2026, 02:52 AM UTC

   Our team has identified components of Jira Service Management that are also impacted by this incident and we have updated our notifications here appropriately. We anticipate our next update to be posted within 8 hours, as our team continues working with urgency towards mitigation of this issue. Feb 20, 2026 - 02:52 UTC Please see prior notifications relating to this incident below: Update - Several regions have fully recovered, and the team continues to diligently work on full mitigation. Some affected users may experience inability to select users and teams in specified fields on certain sites. We anticipate next update to be posted in approximately 8 hours. Feb 19, 2026 - 21:04 UTC Update - We continue to make progress on full mitigation, and more users should see experience returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites. We will continue to share additional updates here as more information is available. Feb 19, 2026 - 18:56 UTC Identified - Mitigation is progressing, and user experience is returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites. Feb 19, 2026 - 17:34 UTC Update - We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience inability to select users and teams in specified fields on certain sites. We will continue to share additional updates here as more information is available. Feb 19, 2026 - 17:14 UTC Investigating - We are actively investigating reports of performance degradation affecting the ability to select users and teams in specified fields on certain sites. We will share updates here as more information is available. Feb 19, 2026 - 16:44 UTC

2. identified Feb 20, 2026, 04:14 AM UTC

   Customers using Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours as we continue our investigation.

3. identified Feb 20, 2026, 07:13 AM UTC

   We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours or sooner based on significant progress.

4. identified Feb 20, 2026, 12:26 PM UTC

   We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours or sooner based on significant progress.

5. resolved Feb 20, 2026, 12:26 PM UTC

   This issue has been resolved and all services are functional.

Read the full incident report →

Started Feb 06, 2026, 08:24 PM UTC· resolved Feb 07, 2026, 05:38 AM UTC

1. identified Feb 06, 2026, 08:24 PM UTC

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access Jira and JSM. We will continue to share additional updates here as more information is available.

2. identified Feb 06, 2026, 08:24 PM UTC

   Impact The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption. Current Status Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible. Next Steps The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes.

3. identified Feb 06, 2026, 08:26 PM UTC

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access Jira and JSM. We will continue to share additional updates here as more information is available.

4. identified Feb 06, 2026, 10:33 PM UTC

   Our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additioanl updates here as more information is available.

5. identified Feb 07, 2026, 02:22 AM UTC

   Our teams are in final stages of mitigation. During this time, some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.

6. identified Feb 07, 2026, 03:43 AM UTC

   Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.

7. monitoring Feb 07, 2026, 05:28 AM UTC

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

8. resolved Feb 07, 2026, 05:38 AM UTC

   On February 6, 2026, JIRA and JSM 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 Feb 06, 2026, 01:47 AM UTC· resolved Feb 06, 2026, 08:01 PM UTC

1. investigating Feb 06, 2026, 01:47 AM UTC

   We are aware of reports that Free JSM customers received emails stating that their plans have been adjusted to Standard Trial Service Collection accounts. Our team is working urgently to address this issue and we plan to revert the change for all customers that are impacted, to reinstate their Free plan status. Please note that if your plan has been incorrectly updated, you will be placed into a no-cost trial status. There is currently no action required from those customers that have incorrectly received these emails. We will provide further update within an hour as our effort continues.

2. identified Feb 06, 2026, 03:02 AM UTC

   During an update designed to enable Service Collection for our Jira Service Management Free customers, some of these customers were incorrectly updated to a Standard Service Collection no-cost trial, and received a notification that they would now need to pay for this service at the end of their trial period. Please rest assured that requiring payment was not an intended change for these Free customers, and we are working to restore these accounts back to their Free status. We will provide further update within two hours or earlier if there is important information to share.

3. identified Feb 06, 2026, 05:57 AM UTC

   Our team is now actively testing the fix required to properly restore customer accounts impacted by this incident. We will provide further update within two hours to provide guidance on our expected timeline for the resolution to be fully completed.

4. identified Feb 06, 2026, 07:52 AM UTC

   Our team continues active testing of the fix to restore customer accounts affected by this incident. We will provide further update within two hours or sooner.

5. identified Feb 06, 2026, 10:25 AM UTC

   Our team has identified the steps required to restore the affected sites and is actively working to restore original entitlements. We will provide our next update in four hours, or sooner if we have meaningful progress to share.

6. monitoring Feb 06, 2026, 02:41 PM UTC

   The team has corrected entitlements for impacted customers and reverted plans to Service Collection Free. We are now monitoring the rollout to confirm the fix has successfully propagated to all accounts.

7. resolved Feb 06, 2026, 08:01 PM UTC

   The team has verified that the fix has successfully propagated to all accounts. Impacted customers will receive an email follow-up containing additional information.

Read the full incident report →

Started Feb 05, 2026, 02:13 PM UTC· resolved Feb 05, 2026, 09:38 PM UTC

1. investigating Feb 05, 2026, 02:13 PM UTC

   Some users in us-east-1 region might not be able to access Jira and JSM. We are aware of this issue and are actively investigating the same. We will provide update on the progress in next 60 minutes or sooner.

2. identified Feb 05, 2026, 02:40 PM UTC

   Some users in the us-east-1 region cannot access Jira and JSM. We have identified the cause and placed Jira and JSM in maintenance mode for the affected sites to expedite resolution. We will provide update on the progress in next 60 minutes or sooner.

3. identified Feb 05, 2026, 03:39 PM UTC

   We have identified the cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.

4. identified Feb 05, 2026, 05:35 PM UTC

   Our team is diligently working on a mitigation, with access being restored for some users in us-east-1 region. We will continue to share additional updates here as more information is available.

5. identified Feb 05, 2026, 07:22 PM UTC

   Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation. We will continue to share additional updates here as more information is available.

6. monitoring Feb 05, 2026, 09:09 PM UTC

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

7. resolved Feb 05, 2026, 09:38 PM UTC

   On February 5, 2026, JIRA and JIRA Service Management 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 Jan 28, 2026, 06:12 PM UTC· resolved Jan 28, 2026, 07:42 PM UTC

1. identified Jan 28, 2026, 06:12 PM UTC

   We are actively investigating an issue affecting Jira, Jira Product Discovery, and Jira Service Management. Affected users may experience delayed issue data in some experiences, such as issue view. We will share updates here in one hour or as more information becomes available.

2. identified Jan 28, 2026, 06:50 PM UTC

   We are continuing to investigate an issue affecting Jira, Jira Product Discovery, and Jira Service Management. Affected users may experience delayed issue data in some experiences, such as issue view. We will share updates here in one hour or as more information becomes available.

3. resolved Jan 28, 2026, 07:42 PM UTC

   On Jan 28, 2026, Jira, Jira Product Discovery, and Jira Service Management users in eu-west-1 region may have experienced delays in viewing recently submitted updates on the web page and/or mobile apps. Updates continued to process successfully during the incident. There are no actions needed from customers. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Jan 27, 2026, 11:07 AM UTC· resolved Jan 27, 2026, 11:49 AM UTC

1. investigating Jan 27, 2026, 11:07 AM UTC

   We understand that some of our customers are facing intermittent issues with Assets. Our team is investigating the issue. We will update you on the progress within 60 minutes or sooner.

2. identified Jan 27, 2026, 11:33 AM UTC

   The incident has affected the Assets product, leading users encountering intermittent unavailability. Our team has identified the cause of the issue and deployed fix for the same. We see that the error rate has decreased, and the team is actively monitoring to ensure further stability. Further updates will follow in 60 minutes or upon significant progress.

3. resolved Jan 27, 2026, 11:49 AM UTC

   Deployment of the fix is completed and services are back to normal. This issue is resolved.

Read the full incident report →

Started Jan 22, 2026, 02:44 PM UTC· resolved Jan 22, 2026, 04:47 PM UTC

1. investigating Jan 22, 2026, 02:44 PM UTC

   Jira Service Management users are currently experiencing an issue where assets are not loading, affecting their interactions with service management functionality. We are currently investigating the issue, and the next update will be shared in 60 minutes or sooner

2. identified Jan 22, 2026, 03:41 PM UTC

   We have identified the cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience issue where assets are not loading, affecting their interactions with service management functionality. We will continue to share additional updates here as more information becomes available.

3. monitoring Jan 22, 2026, 04:32 PM UTC

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

4. resolved Jan 22, 2026, 04:47 PM UTC

   On January 22, 2026, affected Jira Service Management users may have experienced some service disruption where assets were not loading, affecting their interactions with service management functionality. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Jan 20, 2026, 07:10 PM UTC· resolved Jan 20, 2026, 11:09 PM UTC

1. investigating Jan 20, 2026, 07:10 PM UTC

   Impact Users of the Assets product are experiencing intermittent accessibility issues, resulting in gateway timeouts and internal server errors. These technical disruptions are causing difficulties in performing queries, which may manifest as slow performance or failure to load certain pages, particularly those involving schemas. This issue affects related features that depend on the Assets product, such as specific custom fields and automation processes. Current Status The support teams are actively working to diagnose the issue and are focused on identifying the underlying problems causing the disruption. Efforts are ongoing to restore normal service levels and minimize any further inconvenience to users. Next Steps The incident team is continuing its investigation to determine the full extent of the impact and to identify effective resolutions. Further communications will be issued in 60 minutes or when significant progress is made.

2. investigating Jan 20, 2026, 08:08 PM UTC

   We continue to investigate the issue, and next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

3. monitoring Jan 20, 2026, 09:14 PM UTC

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

4. resolved Jan 20, 2026, 11:09 PM UTC

   On January 20, 2026, some customers may have experienced performance degradation of Assets. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Jan 06, 2026, 05:18 AM UTC· resolved Jan 07, 2026, 11:32 AM UTC

1. investigating Jan 06, 2026, 05:18 AM UTC

   We are investigating an incident impacting Automation for Jira across Jira and Jira Service Management. Some automation rules that use specific triggers may fail to execute. Our team is working to identify the cause and restore normal service. We will provide the next update within 60 minutes.

2. identified Jan 06, 2026, 06:17 AM UTC

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

3. identified Jan 06, 2026, 07:58 AM UTC

   Our engineers are continuing work toward the resolution of the incident impacting Automation for Jira. There are no new updates to share at this time. We will provide the next update within 2 hours.

4. identified Jan 06, 2026, 10:11 AM UTC

   Customers using Jira and Jira Service Management in Asia Pacific and South East regions have faced issues with Automation for Jira. Other regions are not impacted. Some automation rules using specific triggers failed to execute, causing rules to appear unresponsive. We have identified the cause and we continue working on restoring the operations back to normal as soon as possible. In the meantime, workaround to manage business critical rules is to disable and then re-enable each automation rule. This action triggers the rule and must be done for every critical rule. We will provide the next update in about two hours or sooner.

5. identified Jan 06, 2026, 12:19 PM UTC

   Some automation rules using specific triggers failed to execute, causing rules to appear unresponsive. Customers using Jira and Jira Service Management in Asia Pacific and South East regions have faced issues with Automation for Jira. Other regions are not impacted. The cause has been identified, and the team is actively working on restoring the operations back to normal as soon as possible. Workaround to manage critical rules, disable and re-enable each automation rule. This triggers the rule and must be done for every critical rule. We will provide the next update in about two hours or sooner.

6. monitoring Jan 06, 2026, 02:04 PM UTC

   Issue has been fixed for all new events - we are waiting for confirmation from some customers when they come online. Customers using Jira and Jira Service Management in Asia Pacific and South East regions had faced issues with Automation for Jira. Other regions not impacted. During Asia Pacific hours tomorrow, the team plans to replay historical events. Team will continue monitoring. Next update will tomorrow.

7. monitoring Jan 07, 2026, 04:43 AM UTC

   We are currently replaying historical events for affected customers to rerun Automation for Jira rules that failed to execute earlier. Our teams are closely monitoring the results of this replay to confirm that all affected automations are running as expected. We will provide the next update in about two hours or sooner.

8. monitoring Jan 07, 2026, 08:37 AM UTC

   We have replayed about 7 hours of historical events for affected customers to rerun Automation for Jira rules that previously failed. This covers most of the APAC business hours. Based on customer feedback, our team continues monitoring the situation and plans to complete rerunning the remaining Automation for Jira rules that failed earlier. We will provide the next update once replaying the historical events is complete.

9. resolved Jan 07, 2026, 11:32 AM UTC

   Rerunning the remaining Automation for Jira rules that failed for affected customers is complete. This update resolves the issue.

Read the full incident report →

Started Dec 27, 2025, 02:48 AM UTC· resolved Dec 27, 2025, 05:20 AM UTC

1. investigating Dec 27, 2025, 02:48 AM UTC

   We have identified an issue with outbound email delivery and mobile push notifications that is impacting Atlassian Cloud customers across all products. Importantly, customer support tickets are unable to be generated during this time. We apologise for any inconvenience this may cause. We are currently investigating and will provide more information as it becomes available.

2. investigating Dec 27, 2025, 03:28 AM UTC

   We are actively investigating this issue and will share additional updates as soon as more information becomes available. We sincerely apologize for the inconvenience this has caused.

3. monitoring Dec 27, 2025, 04:42 AM UTC

   We have taken steps to mitigate the issue and are seeing recovery in the affected services. Our teams will continue to closely monitor the situation and are actively working to confirm that all services are fully restored. We will provide further updates as we make additional progress.

4. resolved Dec 27, 2025, 05:20 AM UTC

   We have successfully mitigated the incident and all affected services are now fully operational. Our teams have verified that normal functionality has been restored across all areas. Thank you for your patience and understanding while we worked to resolve this issue.

5. postmortem Jan 30, 2026, 04:07 AM UTC

   ### Summary On **December 27, 2025**, between **02:48 UTC and 05:20 UTC**, some Atlassian cloud customers experienced failures in sending and receiving emails and mobile notifications. Core Jira and Confluence functionality remained available. The issue was triggered when **TLS certificates used by Atlassian’s monitoring infrastructure expired**, causing parts of our metrics pipeline to stop accepting traffic. Services responsible for email and mobile notifications had a critical path dependency on monitoring path leading to service disruptions. All impacted services were fully restored by **05:20 UTC**, around **2.5 hours** after customer impact began. ### IMPACT During the impact window, customers experienced: * **Outbound product email failures** \(notifications and other product emails did not send\). * **Identity and account flow failures** where emails were required \(e.g. sign‑ups, password resets, one‑time‑password / step‑up challenges\). * **Jira and Confluence mobile push notifications** * **Customer site activations and some admin policy changes** failing and requiring later reprocessing. ### ROOT CAUSE The incident was caused by: 1. **Expired TLS certificates** on domains used by our monitoring and metrics infrastructure caused by **misconfigured DNS authorization record** which prevented automatic renewal. 2. **Tight coupling of services to metrics publishing**, which caused them to fail when monitoring endpoints became unavailable, instead of degrading gracefully. ### REMEDIAL ACTIONS PLAN & NEXT STEPS We recognize that outages like this have a direct impact on customers’ ability to receive important notifications, complete account tasks, and operate their sites. We are prioritizing the following actions to improve our existing testing, monitoring and certificate management processes: * **Hardening monitoring and certificate infrastructure** * We are refining DNS and certificate configuration across our monitoring domains and strengthening proactive checks to detect and address failed renewals and certificate issues well before expiry. * We are also improving alerting on our monitoring and metrics pipeline. * **Decoupling monitoring from critical customer flows** We are updating services such as outbound email, identity, mobile push, provisioning, and admin policy changes so they no longer depend on metrics publishing to operate. If monitoring becomes unavailable, these services will continue to run and degrade gracefully by dropping or buffering metrics instead of failing customer operations. We apologize to customers impacted during this incident. We are implementing the improvements above to help ensure that similar issues are avoided. Thanks, Atlassian Customer Support

Read the full incident report →

Started Dec 15, 2025, 04:16 PM UTC· resolved Dec 15, 2025, 07:02 PM UTC

1. identified Dec 15, 2025, 04:16 PM UTC

   We are actively investigating reports of performance degradation affecting Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo. We'll share updates here as more information is available.

2. identified Dec 15, 2025, 04:26 PM UTC

   We are actively investigating reports of performance degradation affecting Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, Jira Work Management, and Rovo. We'll share updates here as more information is available.

3. identified Dec 15, 2025, 04:48 PM UTC

   We have identified the cause of the issue, and our teams are diligently working on mitigations. We're currently seeing signs of improvements. We'll continue to share additional updates here in 60 minutes or as more information becomes available.

4. identified Dec 15, 2025, 05:47 PM UTC

   Our teams are continuing to implement mitigations. Error rates have decreased across all products and we are seeing improvements. We will continue to provide updates here in 60 minutes or as more information becomes available.

5. resolved Dec 15, 2025, 07:02 PM UTC

   On December 15th, 2025, Admin Hub, Atlassian Analytics, Confluence Cloud, Ecosystem, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo users in the prod-us-east region may have experienced performance degradations and errors on the web page and mobile apps. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Dec 05, 2025, 01:16 PM UTC· resolved Dec 05, 2025, 03:32 PM UTC

1. monitoring Dec 05, 2025, 01:16 PM UTC

   We are currently investigating an issue where users encounter a Something Went Wrong error when creating a Linked Work Item that includes an attachment. Our engineering team is in the process of deploying the fix to production, and the ETA is 9hours from now. We apologize for the inconvenience and will provide updates as soon as more information becomes available. Thank you for your patience. Next Steps: The team will continue to monitor the situation until the hotfix is fully rolled out. Follow-up communications will be sent once the hot fix is fully rolled out.

2. resolved Dec 05, 2025, 03:32 PM UTC

   On December 5th, 2025, Jira Service Management users may have experienced an error when creating linked work items that included an attachment. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Dec 01, 2025, 05:25 PM UTC· resolved Dec 01, 2025, 06:26 PM UTC

1. investigating Dec 01, 2025, 05:25 PM UTC

   We are investigating an incident affecting Jira Work Management, Jira, and Jira Service Management. We will provide updates via Statuspage shortly. The ability to view issues and boards is experiencing degraded performance for some users. Customers may notice a slowdown in accessing these functionalities.

2. investigating Dec 01, 2025, 05:26 PM UTC

   We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

3. investigating Dec 01, 2025, 05:30 PM UTC

   We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

4. investigating Dec 01, 2025, 06:26 PM UTC

   We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.

5. resolved Dec 01, 2025, 06:26 PM UTC

   Impact Jira Software users experienced degraded performance affecting their ability to view issues and boards. Users may have encountered an error or slowdown during this time. Current Status The situation is currently mitigated due to actions taken on the affected systems, leading to a stabilization of services. Next Steps The team is actively monitoring the systems.

Read the full incident report →

Started Nov 21, 2025, 02:55 PM UTC· resolved Nov 21, 2025, 04:49 PM UTC

1. investigating Nov 21, 2025, 02:55 PM UTC

   Multiple Atlassian services are seeing outages and we are investigating the same. We shall keep you posted on the progress in 60 minutes, if not sooner

2. investigating Nov 21, 2025, 03:30 PM UTC

   Multiple Atlassian services are experiencing degraded performance. We are investigating and will provide an update within the hour.

3. monitoring Nov 21, 2025, 04:14 PM UTC

   The Trello performance degradation affecting some customers has been resolved. A subset of customers may have experienced intermittent errors on some of our other products, but these should also now be resolved too. We'll continue to monitor closely to confirm stability.

4. resolved Nov 21, 2025, 04:49 PM UTC

   The Trello performance degradation has been resolved. Also, some intermittent errors on some of our other products, has also now been resolved. The issue has now been resolved, and the service is operating normally for all affected customers.

5. postmortem Dec 08, 2025, 05:24 AM UTC

   ### Summary On November 21, 2025, between 13:44 and 15:16 UTC, Trello customers were intermittently unable to view and update data on their boards. Customers also may have experienced issues authenticating with Atlassian products, and creating new GitHub and Slack integrations. The event was triggered by a bug encountered in the software running our edge proxy fleet, which proxies customer traffic to Atlassian cloud services. The changes included the migration of our edge proxy fleet to hosts running an ARM CPU architecture, rather than the AMD64 CPU architecture they had previously been running, which impacted US East customers. The incident was detected within 1 minute by our automated monitoring systems, and mitigated by a scale up of of fleet size, which put Atlassian systems into a known good state. This was followed by a global migration of edge proxy fleet hosts back to AMD64 CPU architecture the following day. ### **IMPACT** During the impact window, US East customers intermittently could not view or update data in Trello. The same underlying issue also impacted our Identity services and integrations with GitHub and Slack, meaning some customers had trouble signing in to Atlassian products or creating new integrations. At the incident’s peak, the incident impacted up to: * 52% of new Trello network connections. * 9% of new GitHub and Slack integrations. * 8% of new Identity network connections. ### **ROOT CAUSE** The issue was caused by a change to CPU architecture from AMD64 to ARM on our edge proxy fleet. This led to a bug that caused these instances to stall under high load, and refuse up to 52% of new connections. As a result, some customers of the products above could not make new connections to Atlassian services, and customers received CloudFront 504 gateway timeout error responses. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. While we deploy our changes progressively by cloud region to avoid broad impact, on this occasion, our pre-change load testing had not accurately reflected production loads. As part of our response to this incident, and to help prevent recurrence, we rolled back all edge proxy fleets from ARM to AMD64 CPU architecture globally. To minimise the impact of breaking changes to our environments, we plan to implement additional preventative measures such as: * Adding improved load tests into edge proxy fleet deployment pipelines to catch load-related bugs before deployment to production. * Adding alerts to our edge proxy fleet to catch rises in TCP connect times before customer impact. We apologize to customers whose services were impacted during this incident; we are taking steps to help improve the platform’s performance and availability. Thanks, Atlassian Customer Support

Read the full incident report →

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

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

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

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

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

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

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

Read the full incident report →

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

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

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

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

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

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

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

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

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

Read the full incident report →