The United States votes on Tuesday 3 November 2026. If your product touches American users, that is the worst week of the year to be shipping changes — and the cheapest week to protect with a freeze you decide on now.
Who this is for
- Anyone running a US-facing app, payments flow, media property or SaaS product where a mid-week outage would be noticed.
- Heads of engineering and delivery leads who own the deploy calendar.
- Ops and on-call teams who will carry the pager that week.
- Founders selling into US customers who cannot afford an avoidable incident in front of them.
What’s happening
Election week in the US is a traffic and attention spike wrapped around a fixed date. Newsrooms, betting and prediction markets, ad platforms, comment systems and anything downstream of them see load they do not see the rest of the year. Even if your product has nothing to do with politics, your third parties, your CDN, your payment processor and your cloud region are all sitting in the same weather. It is also a favourite window for opportunistic abuse — credential stuffing, scraping, DDoS — because everyone’s attention is elsewhere.
Why it bites
Most self-inflicted outages arrive on the back of a deploy. Put a routine release out on 3 November, watch it interact with a load pattern you have never tested against, and you are now debugging a change and a traffic spike at the same time — with half your responders distracted by the news. The failure is rarely the election itself. It is the ordinary Tuesday change you would have shipped anyway, landing on the one day you had no slack to absorb it.
The one thing to do before 3 November
Declare a change freeze on all US-facing systems for the window around election day — put it on the calendar now, in writing, with a named owner and a documented break-glass exception for genuine security fixes. Pick the dates, tell delivery and on-call, and pause non-essential deploys, migrations and config changes for that window. One decision, made in July, removes a whole category of November incident. Make the freeze the default and require a sign-off to break it, not the other way round.
If you want the freeze backed by monitoring you can actually trust during the week, my resilience and continuity work is where that lives — freeze policy, on-call readiness and the observability to know if something moves.
Engagements are fixed-scope and fixed-fee, quoted before any work starts — no day-rate meter running.
If your own team is stretched too thin to hold a proper freeze and staff the week, that is exactly the kind of short, bounded delivery and ops cover my sister brand provides — extra hands to run the freeze, watch the dashboards and clear the backlog the day it lifts. Decide the freeze this week; 3 November will not move for you.
Free interactive tool
Website compliance checklist
What your site has to do, based on what it actually does
Answer as much or as little as you like — the list builds as you go. Nothing is stored against your name and no email is required.
Everything that applies
Ordered by what to do first: legal requirements you can close quickly, then larger pieces of work, then what is expected rather than required. Not exhaustive, and not a legal audit.
Dated PDF, yours to keep or circulate.
Most technology problems are not technology problems. They are control problems.
The systems exist. The investment has been made. The question is whether leadership can understand, direct, evidence, and sustain what those systems produce. Find out where control exists — and where it only appears to.