Jira: Wide ranging performance regression
Timeline of updates
- resolved
Between 15 Feb 23 2:37 AM UTC and 16 Mar 23 4:00 AM UTC, all customers experienced an average extra latency of 100 milliseconds on all API requests for Jira Work Management, Jira Service Management, and Jira Software. The root cause was the addition of circuit breaker functionality to our caching infrastructure that caused increased CPU utilisation in all paths. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The conditions that cause the bug have been addressed and we're actively working on a permanent fix. The issue has been resolved and the service is operating normally.
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 2023-03-16 00:45 UTC, resolved after 5 d, 1 update(s).
- Title
- Wide ranging performance regression
- Vendor
- Jira
- Date
- URL
- https://rewindex.com/company/jira/incidents/xkp08y92hhfr
Jira profileRecent Jira incidentsAll outages on March 16, 2023Jira in March 2023MarkdownJSON