Flagsmith: Increased 502 responses to our Core API
Affected components: Admin APIAPIAdmin Dashboard
Timeline of updates
- investigating
Hi, We are experienced slightly elevated 502 errors returning from our Core API. We believe this is due to a recently introduced piece of code that is consuming more memory than it should be and are working on a fix.
- monitoring
We have deployed a fix and are monitoring our container memory consumption.
- investigating
We are still seeing elevated 502 errors and are continuing to investigate. These issues are isolated to our Core API only and seem to be affecting ~0.1% of Core API requests only. Our Edge API continues to be fully operational.
- monitoring
The errors have been resolved. We are continuing to monitor this.
- resolved
This incident has been resolved.
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 stspg.io (opens in new tab).