FlagSmith Outage History
FlagSmith is up right nowFlagSmith had 4 outages in the last 2 years totaling 6h 41m of downtime — averaging 0.2 incidents per month.
There were 4 FlagSmith outages since July 23, 2025 totaling 6h 41m of downtime. Each is summarised below — incident details, duration, and resolution information.
Data parsing issues in Edge API
Affected: Edge API
Timeline · 5 updates
- identified Jan 22, 2026, 04:56 PM UTC
We are receiving reports of failing Edge API requests for a small subset of Flagsmith environments. We have identified the problem and the fix is underway.
- monitoring Jan 22, 2026, 05:30 PM UTC
A fix has been deployed to all regions. We have resolved the failures and are monitoring further impact.
- identified Jan 22, 2026, 05:51 PM UTC
The applied fix has not resolved the issue for all customers. New version being rolled out now with a fix for all customers.
- monitoring Jan 22, 2026, 06:02 PM UTC
The latest update has resolved the issue in all regions. We are continuing to monitor.
- resolved Jan 22, 2026, 06:40 PM UTC
This incident has been resolved.
Task processor down
Affected: Admin Dashboard
Timeline · 3 updates
- investigating Oct 23, 2025, 10:08 AM UTC
We are currently investigating an issue with the Flagsmith asynchronous task processor, impacting flag change events, webhooks and audit logs in the Flagsmith UI.
- monitoring Oct 23, 2025, 10:26 AM UTC
We have resolved the issue with the task processor and are no longer seeing issues with the Flagsmith UI. We are continuing to monitor performance of the task processor.
- resolved Oct 23, 2025, 02:49 PM UTC
All issues with the asynchronous task processor have been resolved and all operations in the Flagsmith UI are working as expected.
Delayed asynchronous task processing
Affected: Edge APIAdmin APIAdmin Dashboard
Timeline · 2 updates
- investigating Jul 23, 2025, 09:01 PM UTC
We're seeing a delay in processing tasks by our asynchronous task processor, meaning that changes made in the dashboard may take longer to reflect in the API.
- resolved Jul 23, 2025, 09:17 PM UTC
The issue was caused by a spike of unusual traffic. This traffic has been mitigated and the issue is resolved.