
Keeping Thinkbox’s site responsive through a 7,000% traffic spike
Thinkbox’s national TV campaign sent viewers straight to its website to fill in forms, with demand modelled at up to 25,000 requests a minute. Box UK’s systems engineers put a content delivery network and cloud queueing in front of the site, and it stayed responsive through traffic up to 7,000% above normal.
7K%
peak traffic increase over normal levels
25K
form requests a minute, modelled at peak
100%
of home page hits served from the CDN
70%
of all site hits served from the CDN
In short
Thinkbox, the marketing body for UK commercial TV, ran a national campaign designed to send viewers from prime-time TV to its website. This time they would be filling in forms, in short and intense bursts, and the site had to keep up.
- Demand modelled at up to 25,000 form requests in a single minute
- Cloudflare’s CDN cached the site, so most page requests never reached Thinkbox’s servers
- Amazon SQS queued form submissions, and Amazon SES sent automatic replies
- The site stayed responsive through traffic up to 7,000% above normal
- The CDN worked so well that Thinkbox kept it in place permanently
Customer background
Thinkbox is the marketing body for commercial TV in the UK, showing advertisers what TV advertising can do. So when it ran a national campaign of its own, it expected big results.
The campaign included Shazam-enabled commercials in prime-time shows such as Coronation Street and The X Factor, along with ITV’s dual-screen X Factor app.
The challenge
Thinkbox’s site had coped well with large rises in TV-driven traffic before. This campaign was different: the adverts drove people to fill in forms to download content and enter competitions.
Form submissions need the server to do work, and they were expected to arrive in short, intense bursts. Modelling suggested up to 25,000 form requests in a single minute. The site needed a way to handle those peaks while still giving every visitor a fast, smooth experience.
Thinkbox brought in Box UK’s Systems Engineering team to make sure its infrastructure could cope.
Our approach
Box UK’s approach was to move as much of the load as possible off Thinkbox’s servers. Page requests could be served from cached copies on a content delivery network. Form submissions couldn’t be cached, so they needed to be accepted straight away and processed at a pace the servers could manage.
Cloud services made both possible.
What we built
Box UK’s systems engineers set up the Cloudflare content delivery network (CDN) and configured it to cache the site at regular intervals. Requests for pages could then be served from the CDN instead of Thinkbox’s own servers, which meant faster load times and less pressure on the infrastructure, without affecting the content visitors received.
For the forms, Amazon Simple Queue Service (SQS) held submissions in a cloud-based queue until the server could process them, and Amazon Simple Email Service (SES) sent automatic responses to newsletter subscribers. Both took load away from the servers without visitors noticing any of the work going on behind the scenes.
The outcome
During the TV adverts and in-app content, the Thinkbox site more than met its performance requirements. The CDN served 100% of home page hits and 70% of all site hits, thousands of requests were handled without issue, and the site stayed responsive as traffic rose by up to 7,000% over normal levels.
The CDN proved so valuable that Thinkbox decided to keep it in place permanently, so its content would still be delivered if anything unexpected happened to its servers.
Frequently asked questions
Model the expected load, then move as much of it as possible away from your servers. For Thinkbox, a CDN served cached pages and a cloud queue absorbed form submissions.
It serves cached copies of your pages from its own network, so most visitors never reach your servers. Thinkbox’s CDN served 70% of all site hits during its campaign.
Queue them. Thinkbox used Amazon SQS to hold submissions in the cloud until the server could process them, so the site stayed responsive.
Model it from what the campaign asks people to do, not just how many will see it. For Thinkbox, modelling suggested up to 25,000 form requests a minute.
Often, yes. Thinkbox kept its CDN permanently, so content would still be delivered if anything went wrong with its servers.
In short
If a campaign, broadcast, product launch or news moment could send a sudden rush of people to your site, the time to plan for it is before it happens. The fix is usually less about bigger servers and more about keeping the load away from them.
If you have a spike coming, send us a few lines about the site and what you expect. We’ll tell you where we think it would break.
Talk to one of our digital experts

Tom Houdmont
Chief Technology Officer
Do you have a great idea for a project you need support with?
Tom is CTO at Box UK, with 12 years’ experience helping clients deliver ambitious digital products. His background spans Solution Architecture, Front End Development and AI adoption, with particular expertise in high-traffic websites that perform reliably at scale and in embedding AI into delivery practice.
Or call us on 020 7439 1900
Related case studies
Have a project you’d like to discuss?
Give us a call on 020 7439 1900 or fill in the form and we will get back to you.


