- Level
- confirmed
- Worst impact
- Degraded
- Components
- Confluence Automations
- Regions
- us, us-east-1
- Down Index
- 27of 100
What to do
Check whether you use Confluence Confluence Automations in us, us-east-1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 32m it lasted.
Anything that failed between 2025-10-15 13:43 UTC and 2025-10-15 16:16 UTC may need a replay.Subscribe to Confluence's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=confluence works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Confluence 4
- investigating
UI based Customer interactions are currently degraded and our team is actively investigating the same. We shall keep you informed of the progress in next 2 hours.
provider
- investigating
Atlassian team is actively investigating the issue with UI based Customer interactions. Existing automation rules continue to run without any issue. Accessing automation rules and creating new automation rules could lead to intermittent failures. We shall keep you informed of the progress in next 2 hours, if not sooner.
provider
- monitoring
We have recovered from a issue which saw degraded Automation experience. Impact Some Customers using Jira, Confluence, and Jira Service Management were not able to create or update Automation rules, and some Automation rules which triggered webhooks might have been throttled and require re-running. Current Status The incident has been mitigated and we continue to investigate the cause of this incident Next Steps We are continuing to monitor the service, and will provide further updates in the next two hours
provider
- resolved
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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-436906e0b3
Is Confluence still down?
No, this incident was resolved 2025-10-15 16:16 UTC. For Confluence's live state, see https://down.guide/confluence.
How long did it last?
2h 32m, from 2025-10-15 13:43 UTC to 2025-10-15 16:16 UTC, by the times Confluence posted.
What was affected?
Confluence named Confluence Automations in us, us-east-1.
What caused it?
Confluence hasn't published a root cause. If it does, it shows here.
Where does this come from?
Confluence's official status page, https://confluence.status.atlassian.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.