Is Cookiebot Down?

No — Cookiebot is up

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

Right now

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

Cookiebot's status page

status.cookiebot.com · read 4 minutes ago · checked every 3 minutes

Operational

Cookiebot's components, as its status page reports them
Component	Status
CMP - Consent Banner	Operational
Partner API	Operational
New Admin UI	Operational
Cookiebot Manager	Operational

Open their status page

FlareWarden checks

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

Reachable

Regions up: 8 of 8
Response: 708 ms
Checked: 26 minutes ago

By region

Ashburn reachable, 399 ms
Chicago reachable, 388 ms
Johannesburg reachable, 2424 ms
London reachable, 132 ms
Los Angeles reachable, 755 ms
Singapore reachable, 407 ms
São Paulo reachable, 513 ms
Tokyo reachable, 650 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	12 ms	4 ms	11 ms	221 ms
Chicago	18 ms	1 ms	10 ms	174 ms
Johannesburg	7 ms	159 ms	166 ms	1537 ms
London	52 ms	3 ms	11 ms	103 ms
Los Angeles	87 ms	2 ms	12 ms	284 ms
Singapore	84 ms	2 ms	8 ms	308 ms
São Paulo	25 ms	2 ms	10 ms	254 ms
Tokyo	160 ms	1 ms	8 ms	421 ms

We check that cookiebot.com loads, not every feature behind it. Test it yourself

History

Incidents Cookiebot reported

Since Oct 22, 15 days · from status.cookiebot.com

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

No incidents reported in this window.

Cookiebot website availability

Measured by FlareWarden · cookiebot.com

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

Last 30 days

57-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

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

What Cookiebot does

Cookiebot is a consent management platform used by websites to show a cookie banner, record what each visitor agreed to, and hold analytics and marketing scripts back until consent is given. Its banner script loads on the customer's own pages from Cookiebot, which makes it a third-party dependency of every page view on a site that uses it.

What an outage looks like

The consent banner does not appear on a site that normally shows one, or appears and fails to record a choice. Because tags are held back until consent is recorded, analytics and advertising scripts may never fire, so traffic data goes quiet while the site itself serves pages normally. Administrators may be unable to sign in to change banner settings or read scan reports.

What to do about it

Read status.cookiebot.com, which reports CMP - Consent Banner, Admin UI, New Admin UI, Cookiebot Manager and Partner API as separate components. The banner row is the one that affects visitors; the admin rows affect only your team. If the banner component is degraded, expect a gap in analytics for the period and note it before someone reads the dip as a traffic collapse.

Is it down for everyone, or just you?

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

Cookiebot outage FAQ

My site is up but analytics have gone silent. Could that be Cookiebot?

Yes, and it is the failure mode worth knowing about. Cookiebot holds analytics and marketing tags until consent is recorded, so if the consent banner cannot load or cannot register a choice, those tags never fire while your pages serve normally. The result is a clean-looking site with missing data. Check the CMP - Consent Banner row on status.cookiebot.com before investigating your analytics tool.

Does a Cookiebot outage break my website for visitors?

Your pages continue to be served, since they come from your own infrastructure. What changes is the consent layer: the banner may not render, and anything gated behind consent stays off. Depending on how the script is embedded, a slow or failing third-party request can also delay page rendering, so check how your site loads for a real visitor rather than assuming no visible effect.

Am I out of compliance if the banner does not load during an outage?

The practical position during an incident is usually the conservative one: with no consent recorded, consent-gated scripts do not run, so tracking does not happen without permission. This is a general observation about how consent gating behaves and not legal advice. If a compliance obligation depends on the banner being present, record the incident window and raise it with whoever owns that obligation.

Is it Cookiebot or my own tag setup?

Compare scope and timing. A broken tag configuration or a recent change to your consent categories affects one site, often one page template, and coincides with a change you made. A Cookiebot incident affects every site using the service at once. Check the status page first, then compare against your own deployment history before you start editing tag settings.

Will visitor consent choices recorded before the outage still apply?

Consent decisions already stored on a returning visitor's browser are not erased by a service incident, so people who previously made a choice generally keep it. New visitors arriving during an incident are the ones with nothing recorded. Cookiebot does not publish behaviour for every failure mode, so treat the incident window as a period with fewer recorded consents rather than assuming existing ones changed.

How we measure this

We request Cookiebot'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 Cookiebot 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 Cookiebot 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 Cookiebot goes down

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