Increased ping issues

Left for the weekend and came back yesterday to latencies around 300 ms. I did a tracert with the results below. Would love any feedback that could point to the direction of what the cause may be. Thanks

PS: I’m in the Northeast so it seems to have me connected to Chicago as I would expect.

Tracing route to 24.105.40.50 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.2.1
2 10 ms 12 ms 12 ms 96.120.64.177
3 74 ms 42 ms 82 ms 96.110.30.9
4 11 ms 18 ms 9 ms 96.108.71.245
5 17 ms 18 ms 14 ms 96.108.71.45
6 117 ms 21 ms 19 ms be-7015-cr02.newyork.ny.ibone.comcast. net [68.86.90.217]
7 136 ms 164 ms 190 ms be-10396-pe01.60hudson.ny.ibone.comcast. net [68.86.84.78]
8 25 ms 18 ms 18 ms 50.208.232.150
9 105 ms 48 ms 40 ms ae1-br01-eqny8.as57976. net [137.221.71.33]
10 98 ms 48 ms 48 ms et-0-0-2-br02-eqch2.as57976. net [137.221.65.8]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Edit: other test done

Did the other test here are the results

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
192.168.2.1 - 0 835 835 0 0 27 0
96.120.64.177 - 1 827 825 9 208 481 89
96.110.30.9 - 1 831 830 8 207 532 16
96.108.71.245 - 1 828 826 9 212 484 36
96.108.71.45 - 1 820 816 12 208 502 21
be-7015-cr02.newyork.ny.ibone.comcast. net - 1 823 820 18 217 506 113
be-10396-pe01.60hudson.ny.ibone.comcast. net - 1 816 811 16 217 512 19
50.208.232.150 - 1 820 816 17 223 523 51
ae1-br01-eqny8.as57976. net - 1 820 816 37 239 522 107
et-0-0-2-br02-eqch2.as57976. net - 1 820 816 39 246 705 152
No response from host - 100 167 0 0 0 0 0
No response from host - 100 167 0 0 0 0 0
No response from host - 100 167 0 0 0 0 0
No response from host - 100 167 0 0 0 0 0
No response from host - 100 167 0 0 0 0 0
No response from host - 100 167 0 0 0 0 0
No response from host - 100 167 0 0 0 0 0
No response from host - 100 167 0 0 0 0 0
No response from host - 100 167 0 0 0 0 0
No response from host - 100 167 0 0 0 0 0
No response from host - 100 167 0 0 0 0 0
No response from host - 100 167 0 0 0 0 0
No response from host - 100 167 0 0 0 0 0
No response from host - 100 167 0 0 0 0 0
No response from host - 100 167 0 0 0 0 0
No response from host - 100 167 0 0 0 0 0
No response from host - 100 167 0 0 0 0 0
No response from host - 100 167 0 0 0 0 0
No response from host - 100 167 0 0 0 0 0
No response from host - 100 167 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Are you on a college network? Curious about all of those hops before we see the Comcast address appear. Some of the data is being lost on the second hop and beyond, with ping hitting 500ms occasionally. If it’s a private network you’ll have to address it with them, or call the ISP if it’s their equipment.

I bet your Steam is updating after not playing for a bit. 9 out of 10 times, it’s always Steam choking Overwatch while updating.

I am not on a college network. I am in an apartment complex and this issue just started up over the weekend. I am also experiencing long Pings to google’s DNS at 8.8.8.8 so I am no longer sure if this is an ISP issue or Overwatch servers.

This confirms it’s an ISP issue.