FlagSmith Outage History
FlagSmith is up right nowPingoru has recorded 37 incidents for FlagSmith: 4 in the last 12 months and 2 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 1 | 2 of 720 (0%) |
| October 2026 | 1 | 0 of 744 (0%) |
| November 2026 | 0 | 0 of 81 (0%) |
Incidents, newest first
Critical October 28, 2026 Admin and SDK API outage 15m Admin API, Admin Dashboard, [DEPRECATED] SDK API
Started Oct 28, 2026, 09:56 PM UTC· resolved Oct 28, 2026, 10:12 PM UTC
- identified Oct 28, 2026, 09:56 PM UTC
We have identified the issue and working on getting it resolved
- resolved Oct 28, 2026, 10:12 PM UTC
Incident resolved.
Minor September 10, 2026 Delays processing flag changes 1h 27m Admin API, Admin Dashboard
Started Sep 10, 2026, 02:43 PM UTC· resolved Sep 10, 2026, 04:10 PM UTC
- investigating Sep 10, 2026, 02:43 PM UTC
We are seeing a large amount of tasks consuming our asynchronous task processor, resulting in delays to processing flag changes.
- investigating Sep 10, 2026, 02:44 PM UTC
We are continuing to investigate this issue.
- monitoring Sep 10, 2026, 03:09 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 10, 2026, 04:10 PM UTC
This incident has been resolved.
Notice March 3, 2026 Numeric values incorrectly being converted to numbers in environment documents 1h 36m
Started Mar 03, 2026, 05:00 PM UTC· resolved Mar 03, 2026, 06:36 PM UTC
- resolved Mar 03, 2026, 05:00 PM UTC
Environment documents were being rendered with numeric values cast as numbers in the JSON responses, instead of the previous behaviour where the values were returned as strings. This caused issues for statically typed languages in particular.
- postmortem Mar 04, 2026, 04:27 PM UTC
### 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.
Minor January 22, 2026 Data parsing issues in Edge API 1h 44m Edge API
Started Jan 22, 2026, 04:56 PM UTC· resolved Jan 22, 2026, 06:40 PM UTC
- 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.
Major October 23, 2025 Task processor down 4h 41m Admin Dashboard
Started Oct 23, 2025, 10:08 AM UTC· resolved Oct 23, 2025, 02:49 PM UTC
- 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.
Minor July 23, 2025 Delayed asynchronous task processing 15m Edge API, Admin API, Admin Dashboard
Started Jul 23, 2025, 09:01 PM UTC· resolved Jul 23, 2025, 09:17 PM UTC
- 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.
Critical June 18, 2025 Flagsmith dashboard not loading 5h 56m Admin Dashboard
Started Jun 18, 2025, 01:46 PM UTC· resolved Jun 18, 2025, 07:43 PM UTC
- 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.
Notice June 9, 2025 Public Website Down – Public Website
Started Jun 09, 2025, 10:13 AM UTC· resolved Jun 09, 2025, 10:13 AM UTC
- 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
Minor December 16, 2024 Small number of intermittent requests to Edge API failing 2d 18h Edge API
Started Dec 16, 2024, 07:07 PM UTC· resolved Dec 19, 2024, 02:04 PM UTC
- investigating Dec 16, 2024, 07:07 PM UTC
We are currently investigating the Edge API sporadically timing out some requests or refusing connections.
- investigating Dec 16, 2024, 07:10 PM UTC
The issue seems to only be affecting clients connecting to the us-east-2 region. We're currently redirecting traffic away from the region.
- monitoring Dec 16, 2024, 08:17 PM UTC
We have migrated all traffic away from us-east-2 and are monitoring the impact.
- investigating Dec 16, 2024, 09:59 PM UTC
We have had further reports of similar issues following the migration of traffic away from us-east-2, we are continuing to investigate.
- investigating Dec 16, 2024, 11:43 PM UTC
We have passed on all of the troubleshooting information to our infrastructure provider and are awaiting further information from them on this issue. If you are affected by this issue, please get in touch with us at [email protected] with any information that you can share so we can identify this intermittent issue.
- identified Dec 17, 2024, 03:49 PM UTC
The issue has been isolated to a specific component in our hosting provider's network infrastructure. We are working with them, and escalating to get the issue resolved.
- monitoring Dec 18, 2024, 06:56 PM UTC
Our infrastructure provider has confirmed they were intermittently unavailable between December 14, 01:00 UTC and December 17, 22:50 UTC. We are working with affected customers to confirm that this issue is resolved.
- resolved Dec 19, 2024, 02:04 PM UTC
We have received confirmation from multiple customers in the US east region now that the issue has been resolved.
- postmortem Dec 20, 2024, 05:20 PM UTC
## What Happened On Monday 16th December at around 14:25 GMT, we started receiving reports from customers that they were seeing elevated errors in their monitoring regarding connections to the Flagsmith API. Our investigation suggested that there were no application level issues in the Flagsmith platform. Since all customer reports were coming from Eastern US regions, we moved traffic away from the region, redirecting to our US west region. By this time, we were also able to carry out our own testing using infrastructure set up in US east. Our testing, and feedback from our customers showed that moving the traffic away did not resolve the issue. At 19:15 GMT, we opened a ticket with our infrastructure partner. Their investigations also confirmed that there were no issues with the Flagsmith platform itself. At 21:53 GMT, we created a ticket directly with our infrastructure provider \(AWS\) for them to investigate. At around 23:30 GMT on 16th December, we implemented a work around by creating a new DNS record to point directly to our infrastructure in US east, bypassing the latency based routing \(as provided by AWS Global Accelerator\). We shared this with customers experiencing the issues, and they confirmed that it resolved the issue. From here, we continued to investigate the issue with AWS support, providing them with additional information based on our testing, and reports from our customers. On 18th December at 17:58, we received the following information from AWS confirming that there had been an issue with Global Accelerator in the US East region. > The team confirmed that between December 13 5:00 PM PST and December 17 2:50 PM PST, AWS Global Accelerator experienced intermittent connection failures for client traffic served by the Ashburn, Virginia edge location. The issue has been resolved and the service is operating normally. Following this, we were able to confirm that the issue was no longer reproducible for us, or for our customers. ## What’s Next? We have requested, and are currently waiting for, a full post-mortem from the AWS team which may affect our next steps. In the meantime, we have begun looking at alternative solutions for the Global Accelerator that we may be able to keep as a cold standby in case of similar issues in the future.
Minor December 4, 2024 Issues persisting identities with empty trait values 1d 3h
Started Dec 04, 2024, 11:30 AM UTC· resolved Dec 05, 2024, 03:22 PM UTC
- resolved Dec 04, 2024, 11:30 AM 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.
Notice November 5, 2024 Increased API latency 3h 9m Admin API, Admin Dashboard
Started Nov 05, 2024, 10:19 AM UTC· resolved Nov 05, 2024, 01:28 PM UTC
- 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.