Seasonal
The 2026 holiday code freeze calendar.
Black Friday is 27 November. Cyber Monday is 30 November. Here’s the window most teams actually run, and the January dates that catch people out.
Every date that matters, and why
| Date | Day | What | Typical band | Why it matters | Region |
|---|---|---|---|---|---|
| 11 Nov | Wed | Singles’ Day | Normal | First real traffic spike of the season if you sell into APAC. Worth a load test, not a freeze. | APAC |
| 16 Nov | Mon | Peak season starts | Heightened review | The Monday most retail engineering orgs move to heightened review: bigger changes get a second pair of eyes, deploys stay small. | US · EU |
| 25 Nov | Wed | Freeze starts (typical) | Frozen | The day before Thanksgiving. Teams that freeze for Black Friday almost always start here, not on the Friday — you want a full business day of quiet before the traffic. | US |
| 26 Nov | Thu | Thanksgiving | Frozen | Skeleton on-call in the US. If you need a hotfix today, you need an exception process that takes minutes. | US |
| 27 Nov | Fri | Black Friday | Frozen | The day the freeze exists for. | US · EU |
| 30 Nov | Mon | Cyber Monday | Frozen | Usually the higher of the two for digital-only businesses. Freezing through Black Friday and thawing on the Sunday is the classic mistake. | US · EU |
| 1 Dec | Tue | Freeze lifts (typical) | Heightened review | Thaw on the Tuesday, with people at desks, and stagger the queue rather than merging everything at 09:00. | US · EU |
| 14 Dec | Mon | Year-end close begins | Heightened review | Finance systems start their close. Anything touching billing, invoicing, or ledgers gets frozen earlier and thawed later than the rest of your estate. | Global |
| 18 Dec | Fri | Holiday freeze starts (typical) | Frozen | The last Friday with a full team. Most orgs freeze from here through the first week of January. | US · EU |
| 24–26 Dec | Thu–Sat | Christmas Eve, Christmas, Boxing Day | Frozen | Public holidays across the US, UK, and most of the EU. On-call is genuinely thin — this is a staffing constraint wearing an engineering costume. | US · EU |
| 31 Dec – 1 Jan | Thu–Fri | New Year | Frozen | Date-rollover bugs live here: annual counters, fiscal-year logic, certificate expiry, cron expressions with a year in them. | Global |
| 4 Jan | Mon | Everyone is “back” | Heightened review | The day teams thaw. Half the team is still away. Thawing on the 1st is the single most common freeze-calendar error. | Global |
| 6 Jan | Wed | Epiphany | Heightened review | A public holiday in Spain, Italy, Austria, Sweden, and parts of Germany. If your on-call rotation is EU-wide, this is a real gap. | EU |
| 11 Jan | Mon | Full thaw (typical) | Normal | The first Monday everybody is actually back and the January backlog has been drained deliberately rather than all at once. | Global |
| 18 Jan | Mon | Martin Luther King Jr. Day | Normal | US holiday. Worth knowing if your thaw plan assumed four full working weeks in January. | US |
Dates are fixed calendar facts; the bands are what teams commonly do, not advice. Your risk profile decides your windows.
Three windows teams actually run
Copy one of these, then change the dates that don’t fit. Graduated bands — heightened review before frozen — are what Meta and Amazon both do, and they cause far less resentment than jumping straight to blocked.
E-commerce
3 windows- Heightened review
Mon 16 Nov → Tue 24 Nov
- Frozen
Wed 25 Nov → Tue 1 Dec
- Frozen
Fri 18 Dec → Mon 4 Jan
Two red windows, because Black Friday and the holidays are different risks with different staffing.
Fintech year-end
3 windows- Heightened review
Mon 14 Dec → Wed 23 Dec
- Frozen
Thu 24 Dec → Mon 4 Jan
- Heightened review
Tue 5 Jan → Fri 8 Jan
Ledger and billing services freeze wider than everything else, and thaw last.
SaaS conservative
1 windows- Frozen
Fri 18 Dec → Mon 4 Jan
One window, scoped to production-facing services. Docs sites and internal tools keep shipping.
Set it up in Fwozen
Import a preset as a real schedule with a timezone attached, then edit it. Fwozen shows the next five occurrences in both the schedule’s timezone and yours before you save.
Scheduled and recurring freezes are in the free tier. A downloadable .ics is on the list and not built yet — we would rather ship the import than fake the export.
What most teams get wrong
- Mistake 1
Freezing too late
Starting the freeze on Black Friday morning leaves no time to discover what the freeze itself broke. Start two days early.
- Mistake 2
No exception path, so people merge anyway
If the only way through is a Slack argument with whoever is awake, the freeze becomes advisory in practice and you have a policy that manufactures lies.
- Mistake 3
Forgetting the deploy pipeline
A merge freeze that lets a scheduled deploy run is half a control. Gate the pipeline on the same freeze state.
- Mistake 4
No timezone discipline on a global team
“Freeze on the 24th” means eleven different instants. Attach a timezone to the window and show people their local equivalent.
- Mistake 5
Thawing on 1 January
Nobody is back until the 4th, and half the team not until the 11th. Thaw when there are people at desks to watch it.
A copy-pasteable freeze policy document — scope, banding, approvers, exception process, audit requirements — is being written and will land at /code-freeze-policy-template.
Holiday freeze questions
When should a holiday code freeze start?
For Black Friday, the Wednesday before Thanksgiving — 25 November 2026 — so you get a full quiet business day before the traffic. For the December holidays, the last Friday with a full team, which in 2026 is 18 December. Starting on the day of the event is too late: you want time to notice what the freeze broke.
How long should it last?
Long enough to cover the staffing gap and no longer. Most teams run six to twelve business days in December. The cost of a freeze grows non-linearly: three weeks of queued changes is a thaw nobody can review properly.
What about hotfixes?
Decide the exception path before the freeze, and make it take minutes: who can approve, what reason is required, and how long the exception lasts. If the override is slow, people route around the freeze and you end up with a policy that produces lies instead of safety.
Does a freeze actually reduce incidents?
Honestly: not in the way most people assume. The research on deployment frequency points the other way, and the thaw concentrates risk into one day. What a freeze buys you is lower variance on a date where the downside is enormous, and a smaller on-call load when half the team is away. Those are real reasons. “Freezes reduce bugs” is not one, and we wrote a long argument against our own product about it.
What are the exact 2026 dates?
Thanksgiving is Thursday 26 November 2026, Black Friday is Friday 27 November, Cyber Monday is Monday 30 November. Christmas Day is Friday 25 December and New Year’s Day is Friday 1 January 2027 — both on a Friday, which makes the surrounding weeks unusually thin.