Jira: Degraded Performance for JIRA and JSM
Timeline of updates
- resolved
Between 28 July 2024, 23:00 UTC, and 29 July 2024, 10:22 UTC, some customers experienced performance degradation issues for Jira and JSM. The root cause was a problem with the propagation of configuration in our system during the migration of one of the database instances hosting your Jira cloud site. This caused the Jira application not to correctly balance load against database nodes within the database cluster, leading to CPU saturation of the database. 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: none) posted by Jira, started 2024-07-29 08:27 UTC, resolved after 3.0 h, 1 update(s).
- Title
- Degraded Performance for JIRA and JSM
- Vendor
- Jira
- Date
- URL
- https://rewindex.com/company/jira/incidents/sxfmcmsz2xb8
Jira profileRecent Jira incidentsAll outages on July 29, 2024Jira in July 2024MarkdownJSON