[quote]Because of the copy and paste response that just avoids the topic and continues to blame the players for their connection and networking issues Im making this response. Yea some stuff is player side but its pretty easy to tell whats player side and whats not. For example not all that long ago, like 2 months ago I decided to run a quick test of my internet when playing other games in comparison to D2. Here's some basic results: Rainbow Six Siege: 9ms spikes between 20 and 40 but stable. Halo 3: 17ms spikes between 28 and 51 but stable. Halo 4: 13ms spikes between 19 and 34 but stable. Halo 5: 9ms spikes between 11 and 47 but stable CoD Modern Warfare (2019): 11ms (in beta too) with spikes across the board but its a beta, it happens CoD MW2: 14ms spikes between 26 and 62, slightly unstable. CoD MW3: 12ms spikes between 21 and 34, but stable StarCraft 2: 16ms spikes between 35 and 52 but stable Destiny 2: 39ms spikes between 63 and 84 and unstable This is unacceptable. Halo 3 is a decade old and yet its far more stable. Hell even MW2 is more stable and thats saying something. BO1, BO2, and MW2 are the three most unstable CoDs out there. I continued my test and found that on a dedicated server in Seattle (Im in Los Angeles for reference) my average ping with the amount of data in D2 going at once (forgot how much it was) would be around 15-21 and it would be relatively stable. And this was all with a slightly better than average wifi with someone else on it at the same time. We're not idiots Bungie. Edit Just did a full speed and stress test (not gaming) but still I know its not my wifi. I have Netflix and YouTube running on ALL devices in our house at once on the wifi and everything came back good. 20ms with spikes between 52 and 61 and stable. Download is 40.21mb/s and upload is 41.83mb/s with that much stress occurring on an above average router and plan. I still have 28.73mb/s to spare at that. There's 0 excuse for this nonsense Bungie.[/quote] Just a side note: milliseconds do NOT necessarely mean instability or whatever. I have to admit on my own that I sometimes get stupid error codes when playing, mostly beaver, to be honest and I would argue that something to make the matchmaking better actually can surely be done. However, throwing data here that actually hasn't much meaning doesn't help either: your original point is indeed valid, but milliseconds of latency don't cause any crash or whatever, but rather creates some arguably hard to perceipt delays (in the late 2000, I was playing with 133-267ms in halo, that was actually bad, but the average latency on xbox and ps4 is usually around 50-200ms and, lately, systems can handle latency pretty well) and, really, those latencies keep changing depending on the server you're connected to. The biggest problem I personally saw through a deeper network analysis on D2 is that the amount of lost packages needed to actually be dropped off an activity is really really low: my error codes weren't really related to my latency being either good or bad, but rather about suffering that little half second of packages being lost, which instead of making me able to simply lag in-game and be re-sync, rather dropped me off the activity, regardless whether I was in PVE or PVP. Latency instability, after all, shouldn't be your problem at all (and neither bungie's problem), it's rather the fact that sometimes you can't stay in contact with the server that seems to severely penalize you and most likely drop you off the activity, which doesn't sound much reasonable for PVE, though you may understand that it's fair in PVP to avoid people cheating through it. Now, regardless whether the problem is in destiny's netcode or whatever, I would like to throw in the fact that destiny 2 is actually complex: many interactions in PVE and PVP environment happens, perhaps not something spectacular in PVP Activities, but in PVE activities I would say that there arguably aren't many other games out there that actually are that complex, and this is NOT meant to defend anyone here, it's just my personal opinion. For those saying that the problem can be related to Wi-Fi: you guys should be aware that only a very bad Wi-Fi network can cause such issues. If the network is working properly and there are some connection issues between your machine (either console or pc) and your router, there must be severe problems to actually be kicked off an activity. To be entirely onest, my little analysis done through some free tools is not even barely sufficient to say that the netcode of destiny 2 is bad: it's my own analysis like your, but arguing that those guys can't do their job about matchmaking and netcode in general seems a bit... excessive, to me. Surely the feedback clearly proves that something is not working, but the whole thing is so big that I don't think anyone can actually argue that the problem is in their netcode, problems in this scenarios can be literally anywhere, including in the whole infrastructure.

[quote]I have tested mine multiple times on multiple days. It isn't every match but it is by far way too many and most matches. If it was just me that saw the stuff I would say it might be my connection but when I see the same thing everybody on my team is seeing then that tells me even more so that it isn't my connection. One of my friends has Google fiber with a 1gbps connection and he has seen the same things at the same times and another friend that does networking for a living that has said multiple times that his connection and network is solid and it isn't us and he works with multi million dollar companies and has done contract work with the government in his area. All of this with all that I have done and tested proves to me that it isn't my connection. Before we had the network guy join our clan I had spent hundreds if not on over a thousand trying different things different modems and routers and setting it all up the way Bungie says it should be for Destiny. I will not buy another $300+ router just to test again to see if it helps. When my game is on everything in my house gets cut to being allowed no more than 5mbps except the game and normally there isn't more than maybe normal cell connections and maybe youtube or netflix running.[/quote] Don't get me wrong: I'm not saying you have a bad internet connection. I'm not a very expert networking dude, I just happen to have played with networks a bit and, as a job, I'm actually a software developer (software analyst and developer). I'm trying to give you some suggestions about why it might not work as expected and actually trying to explain you what actually may impact your experience. To give you my final 50 cents, the network is almost always irrelevant in gaming once you have a very basic internet connection: right now, having a 10mbps / 15mbps, let's even say 20mbps to be very pessimistic with an average latency on a CLOSE ISP provider of 15 to 35ms is just enough to play any online game, there is no need to have 1gbps or whatever network in order to play well. Netflix, as many other services, is OPTIMIZED to work with any network, just think that you can watch a netflix movie even with 640kbps network (it's kbps, not mbit, so < 1 mbit). Those services (like netflix) has close to NO interaction with the final device: they just stream some data (usually compressed) and the client (your device) interpretes it, that's it. Destiny, on the other hand, has MUCH more to do, which is mostly communicating with your client to PERPETUALLY tell it many informations that need to be acquired and interpreted in the shortest possible amount of time. If you think about that, don't get me wrong, but these two scenarios have NOTHING in common: it's like comparing a pizza to a car: both might make you happy, but that's the only think they have in common (other than -eventually- the color). You DON'T need any 300$ router, don't get an epic car if you can't drive it (or just don't need it), get a basic one that works for your needs and try to inform yourself about WHY your scenario is not working as you expect by trying, for instance, to "debug" your environment: switching off some devices and testing might give you a feedback about why something doesn't work; doing further advanced analysis may prove that the fault is inside your network, or may prove that it's the exact opposite. If you're sometimes experiencing the issue on Destiny, it's not guaranteed that the problem is bungie related. Some advanced tweaks you may check is whether the issue happens when you play with someone on your team specifically: if this guy is behind a proxy, for example, you might play on a server which is far away from you due to the behavior of the matchmaking who tries to match the closest possible players with eventually the closest skill to yours: perhaps you're from America and playing in a russian server because some of you is behind a proxy identified in Russia, which makes the matchmaking to either match you against russian players or to match any player on a "middle" server which might cause undesired latency. Once again, it can be tricky to identify the problem, mine above are just suppositions and ideas, but really, I have a 40mbps down and 20mbps up network here (in Italy), my own network is not the top quality network, and when I get an error code in destiny, it's likely because, as mentioned in my previous post, I'm losing several packets in a small amount of time, which seems to be a severe issue with Destiny, hence I'm getting kicked off the activity, that's it. Unluckily, I can't do anything about that, I know the issue is there, my ISP provides this quality and can't give me more, so I just accept it and try to minimize it, I usually encounter an error every 50 matches or so, which is somewhat fine to me.

[quote]I’m umping this comment to the top so all the kids saying “iT’s YoUr InTeRnEt i’Ve NeVeR hAd ThOsE pRoBLeMs” can see it. They can’t deny actual data[/quote] But the accuracy/relevance of some of the data is a bit questionable. Still unclear exactly what the posted Bungie result represents. May have been overlooking one or more endpoints that are actually at fault for this player's instability, and/or could have been testing to an irrelevant endpoint altogether when it comes to gameplay. It could very well be an apples/oranges comparison here too, as this game is not structured in the typical client/server fashion... which is at the heart of asking for more details on how the testing was done.

Cloudflare isn't hosting the game... they do the website, perhaps web app stuff too? For gameplay stuff, you would be looking to Akamai, AWS, and/or Azure when it comes to the cloud hosting. I for sure have seen Akamai and AWS in play on my PS4... XBL may be using Azure instead of AWS tbougb?... who knows? Matchmaking can get tricky too... can run in to false positive matches pretty easily. Ping and such could look good while traffic is low and the target is sitting mostly idle. But then the route traffic could ramp up, or the target system or it's network could bog down under load. That may well be less of a Bungie problem to address and more of a User and/or relevant ISP(s) issue to address.

There's sites and what not out there that can calculate this and test your ping, even simulate it in certain game environments.

I'll do it this weekend when I get on ^w^ Thanks!

Bull, you're lying. It's so annoying when people defend cheap companies using cheap servers vs AAA gaming companies that are caught up to the 21st century. Bungie is even still using their broken engine that they even admitted they couldn't even fix the net cod in D1. Please stop spreading nonsense. I will agree that issues happen but nothing like playing Destiny and nowhere near as often and that is a fact.