So since yesterday, I've been kicked from missions and strikes at least 20 times, and gotten every error code under the sun. It's pretty much unplayable and since I love this game to bits, I'd really like to be playing on my day off.
I've gotten Bee, Cattle, Centipede, and Fly.
I've got an xbox one, im in western Canada and my ISP is Shaw... Oh, and my NAT is open. The correct ports are also open.
Who else is having this problem and when is bungie going to do something about it, assuming it is them, which I think it is.
-
I'm in the Texas panhandle and I haven't been able to log in today despite all efforts to fix the problem. The worst part is that Bungie hasn't said a damn thing yet. No encouraging statements letting people know that they are working on it.
-
Lizard squad is spamming destiny servers blame them
-
Edited by Und3rr4ted45: 9/22/2014 1:33:27 AMsame issues here keep getting kicked due to a bunch of random codes.... Im in Northern Washinton State.... Fix this please bungie! Oh im on a PS4 too not xbox.
-
I´m in Madrid (europe) and Im getting the same CATTLE error. D.T.Hell
-
I'm in Colorado USA and I'm blocked out too its bungies fault. I love them and I hate them. I just want tot be able to play their beautiful but I can't until they get this fixed.
-
I've had the same issues starting saturday myself as well. ISP is Shaw as well, slew of different errors come up. Everything was working perfectly fine till yesterday. Gone thru all the checks and still will get kicked. Western Canada as well.
-
Same demographic here, but the rest of my devices are working fine so I don't know if Shaw is to blame. Regardless I'm getting the same issues as you.
-
Central canada on shaw as well, played last night with no errors even played earlier Saturday and still none. Saturday night and I've been booted with a slew of errors over 10 times in 2 hours. Makes running crucible or strikes with friends pure rage inducing frustration. Xbox one as well, I have a feeling it's on bungies servers end being overloaded and dropping packets or not being able to keep up and dropping chunks of people to compensate. Please fix bungie it's not like you can't afford some more infrastructure.
-
I'm also in western Canada with Shaw.... same bs has been happing all day.
-
Hey I'm having the same problem, My net is fine, sometimes it runs smooth for a few hours then all of a sudden it boots me, then I can't get back in for a few hours, I'm really getting over it I jus wanna b able to play the game
-
Now I've been getting my internet doesn't exist! And what I find weird is it was playing perfectly fine this morning.
-
Can't even play now, because I'm getting kicked non stop.
-
today alone i have gotten:bee rabbit lion hyena coconut fly elderberry cattle centipede marionberry and groundhog. i dont think so many errors could be on my connection.
-
I've had berry, baboon, and elderberry everytime I tried playing destiny yesturday. I almost counted it to 20 times yesturday.
-
Edited by HellfireHD: 9/20/2014 9:08:38 PMSame here. In Kelowna on Shaw. Both my buddy and I can't play. NAT Open, Xbox in the DMZ. I'm so pissed! I've been waiting all week to get to play. Oh, in addition to the codes above, I've also received: Currant
-
Eh me too :/
-
[quote]So since yesterday, I've been kicked from missions and strikes at least 20 times, and gotten every error code under the sun. It's pretty much unplayable and since I love this game to bits, I'd really like to be playing on my day off. I've gotten Bee, Cattle, Centipede, and Fly. I've got an xbox one, im in western Canada and my ISP is Shaw... Oh, and my NAT is open. The correct ports are also open. Who else is having this problem and when is bungie going to do something about it, assuming it is them, which I think it is.[/quote] I got this problem last weekend as well and it's always bungie saying it's our service provider but my buddy has the same provider but he hasn't gotten the problem yet. I stopped playing for today.
-
I am with shaw as well... Its frustrating that bungie won't even acknowledge the issues.... Nothing to do with ISP.