Minor impactResolvedCollaboration

Confluence incident: Unable to perform UI Operations

Confluence reported this minor-impact incident on its official status page on Oct 15, 2025, 13:43 UTC. It was resolved after 2h 32m.

Right now Confluence is operational. Live Confluence status →

🔔 Get alerted when Confluence has issuesFree · email alerts · no credit card
Oct 15, 2025, 13:43 UTC
started
Oct 15, 2025, 16:16 UTC
resolved
2h 32m
duration
Minor
impact

Affected components

  • Confluence Automations
  1. resolvedOct 15, 2025, 16:16 UTC

    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.

  2. monitoringOct 15, 2025, 15:26 UTC

    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

  3. investigatingOct 15, 2025, 14:34 UTC

    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.

  4. investigatingOct 15, 2025, 13:43 UTC

    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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Confluence's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

How often does Confluence have incidents?

Confluence reported 7 incidents in the last 90 days, 4 of them major or critical. A typical incident lasted 3h 40m. See Confluence's uptime and incident history

Confluence incident on Oct 15, 2025: Unable to perform UI Operations · APIStatus.watch