Encoded - Notice history

This incident has been resolved. This issue was caused due to an un-optimised database procedure which was quickly resolved by our team. Apologies for any inconvenience caused. If you require any further information then please contact the Encoded Service Desk.

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.

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.

Summary

On September 14, 2026, between 15:30 and 17:10 UTC, Atlassian customers using Opsgenie, Jira Service Management, and Compass experienced delays in receiving alert notifications and intermittent failures when using Ops features. The issue was triggered by long-running transactions in a core service, which led to thread pool exhaustion and caused subsequent requests to become unresponsive. The long-running transactions were caused by a configuration change released between September 9, 2026 and September 11, 2026 UTC. The team actively monitored the impact of the change on the system until early September 14, 2026 UTC, and observed no anomalies. However, increasing traffic during US working hours on September 14, 2026, caused these unexpectedly long-running transactions. The incident was detected within one minute by our automated monitoring systems, and full service stabilization occurred after isolating and rolling back the change on September 14, 2026 at 17:10 UTC.

IMPACT

The incident primarily affected Ops features across Opsgenie, Jira Service Management, and Compass for customers hosted in the US region. During the incident, the end-to-end flow for alert creation and notification delivery experienced an average delay of 22 minutes. No alerts or notification payloads were dropped during the incident; all queued events were successfully processed and delivered as services recovered. Additionally, related Ops API endpoints and Web UI flows experienced elevated latency and intermittent errors. The disruption began at 15:30 UTC and was resolved by 17:10 UTC (total duration: 1 hour and 40 minutes).

Engineering teams were alerted immediately via backup disaster-alerting pipelines and began mitigation without delay. However, the disruption affected internal notification and coordination flows between cross-functional teams (including Customer Support and Incident Communications), which resulted in delays in publishing external Statuspage updates.

ROOT CAUSE

The incident was triggered when a newly released configuration change made redundant downstream service calls on every page load, causing a traffic spike. The configuration change, released between September 9, 2026, and September 11, 2026, was actively monitored for impact until early September 14, 2026. However, a traffic spike during US working hours caused unexpected issues. The downstream service began rate-limiting requests, and an aggressive retry strategy without sufficient backoff held worker threads open, leading to pool exhaustion and timeouts on incoming critical traffic.

REMEDIAL ACTIONS PLAN & NEXT STEPS

The incident was mitigated by disabling the feature flag that triggered the inter-service rate limiting.

We understand reliable access to Atlassian products is critical for your teams. We are prioritizing the following actions to prevent recurrence:

• Improve Service-to-Service Resilience
• Review and adjust rate-limiting configurations between internal services.
• Optimize retry strategies to prevent long-running transactions and keep the impact isolated to problematic point.
• Improve Architectural Isolation
• Refine the architecture of this core service to have more isolation between different transactions so that degradations in one transaction type do not impact unrelated critical flows.
• Improve Proactive Alerting
• Add early-warning alerts for thread pool saturation and elevated inter-service rate-limit responses before they impact end users.
• Implement backup alerting processes for customer support and incident communication paths

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

On September 14, 2026, Opsgenie and Jira Service Management experienced a disruption, and impacted users saw delayed alerts notification and inability to view the alerts in the user interface.

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

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

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

On September 3, 2026, some Jira Service Management users may have experienced errors viewing the Affected Services field or performance degradation on the web. The issue has now been resolved, and the service is operating normally for all affected customers.

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

We have identified the cause of the issue affecting Jira Service Management and are currently deploying a fix. We expect to see recovery shortly and will continue to monitor the situation closely.

We will provide the next update in 60 minutes, or sooner if there is a material update.

On 1st Sept 2026, between 04:22 UTC to 10:59 UTC, some Jira users may have experienced service disruptions.

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

SUMMARY

On August 27, 2026, between 03:51 and 04:35 UTC, Atlassian customers in the Western Europe and Southeast APAC regions were unable to reach Atlassian Cloud products, including Atlassian Analytics, Compass, Confluence, Focus, Guard, Jira, JPD, JSM, Opsgenie, Rovo Search, and Talent. The event was triggered by a defective code change to the routing layer of one of our proxy fleets. This led to HTTP 404 errors being served to all customer traffic through these proxy fleets in Western Europe and Southeast APAC regions. The incident was detected within 1 minute by our automated monitoring systems, and mitigated by rolling back to the previous configuration release, which put the proxy fleet into a known good state.

After the proxy fleet recovered, some Jira and Confluence customers (regardless of location) received HTTP 503 errors between 04:33 and 04:53 UTC as server fleets adjusted to the influx of traffic.

IMPACT

The overall impact was split into two discrete periods:

• First, on 27 August 2026, between 03:51 and 04:35 UTC on Atlassian Analytics, Compass, Confluence, Focus, Guard, Jira, JPD, JSM, Opsgenie, Rovo Search, and Talent. The incident caused service disruption to customer traffic originating from Western Europe and Southeast APAC regions, with HTTP 404 errors returned. There was no impact to customer API traffic, regardless of origin location.
• Second, on 27 August 2026, between 04:33 and 04:53 UTC, some Jira and Confluence customers regardless of location received HTTP 503 errors after the HTTP 404 errors were solved: ~32% of requests in ap-southeast-2, ~4% of requests in eu-west-1, ~2.5% of requests in us-west-2 and ap-southeast-1, and <1% of requests in all remaining global regions.

ROOT CAUSE

The event was triggered by a code change to one of our proxy fleets. However, there was a defect in the code deployed which was not detected by manual and automated testing. This led to a misconfiguration of a tenant lookup functionality in the proxy tier, which led to traffic not having a valid network path, resulting in HTTP 404 errors being served to all customer traffic through these proxy fleets in Western Europe and Southeast APAC regions.

After the proxy tier impact recovered, a second period of impact was caused to some Jira and Confluence customers. Due to the reduction of traffic served to Jira and Confluence by the proxy fleet, the Jira and Confluence service tiers had automatically scaled in the number of servers serving customer traffic. Once the proxy fleet functionality was restored, the surge of traffic overwhelmed the Jira service tier, which returned an elevated rate of HTTP 503s until it automatically scaled out again.

REMEDIAL ACTIONS PLAN & NEXT STEPS

We know that outages impact your productivity. While we have a number of testing and preventative processes in place, this specific issue wasn’t identified because the change was related to a very specific kind of edge case that was not picked up by our automated continuous deployment suites and manual test scripts.

We are prioritizing the following improvement actions to help avoid repeating this type of incident:

• Adding further deployment safeguards: The deployment pipeline for the configuration of the impacted proxy tier was using a legacy system and did not have the appropriate slow regional rollout features configured correctly. We have already added the correct safeguards, and we are moving this to our company standard deployment pipeline that includes all of our safety controls enabled by default. We are also auditing all networking services to validate that they are all on the new standard pipeline deployment service.
• Enhancing service fleet scaling policies: The auto scaling configuration for our Jira and Confluence service fleets was configured to scale in too aggressively. We are thoroughly reviewing and updating all of the complex Jira and Confluence auto scaling policies to ensure that this doesn’t occur again.

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

On 27 August 2026 UTC, Atlassian products including Jira Cloud, Jira Service Management and Confluence 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.

A public postmortem for this incident will be made available on this page when our full investigation of the incident has been completed.

The issues relating to loading Jira Cloud, Jira Service Management and Confluence are now in recovery. We'll continue to monitor closely to confirm stability and provide an update within one hour, or sooner as more information becomes available.

Our teams have identified a possible fix for the issues impacting Jira Cloud, Jira Service Management and Confluence. This is now being rolled out to impacted regions and we will update within one hour, or sooner if further information is available.

We are investigating an issue with accessing products that is impacting Confluence, Jira Cloud and Jira Serivce Management customers.
Our team is urgently investigating this issue and we will provide further details within one hour or sooner if information is available.

On 25th Aug 2026, some users may have experienced increased latency in email, mobile and slack notifications.

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

Our teams continue 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.

We will provide further updates within next two hours, or sooner if we have significant progress to share.

Our teams have taken few corrective measures to mitigate the issue in one of the impacted regions and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered.

We will provide further updates within next two hours, or sooner if we have significant progress to share.

Our teams have identified the impacted regions and are actively working to mitigate the issue. We will provide further updates within an hour, or sooner if we have significant progress to share.

On August 24, 2026, some JIRA, JSM, and Confluence users may have experienced performance degradation resulting in increased latency in email, mobile, and Slack notifications. The issue has been resolved for newly created notifications, and service is operating normally.

There may be older notifications that are being processed, and we expect them to be completed in next few hours.

We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience increased latency in email, mobile, and Slack notifications for JIRA, JSM, and Confluence. We will continue to share additional updates here as more information is available.

Our teams have identified three impacted regions, and continue to investigate the increased latency affecting email, mobile, and Slack notifications for JIRA, JSM, and Confluence.

On August 7th - 2026, between 10:27 UTC to 11:49 UTC, some users in the Central European region may have experienced service access issues.

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

Some customers experienced issues accessing affected services in the Central European region.

We have been able to apply the fix to mitigate the issues and we are seeing recovery. We continue to monitor the situation and should be fully recovered soon.

We should be able to provide more updates in the next one hour or earlier.

On August 7, 2026, JIRA, JWM, and JSM users may have experienced performance degradation when viewing issues and boards. The issue has now been resolved, and the service is operating normally for all affected customers.

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