Need some help trying to figure out what's going on with my connection. ISP - Frontier 200/200 fiber internet Desktop connected via hardwired connection to Frontier Gateway (Arris NVG448BQ) Desktop network adapter: Intel(R) I211 Gigabit Network Connection I am frequently getting disconnected from games regardless of activity (raid, crucible, gambit, sitting in tower, etc) My error codes have been Bat, Anteater, Baboon, buffalo, and a few others but i can't remember all of them. Things I've done to try and fix the issue- 1) reboot everything 2) called frontier and requested they reboot my ONT and look for errors on the interface (none found) 3) checked for any newer network drivers (there was one but issues still occurring) 4) tried swapping out the network cable Beyond this i've done a ton of small ping and tracert tests to try and see where the issue is happening upstream I know that from my PC across 500 pings i would consistently lose about 15% of my pings to 24.105.28.10 and my average latency goes up to around 68ms (think this is a battle.net authentication server?) To other sites such as amazon.com, fast.com, google.com, bungie.net - I lose about 1-2% of my pings and i see an average latency of around 9-10ms (all tests were done with a maximum latency of 1000ms) The tracert tests are the most confusing for me. If i tracert to 24.105.28.10 which is based in the US I end up going all the way out to a series of Netherlands based IPs before coming back state-side Here is the total tracert 1 <1 ms <1 ms <1 ms 192.168.254.254 2 3 ms 4 ms 2 ms 32.214.56.2 3 1 ms 1 ms 1 ms 32.223.0.172 4 3 ms 3 ms 1 ms 32.223.0.106 5 * 3 ms 6 ms 32.223.0.98 6 6 ms 4 ms 4 ms 32.223.104.181 7 * 1 ms <1 ms ae4---0.car02.wlfr.ct.frontiernet.net [74.40.71.101] 8 5 ms 4 ms 6 ms ae0---0.car01.wlfr.ct.frontiernet.net [74.40.4.125] 9 * * * Request timed out. 10 4 ms 4 ms 4 ms ae0---0.scr01.sccs.nj.frontiernet.net [74.40.3.234] 11 4 ms 4 ms 4 ms eqix-ix-ny8.blizzard.com [198.32.118.87] 12 * 68 ms 68 ms ae1-br01-eqny8.as57976.net [137.221.71.33] 13 * 68 ms 83 ms et-0-0-2-br02-eqch2.as57976.net [137.221.65.8] 14 * 68 ms 68 ms et-0-0-29-br01-eqch2.as57976.net [137.221.65.2] 15 68 ms * * 137.221.65.132 16 70 ms 70 ms 70 ms et-0-0-2-br01-eqla1.as57976.net [137.221.65.68] 17 70 ms 81 ms 69 ms be1-pe02-eqla1.as57976.net [137.221.68.69] 18 69 ms 70 ms 70 ms lax-eqla1-ia-bons-03.as57976.net [137.221.66.5] 19 * * * Request timed out. 20 68 ms 68 ms 68 ms 24.105.28.10 Trace complete. In addition to this while matchmaking i usually attempt to connect to a 172.97.56.0 subnet server. When I do this tracert my connection through Frontier is fine until i reach the provider above.net and then go through zayogroup networks where my latency jumps up to an average 59ms. beyond the zayonetworks IPs i don't receive an responses from any other hops going to the 172.97.56.0 servers C:\Users\quick>tracert 172.97.57.84 Tracing route to 172.97.57.84 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.254.254 2 2 ms 1 ms 1 ms 32.214.56.2 3 2 ms 1 ms 1 ms 32.223.0.172 4 6 ms 1 ms 2 ms 32.223.0.106 5 * * * Request timed out. 6 2 ms 3 ms 3 ms 32.222.231.97 7 1 ms 1 ms <1 ms ae4---0.car02.wlfr.ct.frontiernet.net [74.40.71.101] 8 6 ms 4 ms 4 ms ae0---0.car01.wlfr.ct.frontiernet.net [74.40.4.125] 9 * * * Request timed out. 10 8 ms 4 ms 4 ms ae0---0.scr01.sccs.nj.frontiernet.net [74.40.3.234] 11 * * 4 ms above.net [198.32.118.25] 12 59 ms 89 ms 59 ms ae10.cs1.lga5.us.zip.zayo.com [64.125.27.156] 13 * * * Request timed out. 14 65 ms 61 ms 59 ms ae5.cs1.den5.us.eth.zayo.com [64.125.29.19] 15 59 ms 59 ms 59 ms ae12.cs1.las2.us.zip.zayo.com [64.125.30.243] 16 59 ms 59 ms 59 ms ae7.mpr2.las1.us.zip.zayo.com [64.125.28.111] 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. I've reached out to Frontier to see if they could talk to Zayo's network regarding to the jump in latency but I've been told since it's beyond their network they have no control so i'm out of ideas. All this started within the past few weeks. Prior to this I've never had a connection issue with this game so i'm not sure why it's started now.