Is Flagsmith Down?
Reachable from all 8 checked regions
Average response time: 362ms
Last checked · checks run every 6 hours
Official status page: https://status.flagsmith.com
Flagsmith uptime
Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 25 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
30-day history
25-day clean streakReachability by region
Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.
What Flagsmith does
Flagsmith is a feature flag and remote configuration service. Teams define flags in a dashboard and applications read them through SDKs, either by calling Flagsmith's Edge API or by evaluating a downloaded environment document locally. It is open source and can be self-hosted, so the hosted platform is one deployment option among several rather than the only way to run it.
What an outage looks like
The dashboard at app.flagsmith.com fails to load, or flag changes save but never take effect in running applications. The applications themselves often keep working, because SDKs in local evaluation mode serve flags from the environment document they last downloaded. Services that restart or scale up mid-incident are the ones at risk, since they start with nothing cached and fall back to code defaults.
What to do about it
Check status.flagsmith.com, which separates Edge API, Admin API, Admin Dashboard and Public Website. An Admin Dashboard incident does not stop flag evaluation; an Edge API incident does. Hold deploys and avoid autoscaling events while it is unresolved, since new instances start without a cached environment document. Self-hosted installations are unaffected by an incident on the hosted platform.
Is it down for everyone, or just you?
If this page says Flagsmith is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.
Related services
Flagsmith outage FAQ
Does my application break when Flagsmith is down?
Which component matters for my application?
Will a flag change I make now reach production?
Does this affect self-hosted Flagsmith?
How we measure this
- We request Flagsmith's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Flagsmith publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.
Get alerted when Flagsmith goes down
This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring