If Warzone or Black Ops 7 is frozen on "Waiting for Relay," your internet is probably fine — the game just can't finish the handshake to the server. The good news: this is one of the most fixable errors in Call of Duty, and the quickest fix takes about 30 seconds. This guide covers exactly what the error means, the fast fix that clears most cases, and the full advanced list for PC, PS5, and Xbox in Season 4 Reloaded — so you spend your July grind in matches, not on a loading screen.
Quick answer: how to fix "Waiting for Relay" in Call of Duty
Fully close the game (don't just back out to the menu), wait ~30 seconds, and relaunch. This single step resolves the large majority of "Waiting for Relay" cases because it forces a fresh connection handshake to the relay server instead of retrying a stale one. On PC, an even faster trick players confirm: alt-tab out and back in once, and the match often loads immediately.
If a restart doesn't stick, work down this order: check the server status → switch to wired Ethernet → clear the game cache → set your NAT to Open (UPnP/ports) → change your DNS. According to the widely-cited 2026 relay-error breakdown, quick fixes resolve roughly 70% of cases in under five minutes, and switching to wired Ethernet alone fixes it for about 30% of affected players. The rest is network configuration — which we walk through below.
What does "Waiting for Relay" mean in Warzone and Black Ops 7?
"Waiting for Relay" appears when Call of Duty can't complete the connection handshake between your device and its servers. Your device first has to reach a relay server, which then routes you to the actual game server. If that relay handshake stalls — even with a perfectly working internet connection — you get stuck on the "Waiting for Relay" screen instead of loading into the lobby or match.
That's the key thing to understand: a stuck relay is almost never a "your Wi-Fi is down" problem. It's a routing or configuration issue between you and Activision's relay layer. That's why speed-testing your connection and seeing "everything's fine" is so common — and why the fixes below target routing, NAT, ports, and cache rather than your raw download speed.
Common triggers include:
- A stale or failed connection attempt — the game keeps retrying a dead handshake (the #1 cause, and why a full restart works).
- Server load or maintenance during peak hours or right after a patch.
- Strict/Moderate NAT, closed ports, or firewall blocks stopping the relay handshake.
- Corrupted game cache from a failed or interrupted update.
- VPNs and the Discord overlay intercepting or rerouting network packets.
The 30-second fix (works ~70% of the time)
Before touching any settings, do this:
- Fully close Call of Duty. Not "back out to the main menu" — quit the application completely (on PC, close it via the launcher or Task Manager; on console, close the game from the dashboard, don't just rest-mode it).
- Wait about 30 seconds. This gives the relay server time to drop your previous failed session so it stops trying to resume a dead handshake.
- Relaunch and queue again.
Players repeatedly confirm the pattern: "a couple of restarts usually does the trick," and the error very often appears right after using Quick Resume / rest mode — a full relaunch clears it. On PC specifically, alt-tabbing out and back in once frequently kicks the match into loading without a full restart. If you're stuck, try that first; it's the cheapest fix there is.
If restarting doesn't hold after two tries, it's a network-configuration issue — keep going.
Is it just the servers? Check status first
Before you rebuild your network settings, rule out Activision's side — especially in the first hours after a Season 4 Reloaded update, when everyone reconnects at once and the relay layer is under load.
- Check the official Call of Duty / Activision server status page and the in-game alerts.
- Check a live outage tracker (Downdetector) for a spike.
- Glance at the r/CODWarzone and r/blackops7 new feeds — if hundreds of players are posting the same error in the same hour, it's server-side and no amount of port forwarding will fix it. Wait it out.
If servers are green, the problem is between your device and the relay — fix it below.
Advanced fixes for PC (Battle.net / Steam)
Work these in order; most players are back in by the NAT/ports step.
- Switch to wired Ethernet. Wi-Fi packet loss is a leading relay-handshake killer — a cable resolves it for roughly 30% of players on its own.
- Run a launcher repair. On Battle.net, use Scan and Repair; on Steam, use Verify integrity of game files under Installed Files. This fixes the corrupted-cache cause from a bad update.
- Whitelist Call of Duty in Windows Defender Firewall, and temporarily disable any third-party antivirus/VPN to test.
- Open the NAT — this is the big one. Enable UPnP on your router (log in at `192.168.1.1` or `192.168.0.1` → Advanced → UPnP → enable), or manually forward the official ports (below). An Open NAT lets the relay handshake complete cleanly.
- Switch your DNS to Google (`8.8.8.8` / `8.8.4.4`) or Cloudflare (`1.1.1.1`) — bad ISP DNS routing can stall the relay lookup.
- Disable IPv6 temporarily and update your network adapter drivers.
- Disable the Discord overlay — it intercepts network calls and can trigger relay errors.
If the game won't even reach that screen and instead won't launch, players have fixed it by deleting the local player-profile folder (search your C: drive for the "Call of Duty" documents folder and remove the profile/cache folders — leave the Steam/Blizzard/Xbox data intact) and by launching through Battle.net rather than a third-party path.
The official Call of Duty ports and NAT guidance
Straight from Activision Support's "Port Forward and NAT FAQ," the target is simple:
"An Open/Type 1 NAT will provide the best connection quality."
Per Activision's official "Ports Used for Call of Duty Games" list, forward these on your router:
| Protocol | Ports |
|---|---|
| TCP | 80, 443, 1935, 3074, 3478–3480 |
| UDP | 3074, 3478–3479 |
Set a static IP for your PC/console first so the forwarded ports don't drift to another device, then reboot the router after saving. If your ISP blocks ports at their level, placing the console/PC in the router's DMZ is the last-resort workaround.
Advanced fixes for PS5 and Xbox
The console causes are the same (routing, cache, NAT) — the menus differ.
PlayStation (PS4/PS5):
- Run Test Internet Connection in Network settings and check your NAT Type — aim for Type 1/2 (Open/Moderate); Type 3 is the relay-killer.
- Forget and rejoin your Wi-Fi, or go wired.
- Set DNS manually (Google/Cloudflare above).
- Keep the game on internal PS5 storage, not an external SSD, and clear the system cache (full power-down, not rest mode).
| **Xbox (Series X | S / One):** |
|---|
- Check NAT Type is Open under Network settings; if it's Moderate/Strict, enable UPnP on the router.
- Clear the alternate MAC address (Network settings → Advanced), then restart.
- Confirm your Xbox Live region is correct and you're on the primary account, not a guest.
- Forget/rejoin Wi-Fi or switch to Ethernet.
Whichever platform you're on, the winning combo is almost always Open NAT + wired connection + a clean relaunch.
Waiting for Relay vs. the other Season 4 connection errors
"Waiting for Relay" is a routing/handshake stall — it's not the same as the anti-cheat and boot errors going around this season, and the fixes don't overlap:
- If you're blocked at boot by "Failed Attestation" or a BIOS/Secure Boot/TPM message, that's Ricochet anti-cheat, not relay — see our Warzone Failed Attestation & BIOS fix guide and the advanced 'BIOS Update Required' still-failing fixes.
- If you're hitting the enrollaik.exe / "Failed to Enroll AIK" error, that's a separate anti-cheat enrollment issue — see the enrollaik.exe fix.
- Coming back after a break and everything feels broken at once? Start with the Warzone Returning Player guide, which covers the lockout errors together.
Match the error name to the right guide and you'll fix it far faster than blindly reinstalling.
Back in the lobby? Make the grind count
Once you're reconnected, the fastest way to claw back the time you lost on a loading screen is to grind efficiently — the July Summer of Action window and 2XP tokens make this a good moment to push levels. If you'd rather skip the slog entirely, that's what we do:
Get straight back to what matters — leveling, camos, and wins — instead of fighting your router.
- CoD Account & Weapon Leveling — skip the grind, ranked-up by pro players.
- CoD Bot Lobbies — easy lobbies to level fast and pad stats.
- CoD Camo Unlocks (BO7) — mastery camos done fast and secure.
- All Call of Duty services — everything in one place.
For a full breakdown of the fastest legit XP routes this season, see our Warzone Fast Leveling guide.
FAQ
What does "Waiting for Relay" mean in Call of Duty? It means the game can't finish the connection handshake between your device and a relay server that routes you to the game server. Your internet can be working fine — the relay itself is stalling, usually because of a stale connection attempt, a strict NAT, closed ports, or a cache issue.
Is "Waiting for Relay" a server problem or my problem? It can be either, so check server status first. Right after a Season 4 Reloaded patch or during peak hours it's often server-side, and you just wait. If servers are green and only you are affected, it's your routing — restart the game, then fix NAT/ports/DNS.
Why does it keep happening after Quick Resume or rest mode? Quick Resume and rest mode resume a session with a dead relay handshake, so the game gets stuck retrying it. A full close and relaunch (not rest mode) forces a fresh handshake and clears it — this is the single most reliable fix.
How do I set an Open NAT for Warzone and Black Ops 7? Enable UPnP on your router, or manually forward Activision's official ports — TCP 80, 443, 1935, 3074, 3478–3480 and UDP 3074, 3478–3479 — to a device with a static IP. Activision states an Open/Type 1 NAT gives the best connection quality, and it clears most relay handshake failures.
Does a VPN cause "Waiting for Relay"? It can. VPNs reroute your traffic and can confuse the relay routing, and the Discord overlay can intercept network packets too. Disable both to test, then reconnect.
Will reinstalling fix it? Rarely, and it should be your last resort. A launcher repair (Battle.net Scan and Repair / Steam Verify integrity) fixes the same corrupted-cache cause in a fraction of the time. Try restart → wired → cache repair → NAT/ports → DNS before a full reinstall.
