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

9/21/2014 7:03:39 PM
0
I've been playing since launch day (almost two weeks now), and I haven't had a single problem aside from one disconnect about 3 days after release. It was a no name error that kicked me to my ship. I restarted the match, and everything has been fine up until yesterday. Then, I started getting Cattle errors for about a half hour or so, and I couldn't even log in. That seemed to have fixed itself after a couple hours, and then I played for maybe 4 straight hours that night after I got off work, along with the 2 or 3 I played after the Cattle errors subsided before I had to go to work. I thought I was in the clear. Oh, how wrong I was. Now, I'm getting the Bee error after about 10 minutes into a strike. It's really aggravating. I would say that it was on my end if this had been happening from the start, but I've been playing nearly everyday for at least a few hours for nearly two full weeks. If it's on my end, how could this just start happening now? Nothing has changed in my home network between then and now. Even the beta ran just fine for me. I had maybe two or three disconnects the whole time I played, and that was a beta. Now, I've played nearly flawlessly for almost two weeks on the full game (which I've been enjoying), and it's going to choose now to start giving me issues? Just to add insult to injury, I'm actually off on a weekend, and I have all day to do whatever I want. Well, I guess it's not going to be playing Destiny.
English

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