I have a better answer,
I tried everything, and phoned my broadband provider, mine is extremely good at customer service i use ICUK but anyway heres your fix!
This is my response from my ISP,
Unknown to myself when I was contacting you, a colleague in the NOC
team was monitoring the packets and has made changes to help correctly
identify and classify this game. We suspect it had a signature that
matched a P2P application. I'm glad that it's fully functioning for
you, apologies for the disruption witnessed.
English
-
Yeah, I've been saying this all along in other threads. Destiny's network architecture looks like P2P packets to ISP/University routers. They block or otherwise filter these packets because many P2P packets are associated with illegal file sharing. The reason Bungie went to a P2P type architecture as opposed to a more standard client server architecture has to do with being able to scale up bandwidth for more connections. Many FPS games use a client server type of connection and that is the reason matches have a limited number of people that can play. Server bandwidth is not unlimited and in order to keep track of everything going on in game, there is a definite limit to the number of players that can play at the same time and keep everyone in sync. Destiny uses P2P type network architecture which allows each connecting client to add to the total bandwidth available to all peers. It's quite clever really. Theoretically speaking, you could have unlimited number of players in public maps. Anyone who has used P2P torrent software knows that the more peers you have, the faster the torrent becomes. The issue is that Destiny's data packets are being filtered or routed which is causing players to lag or get out of sync. Destiny must have certain minimum QoS performance requirements to ensure that all connected peers are synced and getting stable 30FPS. So anyone falling below certain thresholds will get booted so as not to affect all the other peers. I believe this is the origin of all these different error codes as they all point to a specific type of network fault that is supposed to be able to help Bungie troubleshoot.