Jira: Unable to perform UI Operations
Timeline of updates
- 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.
From Jira’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on jira-software.status.atlassian.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Jira, started 2025-10-15 13:43 UTC, resolved after 2.5 h, 1 update(s).
- Title
- Unable to perform UI Operations
- Vendor
- Jira
- Date
- URL
- https://rewindex.com/company/jira/incidents/khl3w6s9br2g
Jira profileRecent Jira incidentsAll outages on October 15, 2025Jira in October 2025MarkdownJSON