{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
9/11/2025 2:09:47 PM
2
Cannot connect to Destiny 2 reliability
For the past two days, I've been encountering an unusual amount of Centipede, Currant, and Cabbage errors while trying to play or even log into Destiny 2. The times I do get in I can only play for like 30 minutes before the errors kick in. I've restarted my router several times, checked my connections, cleared the cache of my DNS server, and even contacted my service provider. Everything is working fine on my end. I've never had this issue before so before I give up on the game entirely, I wanted to see if there is an issue going on on Bungie's end.
-
3 RespuestasHi there, Thanks for reaching out. As a preliminary step to address this, please consult our [url=https://help.bungie.net/hc/en-us/articles/360048721992-Error-Code-CABBAGE]Cabbage error page[/url] for steps related to troubleshooting that issue. Following that, if issues persist, these can be caused by problems affecting your specific network hardware, packet loss, or greater issues affecting your ISP which are being passed on to you. All of this is possible even if your network seems fine at a glance. For further troubleshooting, we recommend consulting our [url=https://help.bungie.net/hc/en-us/articles/360049496531-Network-Troubleshooting-Guide]Network Troubleshooting Guide[/url] to explore potential solutions. If that doesn't help, the next step would be checking our [url=https://help.bungie.net/hc/en-us/articles/360049024092-Optimizing-Connections-Improving-Latency-and-Packet-Loss]Optimizing Connections[/url] page. Following that, if issues still persist, we would recommend asking your ISP for more hands-on assistance in troubleshooting your network setup.
-
Editado por Hwoarang45: 9/16/2025 1:50:52 PMSame issues, south east asia here, cant even log in now, chiken and weasel error. Last time this happened is when their server got DDOS attacked. [url]https://youtu.be/89OeiT4yqOk[/url]
