JavaScript is required to use Bungie.net

Help

Help us help you.
Edited by Antox: 8/10/2016 1:27:22 PM
28
14
Antox

WHICH NETWORKING HEADACHE ARE YOU HAVING SINCE HOTFIX 2.3.1.1?

Can't join matchmaking,supposed NAT type 3 issues!

11

Can't log into game at all!

35

Can't join fireteam! Kicked into space!

7

Matchmaking slowest it's ever been!

11

Red bar warriors ruling the galaxy!

35

Can't join other players on the same router!

64

Every error code under the sun!

36

[b][u] ***PLEASE BUMP! IF YOU VOTE IN THE POLL!***[/b][/u] [b][u]I'm interested to know how many people started having issues since hotfix 2.3.1.1 and are now persisting after the revert (not including issues Prior to that) and exactly what issues they are. In hope that this information will help bungie fix the problem faster.[/b][/u] This is the worst time I have ever had TRYING to play Destiny. It is clearly not our network setup causing so many issues on this grand scale. I have read many posts with so many people fustrated at the moment, clearly there is a problem with the game/servers otherwise they wouldn't have pulled the hotfix, which when released marked the start of the majority of players issues with the game at this time. No other games are having such bad connectivity issues, and again this all started when bungie changed something.
English
#Help #Networking

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
  • None of the above? We've tracked down issues in the Carolina's that are still not resolved. Problems we found with exchanges into XO.net cleared without us contacting them. Some Level3 exchanges still want to act up from time to time, but my ISP is usually able to route around it. So...the issues I have aren't game specific but ISP centric, so are being handled via my ISP. The problems were actually detected when affecting other services so weren't really impacting Destiny--when I know signalling is unreliable for twitch gaming, I don't load Destiny. So I've pretty much only seen the contacting servers one night when a player in Michigan was team leader. Otherwise I've only noticed the odd red bars here and there, but nothing has been game breaking on the networking side when I've played. But then again, I am more aware of the state of our routing in general than most may be because of all the time I've spent with my ISP in the issue. Perhaps some of you guys need to get in touch with yours as well. Make sure you are configured properly for this game's p2p model and if it persists bring your ISP's tier3 team on board to investigate.

    Posting in language:

     

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

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