{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
1/6/2026 4:46:46 PM
1
Hi there,
Thank you for reaching out to us.
We understand you're experiencing difficulty connecting to Destiny 2. We're sorry to hear of this, as we can imagine the concern this may have caused. By any chance, are you encountering any error codes? Also, if you haven't yet tried doing so, does [url=https://help.bungie.net/hc/en-us/articles/360049496531-Network-Troubleshooting-Guide]Network Troubleshooting[/url] help you to connect?
Please let us know the above information, and we'll review.
English
-
Edited by Dyndase: 1/7/2026 2:56:47 PMI am seeing so many people cannot establish stable connections to Destiny 2 server no matter what which ISP they are using. Centipede is a stable issue everyone has found on day one. I speculate that people are experiencing packet losses, hence creating all the errors; weasel, Baboon, Centipede, Elderberry, etc. because the client cannot have a stable connection to Destiny 2 server despite the Internet is working without issue. Constant "Connecting to Destiny 2 Server" appearing everywhere. Signing in, Character selection, Orbit, Tower, etc. The game is mostly unplayable right now after Renegade updates. Moreover, my current gears are not updating to DIM as well. It has been 30 minutes since I've change my gears. This is the first time I am having this problem. I implore you to look into the connection issues again.
