Confluence: Degraded Performance in Confluence
Timeline of updates
- resolved
On February 13, 2025, between 21:47 UTC and 22:15 UTC, some customers for Confluence Cloud in the Asia Pacific region experienced degraded performance and 500 errors. The issue was caused by a sudden surge in traffic and was resolved within 28 minutes.
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: none) posted by Confluence, started 2025-02-13 23:39 UTC, resolved after 0 min, 1 update(s).
- Title
- Degraded Performance in Confluence
- Vendor
- Confluence
- Date
- URL
- https://rewindex.com/company/confluence/incidents/zmr3cmsr23cz
Confluence profileRecent Confluence incidentsAll outages on February 13, 2025Confluence in February 2025MarkdownJSON