Confluence: Performance degradation for Forge app invocations
Timeline of updates
- resolved
At around 4am UTC, about 40 percent of Forge app invocations experienced high latency, with a portion of the requests failing, during a 15 minute time window. The scaling of the instances was misconfigured following a new deployment of the service, which needed manual intervention which took a few minutes to resolve the issue. Timeline: - 2024-01-31 04:00 UTC: impact started - 2024-01-31 04:03 UTC: incident detected - 2024-01-31 04:15 UTC: the incident was resolved and the impact ended This issue is now resolved and Forge is fully operational. We apologize for any inconveniences this may have caused to our customers, partners, and our developer community.
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 2024-01-31 06:03 UTC, resolved after 0 min, 1 update(s).
- Title
- Performance degradation for Forge app invocations
- Vendor
- Confluence
- Date
- URL
- https://rewindex.com/company/confluence/incidents/7d3vyf2rxcyd
Confluence profileRecent Confluence incidentsAll outages on January 31, 2024Confluence in January 2024MarkdownJSON