FlagSmith Outage History
FlagSmith is up right nowFlagSmith had 11 outages in the last 2 years totaling 82h 43m of downtime — averaging 0.5 incidents per month.
There were 11 FlagSmith outages since July 4, 2024 totaling 82h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.
Data parsing issues in 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
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
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.
Flagsmith dashboard not loading
Timeline · 5 updates
- investigating Jun 18, 2025, 01:46 PM UTC
We are currently investigating alerts that app.flagsmith.com is not loading.
- investigating Jun 18, 2025, 01:47 PM UTC
It appears that the issue is related to our third party hosting provider for the Flagsmith dashboard. We are following up with them.
- monitoring Jun 18, 2025, 01:52 PM UTC
It looks like the issue has been resolved on the provider's side. We are monitoring and validating.
- monitoring Jun 18, 2025, 01:52 PM UTC
We are continuing to monitor for any further issues.
- resolved Jun 18, 2025, 07:43 PM UTC
The incident on the third party system was resolved at 15.11 UTC.
Public Website Down
Timeline · 2 updates
- resolved Jun 09, 2025, 10:13 AM UTC
Our website was down momentarily this morning, but it did not affect our main application (app.flagsmith.com). Users were unable to view our marketing page due to an operational issue with management of our content management system. We'll share a post mortem in 24 hours.
- postmortem Jun 11, 2025, 08:06 AM UTC
We leverage an outside provider as a content management system for our public website. We had an outage for two hours due to an internal operational error with how we managed our account. We have since updated our processes with how we manage our account to prevent the issue from occurring moving forward
Small number of intermittent requests to Edge API failing
Timeline · 9 updates
Issues persisting identities with empty trait values
Timeline · 1 update
- resolved Dec 04, 2024, 03:55 PM UTC
Resolved at: 15:22 UTC A bug in the validation logic traits meant that identities with traits that have a value of `""` would cause an exception, resulting in the identity not being stored correctly when updates were made. This issue was resolved at 15:22 UTC, any new requests to retrieve an identity's flags, or store their traits will correctly store those traits.
Increased API latency
Timeline · 5 updates
- investigating Nov 05, 2024, 10:19 AM UTC
We are currently investigating this issue.
- identified Nov 05, 2024, 10:25 AM UTC
The cause is due to a migration applied to the production database taking more resources than we anticipated. The migration has been completed and the load is normalising. We are monitoring and managing the load. Currently, while this issue is ongoing, it is not possible to create new environments.
- monitoring Nov 05, 2024, 10:32 AM UTC
API latency is back to normal. We are continuing to monitor.
- monitoring Nov 05, 2024, 10:37 AM UTC
Environment creation is functional again now.
- resolved Nov 05, 2024, 01:28 PM UTC
This incident has been resolved.
Core API outage
Timeline · 2 updates
Core API Outage
Timeline · 1 update
- resolved Jul 04, 2024, 08:36 AM UTC
Our Core API was overwhelmed by massive traffic spike, causing the core SQL database to become extremely slow. This led to ECS tasks failing the health checks, prompting the load balancer to start and stop new tasks, which in turn added more load to the already maxed-out database. We tried several approaches to rate limiting the source of the traffic, but eventually had to temporarily stop traffic at the load balancer for 2 minutes in order to stabilise the system. We are working on implementing AWS API Gateway to include rate limiting at the gateway level to avoid these sort of incidents in the future.