Nothing’s worse than firing up Call of Duty for a ranked session, only to get stuck on a “Waiting For Relay” screen. The matchmaking crawls, the timer ticks endlessly, and you’re left wondering if your internet died or if the servers just ghosted you. This error has haunted players across PC, PlayStation, Xbox, and even mobile versions for years, and it’s still showing up in 2026. But here’s the good news: most of the time, it’s fixable without contacting support. Whether you’re grinding multiplayer, tackling Spec Ops missions, or hunting for damascus camos, connection issues can derail your entire gaming session. This guide breaks down what “Waiting For Relay” actually means, why it happens, and exactly how to get back in the fight, fast.
Key Takeaways
- “Waiting For Relay” in Call of Duty means the game can’t complete the handshake between your device and the game’s servers, even when your internet connection is working fine.
- Most relay errors are fixable in under five minutes by restarting your game, switching to wired Ethernet, or clearing your game cache without contacting support.
- Common causes include server connection problems during peak hours, network configuration issues like firewall blocks, WiFi interference, and corrupted game files from failed updates.
- Advanced troubleshooting steps like adjusting firewall port settings, updating game and system software, resetting network settings, and disabling IPv6 resolve persistent relay issues.
- If relay errors persist only in Call of Duty after completing all troubleshooting steps, the problem likely stems from your account’s authentication or regional assignment and requires Activision support.
- Check Activision’s server status before troubleshooting, as temporary maintenance or season launch congestion can cause relay errors on Activision’s end, not yours.
What Does ‘Waiting For Relay’ Mean in Call of Duty?
The “Waiting For Relay” message is Call of Duty’s way of saying it can’t complete the handshake between your console or PC and the game’s servers. Think of a relay as a middleman, your device needs to reach a relay server that then connects you to the actual game server. When that relay fails to respond or can’t establish a path, you get stuck in this limbo state.
It’s different from a simple “Connection Lost” error because your connection to the internet might be perfectly fine. The problem exists somewhere between your device and Call of Duty’s infrastructure. You’re connected to the internet, but the game can’t route itself through the correct server path to get you into a match. The error typically appears during matchmaking, right when the game should be placing you with other players. It can last anywhere from a few seconds to several minutes, and sometimes it resolves on its own. Other times, it doesn’t, and that’s where troubleshooting comes in.
Understanding this distinction matters because it determines which fixes actually work. If it’s a relay issue, restarting your router might help, but it’s not a guarantee. The problem could also be on Activision’s end, your ISP’s routing, or somewhere in between.
Common Causes of the Waiting For Relay Error
The “Waiting For Relay” error doesn’t appear randomly, something’s breaking the connection chain. Here are the most common culprits:
Server Connection Problems
Call of Duty’s server infrastructure isn’t a single monolith. It’s distributed across multiple regions and data centers. When Activision deploys patches, performs maintenance, or experiences unexpected downtime, relay servers can become temporarily unreachable. This was particularly common during major season launches when servers get hammered by millions of players logging in at once.
Geographic routing issues also play a role. Your ISP might normally route you to a relay server in Dallas, but during peak hours or outages, traffic gets redirected unpredictably. Sometimes the relay server you’re assigned is physically far from your location, creating latency spikes that cause timeouts. Bandwidth throttling on specific routes can also trigger relay failures, your packets arrive, but they’re delayed past the server’s response window.
Network Configuration Issues
Your home network setup matters more than you’d think. If your router isn’t forwarding packets correctly, or if you’re behind multiple layers of NAT (Network Address Translation), the relay server might struggle to send data back to you. Firewalls, both on your router and on your PC, can silently block the specific ports Call of Duty uses to communicate with relays.
WiFi is another silent killer. A 5GHz connection might show full bars, but interference from microwaves, cordless phones, or neighboring networks can cause packet loss. When 5-10% of your packets are disappearing in transit, the relay handshake fails before completing. Wired connections eliminate this variable entirely, which is why competitive players and streamers always hardwire their consoles and PCs.
DNS issues can also cause relay problems. If your ISP’s DNS is slow or unreliable, the initial domain lookup for the relay server might time out. You’re then assigned a different relay, which might not work with your current network configuration.
Game Client Conflicts
Corrupted game files create relay errors surprisingly often. If your Call of Duty installation is missing critical files or has corrupted data, the client can’t properly authenticate with relay servers. This happens most often after failed updates, hard shutdowns during patches, or drive errors.
Outdated game clients are another issue. Activision regularly updates the protocol and encryption methods used to communicate with servers. If you’re running a version that’s more than a patch or two behind, the relay server might reject your connection as incompatible. Similarly, running old system software (on console or PC) can prevent modern authentication from working.
Conflicting background applications cause problems too. Anti-cheat systems can interfere with network packets, VPNs can confuse the relay routing, and even Discord’s overlay can occasionally trigger relay errors by intercepting network calls.
Quick Fixes to Try First
Before you jump into deep troubleshooting, try these simple steps. They resolve the problem in roughly 70% of cases and take less than five minutes.
Restart Your Game and Console
This sounds basic, but it works. Close Call of Duty completely, not just backing out to the home menu, actually fully close the application. On PlayStation, highlight the game and press the options button, then select “Close”. On Xbox, press the button on your controller and choose “Quit”. On PC, exit through the launcher completely.
Wait 30 seconds, then restart. This clears your client’s memory, refreshes your connection state, and gives the relay server time to forget about your previous failed connection attempt. If you’re on console, you can power down entirely for 30 seconds while you’re at it, this also refreshes your console’s network stack.
Check Your Internet Connection
Run a speed test using Speedtest.net or your ISP’s built-in test. Call of Duty needs:
- Download: 5+ Mbps (10+ for smooth 60fps multiplayer)
- Upload: 1+ Mbps
- Ping: Under 100ms (under 60ms for competitive play)
- Jitter: Under 20ms
If your speeds are significantly below this, that’s your issue, not necessarily a relay problem, but a bandwidth or latency problem that manifests as relay timeout. Check if other devices are hogging bandwidth. Streaming services, downloads, or other games can easily consume the bandwidth Call of Duty needs.
If you’re on WiFi, switch to wired Ethernet. Even if your WiFi shows strong signal, wired connections eliminate interference and provide more stable latency. This single change fixes relay errors for roughly 30% of affected players.
Verify Server Status
Before assuming it’s your connection, confirm the servers are actually online. Head to Activision’s support page or check Downdetector for Call of Duty server reports. If thousands of players are reporting connection issues simultaneously, the problem is on Activision’s end, not yours. In that case, you’re waiting for them to fix it, not troubleshooting your setup.
Check if specific regions or platforms are affected. Sometimes PlayStation servers are having relay issues while Xbox is fine, or North American servers are down while EU servers work. If that’s the case, you’re unfortunately out of luck until Activision resolves it.
Advanced Troubleshooting Steps
If the quick fixes didn’t work, these deeper solutions address underlying configuration and file integrity issues.
Clear Your Game Cache
Your game stores cached data about servers, matchmaking results, and connection history. If this cache is corrupted, it can cause relay routing errors.
On PlayStation 5:
- Go to Settings > System > System Software > Clear Cache
- Select “Clear System Software Cache”
- Your PS5 will restart
- Restart Call of Duty
On Xbox Series X/S:
- Go to Settings > System > Storage
- Select “Clear Local Saved Games” (this won’t delete your cloud saves)
- Alternatively, perform a “factory reset” of the network settings (Settings > System > Network Settings > Advanced Settings > Alternate MAC Address > Clear)
On PC:
- Open your Call of Duty installation folder (usually C:Program Files (x86)Call of Duty Modern Warfare)
- Delete the “Cache” folder
- Restart Battle.net and the game
Cache clearing is safe and won’t affect your progress, everything is synced to Activision’s servers.
Adjust Firewall and Port Settings
Call of Duty communicates over specific ports. If your firewall is blocking these, relay connections fail.
On Windows:
- Go to Windows Defender Firewall > Allow an app through firewall
- Find Call of Duty in the list (or Battle.net launcher)
- Check both “Private” and “Public” boxes
- Alternatively, add these ports to your firewall’s whitelist:
- UDP: 3074, 3478-3479
- TCP: 3074
On your router:
Access your router’s admin panel (usually 192.168.1.1 or 192.168.0.1). Look for Port Forwarding or UPnP settings. Enable UPnP, it automatically handles port forwarding without manual configuration. If UPnP is already enabled, try disabling and re-enabling it.
If you’re using a VPN, disconnect it temporarily. VPNs can interfere with relay routing by changing your apparent location or encrypting traffic in ways the relay server doesn’t expect. Test Call of Duty without VPN, if it works, you’ve found your culprit.
Update Your Game and System Software
Outdated software is one of the most overlooked causes of relay errors. Call of Duty receives regular patches that include server communication fixes.
Check for game updates:
- PlayStation: Go to your library, highlight Call of Duty, press the options button, and check for updates
- Xbox: Your console automatically downloads updates, but you can manually check in Settings > System > Updates
- PC: Open Battle.net launcher and verify Call of Duty’s version. Updates install automatically but might require a client restart
Check system software:
- PlayStation: Settings > System > System Software > Update
- Xbox: Settings > System > Updates
- PC: Windows Update (Settings > Update & Security), plus any driver updates for your network adapter
Out-of-date drivers are particularly problematic on PC. Network adapter drivers change how your system communicates with relay servers. Update through Windows Update or your motherboard manufacturer’s website.
Reset Network Settings
If nothing else works, a full network reset might help. This is more aggressive but effective for stubborn relay issues.
On PlayStation:
- Settings > Network > Settings > Set Up Network Connection
- Choose your connection type (WiFi or Ethernet)
- Re-enter your WiFi password if needed
- Complete the setup wizard
On Xbox:
- Settings > General > Network Settings > Advanced Settings > Alternate MAC Address > Clear
- Restart your console
- Reconnect to your network
On PC:
Open Command Prompt as Administrator and run:
ipconfig /release
ipconfig /renew
This forces your computer to request a new IP address from your router, which can reset a stalled connection state.
Also restart your modem and router: Unplug your modem and router for 30 seconds, then plug them back in. This refreshes your ISP’s connection and clears any routing issues on your end. This is the nuclear option, use it after everything else fails.
Platform-Specific Solutions
While relay errors are universal, the fixes vary by platform. Platform-specific details matter because authentication and networking work differently on PC versus consoles.
PC Solutions
PC players have more control over their network stack, but also more opportunities for conflicts. Start with the basics: ensure Call of Duty is running through the Battle.net launcher (not bypassing it), and that your antivirus isn’t interfering.
Windows-specific steps:
-
Disable IPv6 temporarily: Some ISPs and networks have issues with IPv6 routing. Go to Settings > Network & Internet > Change Adapter Options. Right-click your active connection, select Properties, and uncheck “Internet Protocol Version 6 (TCP/IPv6)”. Test Call of Duty. If it works, IPv6 is your problem.
-
Check your DNS: Switch from your ISP’s default DNS to Google DNS (8.8.8.8 and 8.8.4.4) or Cloudflare DNS (1.1.1.1). Go to Settings > Network & Internet > Change Adapter Options > Right-click your connection > Properties > Internet Protocol Version 4 > Properties. Select “Use the following DNS server addresses” and enter the DNS manually.
-
Run the Battle.net Launcher repair: Click the Options button in Battle.net (gear icon), select “Repair”, then choose Call of Duty. This re-downloads any corrupted files without erasing your settings.
PC offers another advantage: you can use ethernet almost universally. If you’re on WiFi, switch to wired. That alone fixes relay errors for most PC players, and esports settings guides on sites like The Loadout consistently recommend wired connections for competitive reliability.
Console Solutions (PlayStation and Xbox)
Consoles have fewer variables than PC, but that means when something’s wrong, it’s often a fundamental network issue.
For both PlayStation and Xbox:
-
Forget and rejoin your WiFi network: Go to your network settings, select your WiFi, choose “Forget”, then reconnect and re-enter the password. This clears any stored connection misconfigurations.
-
Test your internet connection: Both consoles have a built-in network test. Run it to check your speeds and connection stability. If the test shows poor latency or packet loss, that’s your issue.
-
Change your DNS settings: Most consoles default to auto-configure DNS, but you can manually set it to Google (8.8.8.8) or Cloudflare (1.1.1.1).
PlayStation-specific:
If you’re using an external hard drive or SSD, the game might be running from there instead of internal storage. Call of Duty performs better from internal PS5 storage. Move the game to internal storage if possible, this also helps with loading times, which indirectly prevents timeout issues.
Xbox-specific:
Make sure you’re in the correct Xbox Live region. If your account is set to a region far from your actual location, relay servers might assign you to distant match servers, causing latency and connection issues. Go to Settings > System > Language & Location and confirm your location is correct.
On both consoles, if you’re playing on a guest account, make sure it has proper network permissions. Guest accounts sometimes have restricted access to certain network features. Switch to your primary account and test.
When to Contact Support
If you’ve worked through all of these steps and you’re still stuck on “Waiting For Relay,” it’s time to escalate to Activision support.
Before you contact them, document what you’ve tried:
- Screenshot your internet speed test results
- Note the exact error message and when it occurs
- List your platform, region, and account type
- Document the steps you’ve completed (cache clear, network reset, etc.)
Based on reports from Dexerto, which covers esports incidents extensively, Activision support typically addresses relay issues within 24-48 hours if it’s a server-side problem, and guides players through additional advanced troubleshooting if it’s client-side.
If relay errors are affecting competitive ranked play or tournaments, that’s a priority issue. Activision has emergency escalation for ranked season progression and esports-related problems. Contact support through the Activision website, not through social media, support tickets get tracked and resolved more reliably than tweets.
One more thing: if other games work fine but only Call of Duty has relay issues, that strongly suggests the problem is with your Call of Duty installation or account, not your network. In that case, support can check if your account has authentication issues or if your regional assignment needs adjustment.
The pros also recommend checking ProSettings to see if any pro players have recently reported similar issues and their solutions, sometimes the esports community discovers workarounds before official support documentation catches up.
Conclusion
The “Waiting For Relay” error sucks, but it’s almost never permanent. Most cases are resolved by restarting your game, switching to wired ethernet, or clearing your cache, fixes that take minutes, not hours.
If quick fixes fail, work methodically through the advanced steps: check your firewall and port settings, update everything, reset your network. The vast majority of relay errors stem from one of these configuration issues. Only after you’ve exhausted the checklist is it time to contact support or consider account-level issues.
Remember that Call of Duty experiences server strain during major patches and season launches, sometimes “Waiting For Relay” is just temporary queue congestion, not a real error. Check server status before assuming something’s broken on your end.
The bottom line: you’ve got reliable tools to diagnose and fix this. Start simple, escalate systematically, and you’ll be back in matches within the hour. Now get back out there, those damascus camos aren’t grinding themselves, and your squad’s waiting for you in Call of Duty Spec Ops missions.