We started checking Flagsmith on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Flagsmith reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Flagsmith's own status page declared. Below it, any public chatter we saw about Flagsmith and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Flagsmith's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Flagsmith in the last 24 hours, which is not evidence that nothing is wrong.
Flagsmith's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Flagsmith's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Flagsmith next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
447
US-West
99.71%
348
Europe
99.68%
317
Asia-Pacific
99.48%
193
Their declared record
Flagsmith's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Admin and SDK API outageMajor outage
Oct 28, 2026, 9:56 PM UTC to Oct 28, 2026, 10:12 PM UTC (15 min)resolved
Sep 10, 2026, 2:43 PM UTC to Sep 10, 2026, 4:10 PM UTC (1h 27m)resolved
their latest update (Sep 10, 2026, 4:10 PM UTC): This incident has been resolved.
Numeric values incorrectly being converted to numbers in environment documentsAll systems operational
Mar 3, 2026, 5:00 PM UTC to Mar 3, 2026, 5:00 PM UTC (0 min)postmortem published
their latest update (Mar 4, 2026, 4: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 …
Data parsing issues in Edge APIMinor incident
Jan 22, 2026, 4:56 PM UTC to Jan 22, 2026, 6:40 PM UTC (1h 44m)resolved
their latest update (Jan 22, 2026, 6:40 PM UTC): This incident has been resolved.
Task processor downPartial outage
Oct 23, 2025, 10:08 AM UTC to Oct 23, 2025, 2:49 PM UTC (4h 42m)resolved
their latest update (Oct 23, 2025, 2:49 PM UTC): All issues with the asynchronous task processor have been resolved and all operations in the Flagsmith UI are working as expected.
Jul 23, 2025, 9:01 PM UTC to Jul 23, 2025, 9:17 PM UTC (16 min)resolved
their latest update (Jul 23, 2025, 9: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 loadingMajor outage
Jun 18, 2025, 1:46 PM UTC to Jun 18, 2025, 7:43 PM UTC (5h 57m)resolved
their latest update (Jun 18, 2025, 7:43 PM UTC): The incident on the third party system was resolved at 15.11 UTC.
Public Website DownAll systems operational
Jun 9, 2025, 10:13 AM UTC to Jun 9, 2025, 10:13 AM UTC (0 min)postmortem published
their latest update (Jun 11, 2025, 8: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…
Small number of intermittent requests to Edge API failingMinor incident
Dec 16, 2024, 7:07 PM UTC to Dec 19, 2024, 2:04 PM UTC (2d 18h)postmortem published
their latest update (Dec 20, 2024, 5: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 issue…
Issues persisting identities with empty trait valuesMinor incident
Dec 4, 2024, 11:30 AM UTC to Dec 4, 2024, 11:30 AM UTC (0 min)resolved
their latest update (Dec 4, 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 t…
Showing the 10 most recent of 37 incidents Flagsmith has declared in the history we hold.
These entries are Flagsmith's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Flagsmith's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.