Is Flagsmith Down?
- Flagsmith's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 368 ms
Right now
The verdict is the worse of these two. How we decide
Flagsmith's status page
status.flagsmith.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| Edge API | Operational |
| Admin API | Operational |
| Admin Dashboard | Operational |
| Public Website | Operational |
| [DEPRECATED] SDK API | Operational |
FlareWarden checks
app.flagsmith.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 368 ms
- Checked
By region
- Ashburn reachable, 391 ms
- Chicago reachable, 284 ms
- Frankfurt reachable, 130 ms
- Johannesburg reachable, 525 ms
- London reachable, 91 ms
- Los Angeles reachable, 251 ms
- São Paulo reachable, 415 ms
- Tokyo reachable, 864 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Ashburn | 224 ms | 2 ms | 10 ms | 390 ms |
| Chicago | 111 ms | 1 ms | 24 ms | 284 ms |
| Frankfurt | 34 ms | 2 ms | 13 ms | 130 ms |
| Johannesburg | 230 ms | 1 ms | 79 ms | 525 ms |
| London | 47 ms | 2 ms | 8 ms | 91 ms |
| Los Angeles | 31 ms | 2 ms | 36 ms | 248 ms |
| São Paulo | 165 ms | 1 ms | 9 ms | 414 ms |
| Tokyo | 268 ms | 1 ms | 127 ms | 863 ms |
History
Incidents Flagsmith reported
Since Oct 22, 16 days · from status.flagsmith.com
- Incidents
- 1
- Major or critical
- 1
- Median to resolve
- 15m
- lasted 15m
critical ·
Flagsmith website availability
Measured by FlareWarden · app.flagsmith.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 335ms
Last 30 days
72-day clean streakMeasured by FlareWarden's own checks of app.flagsmith.com from multiple regions every 6 hours. Flagsmith's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 72 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
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 17 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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- 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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Flagsmith itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Flagsmith goes down
We check Flagsmith every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring