loading
loading
Every four years, the World Cup becomes the largest planned stress test of our infrastructure. This year it also set an all-time record! There are a few moments throughout the year, like New Years Eve, that really let us see the collective impact of everything we’ve built — but none are bigger than the quadrennial World Cup tournament. The 2026 World Cup broke records across messaging, video, recommendations, and networking at the same time. Some highlights: - WhatsApp: More than 30 million messages per second during the July 19 final (Argentina vs. Spain), 1.23x the peak of New Year’s Eve 2026 and an all-time platform record. The previous record had already fallen 12 days earlier, during the Round of 16 match between Argentina and Egypt, at 29 million messages per second. - Messenger, Threads, and Instagram Direct: 49 million messages per minute at peak. - Instagram: Recommendation system traffic up to 80% higher week-over-week. Final-squad players collectively added +213.6 million activated followers — a 6.6% increase — with combined followings surging from 3.26 billion to 3.47 billion. - Live video: Watch time spiked +90% on Instagram and +242% on Facebook, versus the July baseline. - Threads: 1.5 billion impressions on tournament-tagged posts, reaching about 15 million people daily and peaking at 25 million on July 6. - Facebook: 80 million posts mentioning the World Cup. Traffic Followed the Breaks, Not the Ball Every World Cup match caused surges in traffic. During the final, for example, traffic surged +46% in about four minutes at the end of regular time, and +57% in about 15 minutes at the final whistle. But by lining game events up against global egress traffic we discovered a striking pattern – surges in sharing were primarily happening during breaks (hydration breaks, halftime, extra time, the final whistle, the awards ceremony). The end-of-regulation whistle produced the single biggest peak of the tournament. It wasn’t the gameplay that moved our charts. It was the conversations after it. The world came to Meta to watch the game and to share what it made them feel. Every capacity decision below follows from that one pattern. Layered Systems, No Manual Intervention Those spikes were absorbed by systems built for exactly this. Taiji balanced load across datacenters, Katran and Proxygen handled L4/L7 traffic distribution, our global load balancing system routed users to the best-positioned edge, and AutoScaling provisioned capacity on demand. Region-Specific Capacity Months before kickoff, Meta’s edge teams analyzed network capacity and worked closely with ISP partners so that upgrades landed where they would most improve quality of experience for end users. That targeted pre-build is now permanent capacity that will keep serving demand long after the tournament. Instagram: Preparing for 39 Consecutive Days of Surges For Instagram, the tournament meant 39 straight days of traffic spikes as billions of fans checked scores, posted Stories, and flooded Feed during breaks. Machine learning inference, Feed serving, Stories, Explore, and data infrastructure all had to absorb it without degrading the experience. During the final, halftime Instagram Feed traffic rose 76% above the previous day in the minute the match ended, and stayed about 21% above for the following two hours. Our approach rested on four things, deployed incrementally as the tournament moved from group stage to final. - Capacity buffers: Our products went into the tournament with sufficient capacity, which meant real buffers were available to allocate. We pre-provisioned significant additional capacity across all serving tiers so that spikes never had to wait on autoscaling to catch up. These dedicated buffers were our single most effective lever of the tournament. - Country-level graceful degradation: For high-risk matches, we shed non-critical background load in the top-traffic nations (Brazil, Argentina, India, Indonesia, Spain) to protect core functionality. - Cascade prevention: So spikes at the serving layer couldn’t propagate into downstream data systems. - Early warning signals These alerted us before we approached capacity thresholds, rather than after. All of this, including the phased deployment timeline and the degradation activation criteria, is now a reusable runbook for future large-scale events like the 2028 Olympics. WhatsApp: 8.4 Billion Messages in Five Minutes Goals and the final whistle drove WhatsApp spikes lasting four to five minutes at a time. In its single highest-traffic five-minute window, WhatsApp delivered nearly 8.4 billion messages without interruption. That came from months of preparation. More than 100 internal services were load-tested and resized ahead of the tournament, then retested, revalidated, and resized as the bracket narrowed and demand climbed. Two things we’d normally do, we didn’t. We didn’t shift load between regions. For past high-traffic events, our default has been to spread demand across multiple regions, letting capacity in quieter parts of the world absorb the spike. That works when peaks land hours apart — a global New Year’s Eve, for example. This event was different. Every region peaked in the same instant, so there was no idle capacity to borrow. Instead of deriving regional demand from a global multiplier, we forecast each region’s peak on its own terms. We didn’t freeze. The other standard playbook move for a major event is to pause continuous deployment and hold off on riskier operations like disaster recovery exercises. This time we skipped the freeze entirely, on the strength of years of reliability enhancement. Teams shipped on their normal cadence throughout the entire event window, including during the peak moment itself. We Stay Ready Year-Round Enabling connection in moments like this doesn’t just happen. Powering every message sent, every follower, and every Reel shared in real time across 48 teams and 104 matches is a story of infrastructure and product working as one. Capacity planning, load testing, traffic management, and rapid incident response come together across these teams so that billions of people can connect in the moments that matter most — like an entire continent celebrating a last-minute goal at the same second.
document fetched 2026-10-24 09:56 · canonical https://engineering.fb.com/2026/10/15/production-engineering/2026-world-cup-record-traffic-reliability-at-scale