JavaScript is required to use Bungie.net

Service Alert
Destiny 2 will receive an update tomorrow. Players will be required to log in to Destiny 2 again after installing the update. Please stay tuned to @BungieHelp for updates.

Forums

Edited by Mud Turkey 3: 9/21/2014 6:20:32 AM
1
So for three consecutive strike missions tonight, I've been Bee'd during the boss fights. I was unable to complete a single one today. My internal router diagnostics are reporting very minimal packet errors. I reset my router an hour ago. I've had 4 bee hours in this span. My router is not reporting a single drop or packet error out of close to 100,000 packet sents. *So note this please* The packet loss is minimal to zero. I have recieved the bee error 3 or 4 times in this span. I don't deny that packet loss could cause this error -- as you folks assert. But why am I getting it constantly with minimal to zero packet loss on a fuly open nat and forwarded ports on a private network? Things have been WAY worse since the first patch too.
English

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Hey I noticed we are having similar issues. Do you know if other people are sharing your network? I heard bee errors are bandwidth issues.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon