Confluence: Confluence Degraded Performance
Timeline of updates
- resolved
Between 08:00 UTC to 08:50 UTC, some customers experienced degraded performance for Confluence The root cause was a change in user caching that caused slower back end response times. 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 Confluence’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 confluence.status.atlassian.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Confluence, started 2019-06-24 09:13 UTC, resolved after 40 min, 1 update(s).
- Title
- Confluence Degraded Performance
- Vendor
- Confluence
- Date
- URL
- https://rewindex.com/company/confluence/incidents/jqgr8kr39pyn
Confluence profileRecent Confluence incidentsAll outages on June 24, 2019Confluence in June 2019MarkdownJSON