Flagsmith Status Page

Mar 3, 2026 · resolved Mar 3

### 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 completed a rollback to the previous stable release by 18:36 UTC, restoring the expected behaviour. ### What's Next? We are fixing the underlying serialisation issue at its source before the next production deployment. The next release will preserve the expected string-typed behaviour for numeric features — no customer action is required. To prevent this from happening again, we are adding integration tests that compare Core and Edge response types for the `/api/v1/environment-document/` endpoint, introducing a stricter review process for any changes that affect serialisation or data types, and requiring that test failures are investigated at their root cause before a fix is applied.

Jan 22, 2026 · resolved Jan 22

This incident has been resolved.

Oct 23, 2025 · resolved Oct 23

All issues with the asynchronous task processor have been resolved and all operations in the Flagsmith UI are working as expected.

Jul 23, 2025 · resolved Jul 23

The issue was caused by a spike of unusual traffic. This traffic has been mitigated and the issue is resolved.

Jun 18, 2025 · resolved Jun 18

The incident on the third party system was resolved at 15.11 UTC.