I've been playing Destiny 2 for about five years without any major issues. However, since Tuesday’s update, I've encountered persistent errors when trying to log in—repeatedly receiving messages stating that the servers are offline along with Centipede errors. When I finally manage to log in and attempt to launch an activity, I’m met with a frustrating mix of Cabbage, Currant, and Coconut errors at random, making it difficult to start anything consistently.
Before you point me toward network troubleshooting guides, I've already exhausted those options. My NAT is not closed, I’m not using a shared network in a complex or building, and I’ve tried port forwarding and other configurations. The issue occurs across multiple devices, and I’ve contacted my ISP—there have been no changes or problems on their end. Notably, this only affects Destiny 2; no other services or games are experiencing issues.
Given the number of similar reports from other players, this seems too widespread to be a coincidence. It appears something on Destiny 2’s network side may be causing these errors, and it’s worth investigating further.
My ISP is Telmex, I've seen it mentioned on other post.
-
3 RepliesI'm in the exact same spot as you. I haven't been able to load into any activity, not even the tower and all started right after the weekly reset. Bro, all I wanted was the pew pew sparrow from the event, but I don't think I'll get it, the event ends tomorrow... I don't think this issue will be fixed before tomorrow smh