Flagsmith outage, 4 March 2026
Numeric values incorrectly being converted to numbers in environment documents
- Started
- Resolved
- 3 Mar 2026, 17:00 UTC - reported afterwards
- Impact
- Not stated
Last update from Flagsmith
### What Happened On Monday 3rd March at around 17:00 UTC, we deployed a release to the Edge API that inadvertently changed the JSON types returned for integer-typed feature state values. Values that had previously been returned as JSON strings \(e.g., `"300"`\) began returning as JSON numbers \(e.g., `300`\). The change affected the `/api/v1/environment-document/` endpoint used by SDKs operating in local evaluation mode. Features stored as strings, booleans, or null values were not affected, and the Core API was not affected. Our existing test suite did not catch the type change before it reached production. The issue was reported at 18:12 UTC, classified as P0 at 18:27 UTC, and we comple...
Read the full incident on the official Flagsmith status page
Is Flagsmith down now?
This page is the record of one past incident. For the live status, see Is Flagsmith down right now? - it reads the official status page every 2 minutes.