The latest Vow of the Disciple Destiny 2 raid has given players constant connection issues involving multiple error codes. Here's how to fix it.

Page Updated March 6, 2022, 10:25 |First Published March 5, 2022, 19:43

Destiny 2's Vow of the Disciple raid debut has been a bit of a disaster for Bungie after several users reported experiencing connection errors.

This was made worse because the highly anticipated Worlds First raid race has now been marred by these constant disconnects, with some important content creators stuck at the start of the raid for hours. 

It's not just those looking to claim the Worlds First belt the ones being affected, virtually any fireteam trying to play the Vow of the Disciple raid at the moment is being affected by error codes. Out of all the errors, the most common is far and wide is the error code Anteater. Here's everything you need to know about it. 

How to fix error code Anteater in Destiny 2

According to Bungie's official support website, the error code Anteater in Destiny 2 is simply a disconnection from the servers for unknown reasons. "Bungie is actively tracking this general networking error. Your disconnect was reported the moment it occurred," the website reads.

Naturally, there isn't a workaround for players to try out yet, as it simply means something on the Bungie side of things went wrong, prompting an unknown server error that disconnects players from the game.

Some users online have reported that removing certain mods would help with the error codes. For example, Tom Warren mentioned that unequipping Volatile Rounds stopped the error codes from happening.

we disabled volatile rounds and it stopped the errors

— Tom Warren (@tomwarren) March 5, 2022

However, as more and more fireteams tried this fix, it became clear that Warren's solution might have been purely coincidental.

What's worse is that even if you get past those connection issues, other bugs have taken place inside the pyramid. As a result, some teams, including Twitch streamer Datto, lost about 20 minutes attempting to find the subsequent encounter.

It turns out the raid got bugged, and the follow-up encounter was not triggering as it should've. Followingly, they were forced to back out of the game and re-enter with a checkpoint in place.

As always, as more connection errors or bugs crop up, we'll try to keep you updated as the raid race and Day 1 completions continue.

Featured image courtesy of Bungie.

For more Destiny 2 news, be sure to check out our dedicated section or take a look at some of our Guides & Tutorials just below:

Weekly Updates

Future Content

Best Hunter Builds

Best Titan Builds

Best Warlock Builds

Emblem & Shaders

Exotics, Catalyst & God Roll Guides

Game Guides