- Service Status
- /
- ConfigCat

Is ConfigCat Down?
- ConfigCat's status page
- Not available · we could not read it
- FlareWarden checks
- Website reachable · 8 of 8 regions · 235 ms
Right now
We could not read ConfigCat's status page, so the verdict rests on our checks. Check it yourself How we decide
FlareWarden checks
app.configcat.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 235 ms
- Checked
By region
- Ashburn reachable, 259 ms
- Chicago reachable, 320 ms
- Johannesburg reachable, 277 ms
- London reachable, 133 ms
- Los Angeles reachable, 288 ms
- San Jose reachable, 183 ms
- Singapore reachable, 195 ms
- Tokyo reachable, 227 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Ashburn | 103 ms | 1 ms | 8 ms | 257 ms |
| Chicago | 106 ms | 2 ms | 13 ms | 318 ms |
| Johannesburg | 208 ms | 1 ms | 6 ms | 276 ms |
| London | 14 ms | 3 ms | 8 ms | 129 ms |
| Los Angeles | 145 ms | 3 ms | 12 ms | 284 ms |
| San Jose | 24 ms | 2 ms | 8 ms | 181 ms |
| Singapore | 114 ms | 2 ms | 7 ms | 192 ms |
| Tokyo | 132 ms | 1 ms | 11 ms | 225 ms |
History
ConfigCat website availability
Measured by FlareWarden · app.configcat.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 217ms
Last 30 days
72-day clean streakMeasured by FlareWarden's own checks of app.configcat.com from multiple regions every 6 hours. ConfigCat'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 ConfigCat does
ConfigCat is a hosted feature flag service. Developers define flags in a dashboard and ConfigCat distributes the resulting configuration through a CDN to SDKs embedded in applications. Teams use it to turn features on and off without deploying and to run gradual rollouts, which puts it in the request path of production software.
What an outage looks like
Less than people expect. Applications keep evaluating flags from the configuration their SDK already cached, so the visible symptom is usually that a flag change made in the dashboard never reaches running applications. The dashboard itself may fail to load or save. Processes starting with an empty cache are the ones genuinely at risk.
What to do about it
Check ConfigCat's status page, then confirm whether anything is actually broken: a failed refresh does not erase configuration an SDK has already downloaded, so most applications continue on their last known good values. Hold deployments that would start instances with a cold cache. Teams running the ConfigCat Proxy have a local copy to serve from.
Is it down for everyone, or just you?
If this page says ConfigCat 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
ConfigCat outage FAQ
Does my application break when ConfigCat is down?
Will a flag change I make now reach my users?
What about processes that start during the outage?
Does the ConfigCat Proxy help here?
How we measure this
- We request ConfigCat'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 ConfigCat 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 ConfigCat 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. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.
Get alerted when ConfigCat goes down
We check ConfigCat 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


