Call of Duty connection errors, and how to fix them

Modern Call of Duty games need a live connection to Activision's servers for almost everything. When that fails you get a Connection Failed box, most often with the line Unable to access online services, or a message that Networking is offline followed by a reason code made of two place names, such as HUENEME - CONCORD or TRAVIS - RILEA.

The reason codes look specific, but Activision does not publish a list of what each one means. What it does publish is a status page and a set of connection tests, and those are the reliable route to a fix. This guide covers both, plus what the gaming press has established about the best-known codes.

Are the Call of Duty servers down?

Check our Call of Duty status page for live checks and player reports. Activision's own page is Online Services at support.activision.com/onlineservices. Pick your game from the list and it shows ONLINE or a problem for each platform: PlayStation 5, Xbox Series X|S, Battle.net, Steam, Xbox on PC and Nintendo Switch 2. Activision says that if the indicator for your platform is not green, or an alert is posted, you may have connection problems until service is restored.

The same page lists recently resolved incidents with start and end times. On 13 November 2026, for example, it logged a "Connectivity drop across listed titles" that lasted about an hour. Activision also posts updates on X as @ATVIAssist. If Call of Duty shows as online, check your platform next: PlayStation Network, Xbox, Battle.net or Steam.

Activision's fixes, in order

1. Make sure you are signed in to your platform account. Activision says trouble signing in usually means the console itself is not reaching the internet.
2. Run your console's connection test. On Xbox press the Xbox button, then Profile & system, Settings, General, Network settings, Test network connection. On PlayStation go to Settings, Network, Test Internet Connection. On Nintendo Switch 2 open System Settings from the HOME Menu, choose Internet, then Test Internet Connection.
3. Restart your router. Activision calls this often the easiest and quickest fix.
4. Use a wired Ethernet connection. Activision strongly recommends it for online play.
5. Stop other heavy use of your connection, such as video streaming and large downloads on other devices.
6. Fully close and restart the game, and install any update that is waiting. An out-of-date game cannot connect.
7. Test UPnP on your router. Activision's first router test: turn off any port forwarding and turn on Universal Plug and Play (UPnP), then try the game.
8. Then test port forwarding. If UPnP did not help, turn it off, give the console a static IP address and forward the game's ports to it. Activision lists a third, console-only test using the router's DMZ, and says to remove the console from the DMZ again once you have tested.

On a school, work or other shared network, Activision's advice is to speak to the network administrator. If none of the tests help at home, it says to contact your internet provider.

What the named codes mean

None of these explanations come from Activision. They are what gaming sites consistently reported while covering Modern Warfare II, Modern Warfare III and Warzone.

• HUENEME - CONCORD. Shown as "Networking is offline". The game could not reach the online servers at start-up. Reported during server trouble and on restrictive home networks.
• TRAVIS - RILEA. A "Connection failed" error where the network connection drops or times out while signing in to the online platform, after the game has started.
• GOLDFLAKE. A disconnection reported when a console wakes from rest mode or Quick Resume with the game still open. The reported fix is to close the game completely, or restart the console, and launch it fresh.

In every case the first two steps are the same: check the server status, then restart the game and the router.

What the two-word codes are

Call of Duty labels many of its errors with pairs of words, several of them American place names, in place of numbers. They are internal labels. Activision's support site does not list them, and its help articles for connection problems send every player down the same path whatever the code says. Treat the code as a search term, not a diagnosis, and be wary of any site that claims a guaranteed fix for one code.

Dev Errors are a different thing

A message such as Dev Error followed by a number is generally a fault inside the game, not a failed connection, so router changes will not help. Activision tracks the widespread ones on its Known Issues page for each game. In November 2026, for example, the Modern Warfare 4 list included Dev Error 0x26FEC466, which was stopping some players on all platforms from entering DMZ and was marked as under investigation. If your Dev Error is on that list, the fix has to come from Activision in an update.

Signs it is the servers, and signs it is you

• Servers: the error began at the same moment for friends on other networks, it started just after a season launch or update, or Activision's page shows your platform as anything other than online.
• Your platform: other online games on the same console fail too.
• Your network: the game connects through a phone hotspot but not your home broadband, or only one console in the house is affected. That last case often points to two consoles competing for the same ports, which is what Activision's UPnP test is designed to sort out.

What not to do

• Do not reinstall the game during an outage. The download is very large and it will not help.
• Do not leave a console in your router's DMZ after testing. Activision itself says to remove it.
• Do not give your Activision login or a two-factor code to anyone offering to fix an error. Activision support is reached through support.activision.com.

Related fix guides

• PlayStation Network not working: sign-in and connection fixes
• Can't sign in to Xbox: how to fix Xbox network problems
• Steam error codes -105, -118 and -102, and Steam not connecting
• How to fix Fortnite login and matchmaking errors