JavaScript is required to use Bungie.net

Help

Help us help you.
11/23/2014 6:55:05 AM
15
17
Batz

Four days.

Four -blam!-ing days, that''s the longest time I've managed to stay away from a barrage of error codes and it happened from Tuesday to Saturday this week. That's not to say I didnt recieve any error codes at all, there was the Vulture relapse for an hour or two - but the game was atleast playable. Come the weekend - and for some reason I've noticed that Mondays also are more trouble than the standard - and it's unplayable again. UNPLAYABLE! Don't tell me that it's not when I don't even have time to knock out a patrol mission between Bees and Currants. So basically, what the hell is going on? I'm open to the possibility that XBL might be a factor but for some reason I've never had these issues in other XBL games. Not to mention that I played PC games for the past couple of years, on the same connection, and never got thrown out. What i don't get is how it can be fine one day and total chaos the next. Are you constantly doing some background stuff or is it in correlation with game population? In the event of the latter, isnt it time that you perhaps opened up some additional channels so that it won't happen every week? And the money doesnt really bother me but when you invest in both the xbox and xbl to play this game - and this game only - it's like throwing money in the sea. It doesnt matter how rich or poor you are, it's still a waste.
English
#Help #Errorcodes

Posting in language:

 

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

View Entire Topic
  • Hi Batz, I am sorry to hear you have been experiencing connection issues, and we understand it is frustrating to hear that changing your home network can help if it was working previously, but many others have reported success by following the steps on our help pages, which I will post here just in case: http://www.bungie.net/en/Help/Article/11930 . In some cases, even power-cycling the router/modem and the console itself can get rid of these errors, as CURRANT is a general network error. Additionally, it may be a temporary connectivity issues attributed to heavier or slower traffic than normal in your physical area. If none of the above-mentioned steps work, we are aware that sometimes this is out of the player's control, and we understand this may be an issue you cannot solve alone. In all cases, we’re constantly monitoring and improving our network services to keep Destiny up and running for as many players as possible.

    Posting in language:

     

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

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