Blizzard has released The Burning Crusade, but players are experiencing connectivity issues and are unable to play

Jun 2, 2021 09:37 GMT  ·  By

According to Blizzard, they are under massive DDoS attack, that may cause significant latency and disconnections for some gamers. The company also says that it's working hard to address this issue. 

Blizzard Entertainment is a California-based American video game developer and publisher. It created incredibly successful games such as Overwatch, Diablo, World of Warcraft, Starcraft, and Warcraft.

Their statement is posted on the following tweet

A Twitter user responded to Blizzard's announcement that this could be due to poor load balancing on their systems rather than a DDoS attack. His position in the game's queue was 2376, and his turn to enter the game was expected to take 54 minutes.

A distributed denial-of-service (DDoS) attack occurs when numerous systems flood the bandwidth or resources of a target system, typically one or more web servers. A DDoS attack uses multiple unique IP addresses or workstations, often from thousands of malware-infected computers. A DDoS attack often involves more than 3-5 nodes on separate networks; fewer nodes may be considered a DoS attack but are not a DDoS attack.

Are Blizzard's connectivity issues caused by a lack of IT infrastructure or DDoS attacks? 

The event could be related to the fact that they recently released The Burning Crusade earlier today. This type of incident happened before when they released a new game.

Blizzard seems to have a pattern of attributing connectivity troubles to DDoS attacks. Whether the attacks are real or the result of bad system/network administration, gamers are harmed by these issues.

When gamers attempted to play World of Warcraft in January of this year, they encountered the same issues with high latency and disconnections.

Blizzard has faced similar challenges several times in the past year. Two complaints of DDoS attacks were registered in April and June.

The company says that its support team is working to mitigate this issue right now.