You are connecting to multiple locations all at once... Bungie in the Seattle area, any number of different cloud service portals, and all the players that are matched with you. So it isn't exactly viable to ping just one location to get an idea of how your latency is stacking up. They really need to actually monitor your line as you are playing and experiencing issues so they can trace the routes and such themselves. Your ISP should at least make sure their routing to Bungie's ASN is actually performing in line with the metric's announced in their databases: AS394073 One of the "easier" ways to simulate things would be to run the batched latency tests, something like the testmy.net latency tests (can run each separately or click the icon to run all of them), or the ping test tool at dslreports.com. At the VERY least, any tests done should include the Seattle area so you can get some idea of how the routes are to the exchange points likely in play for your two persistent connections to Bungie. If you are using speedtest, you can click to change the test server and search by city or brand--for example you can test to Century Link in Seattle by searching on either "Seattle" or "Century".