{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Guardian3528:
8/23/2024 1:12:02 PM
2
A large increase in currant and cabbage errors...
The entire day I've been getting thrown out of matchmade activities always getting either Currant or Cabbage as the error code. My setup is working fine, I can play other games online without issue. I've activated UPnP in my router and I'm on the Open NAT-type in-game.
What's going on here?
Edit: Still going on almost 12 hours later... Bungie?
-
3 RepliesHi! Thanks for reporting this to us. Currant errors are actively monitored by our team for potential issues, while Cabbage errors typically indicate your router settings are blocking communications to or from Destiny servers. I seem to understand that your ISP is Telia, as several users have mentioned in the comments. I'll relay this to my team for a more thorough investigation. If I may ask, what brand/model is your router? This will help us further investigate and find any potential root cause.
-
5 RepliesHaving the same error, started happening after the patch and nothing has changed on my end compared to before the patch.
