Bee is a client side issue. Please have a look at the error code article: https://www.bungie.net/en/Help/Article/11791
Also, [url=https://www.bungie.net/en/Support/Troubleshoot?oid=12915]Network Troubleshooting Guide[/url].
English
-
Same issue here. Never had this problem before. Destiny play since day 1. Called my ISP, uninstalled the game, new Ethernet cable, cleared my console cache, power cycled hardware, ISP ran packet loss tests. This is Destiny not client side. Please fix.
-
I’ve been getting bee since the last maintenance window and there’s nothing wrong with my connection. Ran tests, played other games, stream TV all day long. No other issues. Just destiny. It’s not client side.
-
Agreed. My connection is fine. I’m only having a problem with D2. Other games I have all work fine without any issues. D2 in fact worked just fine since release up until this recent update.
-
Yep. I got on Apex and Fortnite today in 60/100 person lobbies and didn’t have connection issues. It’s disappointing. Destiny finally turns a corner and looks to be pumping out great content again and now servers are failing. can’t get out of their own way.
-
Bearbeitet von TelKaz: 7/17/2019 6:40:44 PMI know that I read that these are 'client' side problems, but i haven't had any issue with the game at all, ever, until this 1.37 update on July 9. Things i have tried: ps4 in dmz static ip (both ipv4 and ipv6) dns name servers set to google dns on both route and ps4 destiny 2 port forwarding psn port forwarding my ps4 is always hardwired 500/500 fiber inernet uninstalled and reinstalled destiny 2 twice in past day disabled/enabled upnp just to test talked to Frontier about possible issues with Bungie Services nothing to see my latency is <10 ms restored licenses rebuilt databases Please let me know if there is anything client side i could have possibly missed. Just to add, none of my other online only games have any issues, i only can't stay connected to Destiny 2
-
Thank you. I will try to run through the steps on the troubleshooting guide. However, I have never experienced this issue once since year 1 until this recent update 2.5.1.1