{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
12/4/2019 7:36:24 PM
2
More often it is an issue occurring in route, typically something up with the intermediary ISP connecting the two endpoint ISP's.
Would be something for your ISP to investigate, which has to be requested from your end... because, well, you are their paying customer--not Bungie.
That is why they are telling you to address your connectivity issues... the investigation needs to be instigated from your end.
English
-
While you could right you really got ask why can I do other things like Netflix and such and not have one issue what so ever. And other play destiny with no issues. But then have an issue like I did where other people using different isps in different states or countries are having the same exact codes and disconnects. But the only thing they tell you is check ur equipment. I went through everything and after I complained it finally resolved. Everyone can't have the same issue at the same time with different states country's or isps at the same time. And when bungie screws up they admit that there's an issue unless it knocks everyone out. Really makes you wonder who's really telling the truth.
-
Because, as I mentioned earlier, it is often an issue at the peering level. Your network does not connect directly to Bungie's networks, nor the cloud service, nor every other individual player network. You will hop through up to a dozen or more unique network segments, often under the management of at least 3 different ISP's--yours, theirs, and one in between. That third party ISP has peering agreements with each of the endpoint ISP's. Mainstream ISP's typically have peering arrangements with three or more third-party ISP's... at bare minimum 2. In Bungie's case, the bulk of their data is carried across Level3/Century Link. Last I looked at their BGP/IGP data it was like 95%. A big chunk of Spectrum's traffic from the southeast also goes across Level3 (by way of the Atlanta area). Now, add this all together. Level3 is having issues in the Seattle area, as well as Southern California. They are also having issues in Atlanta. Spectrum is having issues in Charlotte, Raleigh, Atlanta, and south/east Texas. Spectrum South East routing corridors to Bungie's ASN favors Level3 via Atlanta, Las Vegas, several spots in Southern California, and up through Seattle. Basically, there is only ONE decent level3 corridor announced atm from the south east toBungie... by way of Vegas. If people's ISP's tables are not updated to avoid the troubled segments on Level3, they may all be getting sent along troubled routes if they are getting directed to Level3 instead of TATA, Cogent, or Zayo.
