Black Friday Hosting: The Capacity Plan That Starts in September

Black Friday falls on 27 November 2026, and Cyber Monday on 30 November. From the day this is published that is 66 days — which sounds like plenty and is not, because almost every decision that matters has a lead time attached to it.

Black Friday hosting goes wrong in November for reasons that were fixable in September. Hardware has delivery estimates. Platform upgrades need a staging environment and a rehearsal. DNS changes need their TTL lowered before you need them lowered. None of that can be compressed into the last week, which is exactly when most stores start looking.

This is a dated plan, not a checklist of good intentions.

First, check what your platform actually requires

More stores are broken by an unsupported PHP version than by traffic. Before any capacity work, confirm the stack you are on is one your platform supports — and read the compatibility chart, not the headline sentence, because they disagree more often than you would like.

Two traps live in that table.

PrestaShop. The documentation recommends PHP 8.5, but that recommendation is for 9.1. PrestaShop 9.0 stops at PHP 8.4. Upgrading PHP to 8.5 on a 9.0 store because the headline told you to will take the store down, in November, for a reason you introduced.

OpenCart. The official requirements page asks for PHP 8.0 or later and also lists magic_quotes_gpc and register_globals among the settings to enable. Both directives were removed from PHP in version 5.4. The page is stale; the PHP 8.0 minimum and the extension list (Curl, GD, Iconv, Mbstring, OpenSSL, ZipArchive, Zlib) are the parts to act on.

Magento also needs OpenSearch 3 and Valkey or Redis alongside the database. Those are separate services with their own memory footprints, and "we upgraded PHP" is not the same as "we upgraded the stack".

Size the peak hour, not the month

Peak-season capacity is an hour-shaped problem. A store that handles 100,000 pageviews across a normal month may see a fifth of its Black Friday volume inside sixty minutes, and the server does not get to average that out.

Take last year's busiest hour from your analytics — not your busiest day — and multiply by whatever growth you are planning for. That is the number to test against. If you have no last year, test against three times your current busiest hour and find out where it breaks.

The thing that breaks is almost never bandwidth. Checkout is a write-heavy path: cart updates, stock decrements, order inserts, payment callbacks. Those are database transactions that cannot be cached, and they queue behind each other. Page caching makes the catalogue fast and does nothing at all for the ten seconds that actually earn the money. Load-test the checkout, with payment in sandbox, or you have not load-tested anything.

The eight-week plan

The 16 October line is the one with a hard edge. AMD EPYC builds at NexonHost carry a two-week estimated delivery as of September 2026, while the Intel Xeon builds provision automatically in minutes. If you want EPYC hardware live and rehearsed before the freeze, mid-October is the decision point, not mid-November.

Scale up, or scale out, or neither

Three honest options, in order of how often they are the right one:

1. Fix the code. An N+1 query in the cart is cheaper to fix than to host around. Profile first.
2. Move to bigger metal. A single larger machine keeps the architecture unchanged, which matters when there is no time to test a new one. NexonHost dedicated servers run from a 20-core Intel Xeon build at €129/month up to a 256-core dual EPYC 9754 with 1 TB of memory, all on unmetered 1 Gbps ports as standard.
3. Split the tiers. Database on its own box, application on another. This is the right long-term answer and the wrong thing to attempt in November.

If the constraint turns out to be egress rather than compute — heavy media, big downloads, a lot of uncached traffic — the port is the fix, and 10 Gbps dedicated servers are configurable on every build. Work out which constraint you actually have first; the method is in How Much Bandwidth Does a Server Need?

Platform-specific pages worth reading

The per-platform requirements and tuning notes live on the hosting pages for each: Magento hosting, PrestaShop hosting, OpenCart hosting and WordPress hosting. The deeper requirement write-ups are in Magento 2 hosting requirements, PrestaShop hosting server requirements and OpenCart hosting requirements.

What hosting cannot fix

Be clear about the boundary, because the last fortnight is a bad time to discover it.

Hosting does not fix a payment gateway that rate-limits you, a third-party script that blocks rendering, a stock system that oversells, or a checkout with four required fields too many. It does not fix an email provider that throttles your order confirmations. And it does not fix an attack — though it should not make one worse: network-edge DDoS mitigation is included on every NexonHost dedicated server, and application-layer filtering is a separate product.

The most valuable thing you will do before November is the 9 October load test, because it converts opinions into a list. Everything after that is just working the list in date order.

Prices and delivery estimates are as of September 2026 — check the product pages for current figures.

Sources

• Adobe Commerce system requirements, Adobe Experience League. Retrieved 21 September 2026.
• System requirements for PrestaShop 9, PrestaShop Developer Documentation. Retrieved 21 September 2026.
• OpenCart system requirements, OpenCart Documentation. Retrieved 21 September 2026.
• WordPress requirements, WordPress.org. Retrieved 21 September 2026.
• NexonHost dedicated server configurations, pricing and delivery estimates. Retrieved 21 September 2026.