This incident has been resolved.

Our teams have identified and fixed the root cause of the issue that caused delay in executing Automation rules. This was caused due to scaling issues following on from the recent AWS outage. This issue is marked as resolved.

On October 20, 2025, Atlassian cloud services were impacted by an outage from a third-party provider, Amazon Web Services \(AWS\). While we have since resolved the immediate impact on our services, our teams are continuing to work on a full Post-Incident Review \(PIR\). AWS has published their summary of the event, which you can find here: [AWS Incident Summary](https://aws.amazon.com/message/101925/). We are continuing our own thorough internal investigation to understand the full impact on Atlassian services and to identify corrective actions to help prevent similar occurrences in the future. We are committed to transparency and will publish our public PIR on our [Statuspage](http://status.atlassian.com/) once this investigation is complete. We expect to publish this within the next 30 days. We sincerely apologize for the disruption this incident caused you and your teams. We appreciate your patience as we complete our review.

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

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