Meta's biggest World Cup spikes came at whistles and breaks, and it never froze deploys

The biggest traffic spikes Meta's apps saw during the 2026 World Cup came when play stopped, not during the action, according to an October 15 engineering post: the whistle at the end of regular time in the final produced the single largest peak of the tournament. The same post says WhatsApp handled more than 30 million messages per second in the July 19 final without freezing code deployments, a step many companies take before big events.

Meta announced the headline records in July. The new post is its engineers' account of where the load actually came from and how they handled it.

The conversation after the moment

Traffic rose around every match, but the sharp sharing spikes clustered in pauses: halftime, cooling breaks, extra time, the last whistle and the trophy ceremony. In the final between Argentina and Spain, traffic climbed 46% in roughly four minutes as regular time ran out, and 57% over roughly 15 minutes once the match was over.

Instagram Feed traffic in the minute the final ended was 76% higher than a day earlier, and it remained around 21% up for two hours afterwards. The engineers' own summary: "It wasn't the gameplay that moved our charts. It was the conversations after it."

On WhatsApp, goals and the final whistle each set off spikes lasting four to five minutes. The final's peak was 1.23 times WhatsApp's New Year's Eve 2026 peak and beat a record of 29 million messages per second set 12 days earlier during Argentina's round of 16 match against Egypt. In one five-minute window, the service delivered nearly 8.4 billion messages.

Two rules WhatsApp broke on purpose

The usual way to absorb a surge is to push demand toward regions that are quiet at that hour. That did not work here, the engineers write, because every region peaked at the same moment. Instead they forecast each region's peak separately rather than applying one global multiplier, and load-tested and resized more than 100 internal services before the tournament, then again as demand grew.

The second departure was keeping the normal release schedule. Teams shipped as usual through the whole event, including during the peak, and kept running riskier operations such as disaster recovery exercises.

Instagram's 39 days

Instagram dealt with 39 consecutive days of surges. Its main lever, by the team's account, was capacity provisioned in advance across every serving tier so that spikes never waited on autoscaling. For high-risk matches it also prepared to shed non-critical background work in the five countries with the most traffic: Brazil, Argentina, India, Indonesia and Spain.

The post does not say whether that fallback was ever switched on, and it reports no outages. Meta says the plan is now a reusable runbook, with the 2028 Olympics named as a future use.