Is GrowthBook Down?

No — GrowthBook is up

GrowthBook's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 334 ms

Right now

The verdict is the worse of these two. How we decide

GrowthBook's status page

status.growthbook.io · read just now · checked every 3 minutes

Operational

GrowthBook's components, as its status page reports them
Component	Status
GrowthBook Cloud App	Operational
Api	Operational
CDN	Operational

Open their status page

FlareWarden checks

growthbook.io from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 334 ms
Checked: just now

By region

Chicago reachable, 231 ms
London reachable, 227 ms
Los Angeles reachable, 244 ms
San Jose reachable, 464 ms
Singapore reachable, 199 ms
Sydney reachable, 477 ms
Tokyo reachable, 511 ms
Toronto reachable, 324 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Chicago	150 ms	1 ms	11 ms	226 ms
London	47 ms	26 ms	21 ms	148 ms
Los Angeles	168 ms	2 ms	12 ms	236 ms
San Jose	385 ms	5 ms	11 ms	456 ms
Singapore	142 ms	2 ms	12 ms	194 ms
Sydney	208 ms	1 ms	7 ms	473 ms
Tokyo	316 ms	1 ms	8 ms	433 ms
Toronto	251 ms	2 ms	25 ms	320 ms

We check that growthbook.io loads, not every feature behind it. Test it yourself

History

Incidents GrowthBook reported

Since Oct 27, 10 days · from status.growthbook.io

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

GrowthBook website availability

Measured by FlareWarden · growthbook.io

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 216ms

Last 30 days

59-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of growthbook.io from multiple regions every 6 hours. GrowthBook's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 59 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What GrowthBook does

GrowthBook is an open-source feature flagging and experimentation platform. Applications fetch flag definitions from its CDN and evaluate them locally, then send experiment exposure data back for analysis against a warehouse the team already runs. It is offered both as GrowthBook Cloud and as software teams host themselves, so two customers can depend on very different infrastructure under the same name.

What an outage looks like

Feature flags stop updating and applications keep serving whatever values they last fetched, so a rollout freezes rather than failing loudly. Changes saved in the GrowthBook interface do not reach running services. If the SDK cannot reach the CDN at startup it falls back to the defaults compiled into your code, which can quietly turn a live feature off for new instances.

What to do about it

Read status.growthbook.io, which reports GrowthBook Cloud App, Api and CDN as three components with 90 days of uptime each. If CDN is the affected row, running applications are still serving cached flag values and the risk is stale configuration, not an error. Confirm your SDK has a sensible fallback for a failed fetch before changing anything, and hold flag changes until the CDN row recovers so you are not reasoning about a rollout you cannot deliver.

Is it down for everyone, or just you?

If this page says GrowthBook 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.

Test it yourself

Related services

GrowthBook outage FAQ

I self-host GrowthBook. Does the status page apply to me?

No. status.growthbook.io reports GrowthBook Cloud App, Api and CDN, which are the hosted service. A self-hosted deployment runs on your own infrastructure and database, so an incident there says nothing about your instance and an all-clear does not clear you either. Check your own containers, MongoDB and the CDN or proxy you serve flag payloads from before looking at GrowthBook's page.

My flags are not updating but the app is fine. Is GrowthBook down?

That is the usual shape of a CDN incident. GrowthBook SDKs fetch flag definitions and evaluate them locally, so an application keeps running on the last payload it received and nothing errors. The symptom is a rollout that will not move rather than a failure. Check the CDN row on status.growthbook.io before debugging your own targeting rules.

What happens to my A/B test data during a GrowthBook outage?

Experiment analysis reads from your own data warehouse rather than from GrowthBook's storage, so historical results are held where you keep your event data. What an outage interrupts is the interface for querying and displaying them. GrowthBook does not publish a guarantee covering exposure events sent during an incident, so confirm the affected window against your warehouse rather than assuming completeness.

Can a GrowthBook outage break my application?

It can change behaviour rather than break it. If the SDK cannot fetch a payload it uses the fallback value in your code, so a newly started instance may serve defaults while older instances keep the flags they already have. That split is the risk worth planning for: set deliberate fallbacks and cache payloads locally so an unreachable CDN produces a known state instead of an accidental one.

Is GrowthBook down or is it my SDK integration?

Compare scope. An integration fault affects one application or one SDK version and usually shows an error in your own logs, while a GrowthBook incident stops flag updates for every consumer at once. status.growthbook.io publishes per-component uptime graphs, so a dip on CDN or Api confirms the platform side. Fetching the flag payload URL directly is the fastest local check.

How we measure this

We request GrowthBook'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 403 or 429 means 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 GrowthBook 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 GrowthBook 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 GrowthBook goes down

We check GrowthBook 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

Free plan available No credit card required