Millions of gamers log onto Fortnite every day expecting a seamless drop onto the Battle Royale island. But yesterday, players across Western Europe were met with a frustrating spinning wheel. Matchmaking went down. The culprit wasn’t a sudden spike in player numbers or a botched weapon balance update. Instead, an ambitious backend upgrade collided head-on with real-world network traffic.
Epic Games tried to transition its European player base to Amazon Web Services’ (AWS) new localized Edge servers. It didn’t go quite as planned.
The Matchmaking Meltdown
The trouble started in the early afternoon, right around 2:30 PM UTC. Reports of matchmaking failures suddenly spiked on DownDetector. Gamers from London to Munich found themselves stuck on loading screens. The dreaded “Error Code 9.1” popped up on thousands of monitors, cutting players off from the game’s servers.
Epic Games quickly realized they had a problem. On their official Fortnite Status social media account, the developer confirmed they were investigating “issues with matchmaking in the European region.” While they didn’t mention AWS in their initial public warning, network monitors and backend developers quickly pointed to a major routing shift in the EU-West region.
Why Make the Shift to the Edge?
Epic has been quietly working to bring server response times down to the absolute minimum. For competitive shooters, every single millisecond matters. High ping can mean the difference between landing a game-winning shot or getting sent back to the lobby. That is where AWS’s new localized Edge servers come in.
These specialized nodes are designed to process data closer to the actual players. They bypass the traditional, centralized data centers that often bottleneck traffic during peak hours. By shifting matchmaking and core gameplay instances to these Edge locations in Western Europe, Epic hoped to deliver virtually lag-free gaming. It was a great idea on paper.
A Complex Balancing Act
Moving millions of concurrent connections to a brand-new architecture is incredibly complex. Network engineers explain that when the switch was flipped, the routing tables couldn’t handle the sudden, massive influx of matchmaking requests. Instead of distributing the load evenly across the new Western European Edge nodes, the system choked.
The servers essentially locked up, leaving players stranded in infinite queues. Competitive players were especially hit hard, with many locked out of scheduled scrims and practice sessions. Many took to social media to voice their frustration, sharing screenshots of matchmaking timers ticking past the thirty-minute mark.
Scrambling for a Fix
Epic’s engineering team scrambled to resolve the issue. By 5:00 PM UTC, the company began rolling back some of the traffic to its legacy AWS server configurations. It was a temporary band-aid to get people back into the game while they diagnosed the core issue with the Edge servers. Slowly, matchmaking queues began to shrink. By dinner time in Europe, the game was fully functional again, though some players still reported slightly higher ping times than usual as traffic routed through older, more distant servers.
What Happens Next?
Despite the hiccup, Epic isn’t giving up on its Edge computing dreams. Shifting to localized servers is the logical next step for massive live-service games. It reduces infrastructure costs and promises a much better player experience once the bugs are worked out. For now, the developer says it is closely monitoring performance. They plan to phase in the new AWS Edge servers more gradually next time. They want to avoid another widespread blackout. European players can expect more tests in the coming weeks, hopefully with fewer crashes.
