Skip to content
Back to insights

The Black Friday weekend runbook for Cloudflare

Hour by hour from Thanksgiving night to the Tuesday after Cyber Monday - what to watch on Cloudflare, what each signal means and what to do first.
Ilyas Esmail

Ilyas Esmail

Founder & CEO

Key takeaways

  • Write the weekend down as shifts, with a named person and a handover note for each one, before Thursday.
  • Watch four signals - challenge rate on checkout, origin errors, cache hit ratio and payment confirmations - and agree in advance what level of each means act.
  • When real shoppers are challenged, narrow the rule that caught them; don't switch off the protection for the whole zone.
  • Book the review for Tuesday, while everyone still remembers why each weekend change was made.

Black Friday falls on 27 November this year and Cyber Monday on 30 November. For most online shops those four days carry more revenue than any other stretch of the year, and they run through a weekend when the people who know the Cloudflare account would rather be somewhere else.

Preparation is covered in our 2026 retail plan for Cloudflare: settle the configuration, write the exceptions, agree the freeze. This post is the part that comes after, the weekend itself. It is written as a runbook, so you can copy it into your own and put names against each shift.

The weekend as shifts

Treat the weekend as five shifts. Each one has an owner, a short list of things to check, and a handover note at the end.

  1. Thursday 26 November, evening

    Final checks

    Configuration matches the baseline, alerts reach the on-call channel, and the first sale email's send time is confirmed.

  2. Friday 27 November, from midnight

    Black Friday opens

    The heaviest automated traffic arrives in the first hours. Watch checkout and limited-stock pages closely.

  3. Saturday 28 and Sunday 29 November

    Weekend watch

    Lower staff, steady traffic. Most changes now are exceptions for clients the rules caught on Friday.

  4. Monday 30 November

    Cyber Monday

    A second peak, often with new promo codes and online-only offers. Treat it as a fresh launch.

  5. Tuesday 1 December

    Review

    Go through every change made since Thursday and decide which ones stay.

Agree the time zone for the whole runbook before you start. A shop selling across the U.S. has its midnight at a different hour on each coast, and a team in Europe or Africa watching it needs one clock to talk in.

The four signals to watch

Dashboards show dozens of numbers. During a peak, four of them tell you almost everything. Decide before Thursday what "normal for a sale" looks like for each, using last year's peak or your biggest campaign since, and write down the level that means act.

SignalWhere to see itWhat it usually means when it moves
Challenge and block rate on checkout and sign-inSecurity Events, filtered by pathA rule is catching shoppers, or an attack has started. Look at who is being challenged before deciding which.
Origin errors (5xx and Cloudflare 52x)Traffic analytics, by status codeThe origin is struggling with load or a release, or Cloudflare cannot reach it. Usually not a WAF problem.
Cache hit ratio on sale pagesCache analytics, by pathA sale page is bypassing the cache, often because of a query string or a cookie, and sending every visitor to the origin.
Payment confirmations receivedYour payment provider and order systemIf orders are placed but confirmations stop, a rule may be blocking the provider's webhooks.

The last one is outside Cloudflare, which is exactly why it belongs on the list. Webhook failures look like a payment problem to the finance team and like a quiet night to whoever is watching Security Events.

If you see this, do this first

The first move in each case should be small and reversible. Write it down before the weekend so the person on shift doesn't have to invent it at 3 a.m.

You seeDo this firstAvoid
Real shoppers challenged on one pageFind the rule in Security Events and add an exception for that path or parameter onlySwitching off a managed ruleset or bot setting for the whole zone
A sudden spike to search, sign-in or a promo fieldTighten the rate limit on that route, or add a challenge for that route onlyTurning on Under Attack Mode for every visitor
Origin errors rising with no attack in Security EventsTell the application team, check recent releases, and raise caching on static and sale pages if it is safeBlocking traffic to "reduce load" when the visitors are customers
Cache hit ratio falling on a sale pageCheck for a new query string or cookie on the campaign links and adjust the cache ruleCaching pages that show carts, prices for signed-in customers or account details
Payment confirmations stoppingCheck Security Events for the provider's webhook path and add or fix its exceptionWaiting for the provider to raise it
Stock on a limited item selling out in secondsLook for automation on add-to-cart and challenge it on that product onlyChallenging every product page

If a real attack takes the site down, scoping matters more than ever. Our post on Under Attack Mode shows how to turn it on for one path instead of the whole zone, and what it breaks when you don't.

The handover note

Every shift ends with a short note in the place the next shift will look. Five lines are enough:

  1. State of the four signals at the end of the shift, against the levels you agreed.

  2. Changes made, each with the time, the reason, who approved it and how to undo it.

  3. Anything still being watched, such as a rate limit tightened an hour ago that may need relaxing.

  4. What the business told you, such as an email going out at 9 a.m. or a product selling out.

  5. Who to call if the next shift needs the person who made a change.

The note is also your record for the review. Changes made in a hurry and never written down are the ones that are still blocking someone in March.

The Tuesday review

On Tuesday, go through every change since Thursday. For each one, decide whether it stays as it is, stays with a better scope, or goes. Then write three short lists for next year: what worked, what you had to invent during the weekend, and which signals you wished you had watched from the start.

If a rule was tuned so tightly for Cyber Monday that it would trouble ordinary traffic, loosen it now. December brings its own peaks, and the January sales start soon after.

Who watches the weekend

The runbook works with any team, as long as every shift has a name against it. If yours doesn't have enough people for five shifts, that is the gap a managed service fills.

Vigilbase is a Preferred Cloudflare Partner, ISO 27001 and SOC 2 Type 2 compliant. On our Priority and Critical service levels, our follow-the-sun teams in Kenya, South Africa, the UAE and Portugal cover the whole weekend, with the response times on our SLA page. For a single shop, Vigilbase Shield is a monthly plan with managed WAF rules, DDoS protection and Super Bot Fight Mode.

What should we watch on Cloudflare during Black Friday?

Four things: the challenge and block rate on checkout and sign-in, origin errors, the cache hit ratio on sale pages, and whether payment confirmations are still arriving. Agree beforehand what level of each means someone has to act.

Is it safe to change Cloudflare rules in the middle of Black Friday?

Small, scoped changes are safer than leaving a rule that blocks shoppers. Add an exception for one path, tighten one rate limit, or challenge one route, and record each change with how to undo it.

How many people does a Black Friday weekend need?

At least one named person per shift from Thursday evening to Monday night, plus someone who can approve changes. Five shifts is a common split.

What should we do on the Tuesday after Cyber Monday?

Review every change made over the weekend, keep or remove each one, and write down what you had to work out during the weekend so next year's runbook already has it.

Share this article

Tags

CloudflareBlack FridayCyber MondayRetailIncident response

Get a free Cloudflare Checkup

An A–F grade for your Cloudflare account in about 2 minutes. Read-only: sign in with Cloudflare, and access is revoked when the scan finishes. The grade and free findings cost nothing; the full report is an optional upgrade.

Run the free Checkup
Ilyas Esmail

Ilyas Esmail

Founder & CEO

Ilyas founded Vigilbase to simplify how businesses get their cybersecurity work done. On this blog, Ilyas writes about cybersecurity, Cloudflare and the work of keeping businesses secure.

About Vigilbase

Vigilbase is the cybersecurity operating system. Vigilbase OS connects the security tools an organisation already pays for, keeps their logs and events in one auditable place, and has the Vigil agent investigate, make authorised fixes and verify the result. As a Preferred Cloudflare Partner, Vigilbase also sells Cloudflare Enterprise and operates it as Managed Cloudflare. Vigilbase is ISO 27001 and SOC 2 Type 2 compliant.

Stay ahead of threats

Get the latest cybersecurity insights and best practices delivered to your inbox.