• By Vikas Yadav
  • Sat, 18 Nov 2023 06:37 PM (IST)
  • Source:JND

Call of Duty Down: First-person shooter gaming title Call of Duty is now back after service disruptions in the United States. According to Downdetector, an outage monitoring platform, the reports peaked at 7,900+ at 06:08 PM IST. This is the second outage within 24 hours, with the first one striking the game at about 04:53 AM (around 1,800 reports) today.

According to the platform, 81 per cent of users reported problems with server connection, 15 per cent flagged glitches with the login page, and 3 per cent cited issues with the gameplay. The heat map indicates the outage affected the central USA the most, followed by other regions such as Dallas, Chicago, New York, Washington, Tampa, Atlanta and more.

Also Read: Good News For PlayStation Fans! Call of Duty Will Continue To Ship On PS5 and Upcoming Sony Consoles

"You have been disconnected from the Call of Duty: Modern Warfare III servers. Please try again [clipped message]," an error message read. The game developer has not issued any statement about the outage. Amid the rising disruption reports, users flooded X with diverse reactions. Here's what they shared.

1.

2.

According to comments on Downdetector, the game witnessed disruption in connecting with online services, login and more. One user on X said: "I can't login to call of duty servers. Is there any public issues?" Another one added: "The daily challenge wins are not working."

For the unversed, the franchise in the game includes Modern Warfare III, Modern Warfare II, COD: Warzone, COD: Warzone Mobile and COD: Mobile, as per the official website.

Also Read: Call Of Duty Players Infected With Self-Spreading Malware? Why Gamers Should Be Concerned?

Call Of Duty Down Update: 07:15 PM

It seems the game is now back after service disruptions. The reports have moved below 100 in the US. Users can head back to the game to check if they still face any server issues or problems with login. While the company has not issued a statement, it seems the problem was fixed internally.