Is ConfigCat Down?
Reachable from all 8 checked regions
Average response time: 180ms
Last checked · checks run every 6 hours
Official status page: https://status.configcat.com
ConfigCat uptime
Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 26 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
30-day history
26-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 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 18 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.
- 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 ConfigCat 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 ConfigCat 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