If anyone is still having trouble, please provide a current trace route in this thread and we will forward to our network operations team for further review. Thanks!
Brian
Cox Support Forum Moderator
C:\Users\mbubl>tracert google.com
Tracing route to google.com [216.58.193.142]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.1.1]
2 10 ms 8 ms 9 ms 10.71.32.1
3 9 ms 9 ms 9 ms 100.120.104.132
4 16 ms 13 ms 26 ms 100.120.104.12
5 12 ms 13 ms 10 ms 68.1.1.167
6 14 ms 13 ms 19 ms 72.14.196.240
7 34 ms 25 ms 33 ms 108.170.247.243
8 13 ms 17 ms 16 ms 108.170.234.41
9 80 ms 79 ms 79 ms 209.85.251.136
10 83 ms 79 ms 87 ms 216.239.59.169
11 77 ms 78 ms 76 ms 108.170.240.193
12 87 ms 77 ms 78 ms 209.85.244.85
13 85 ms 77 ms 83 ms atl14s08-in-f142.1e100.net [216.58.193.142]
Trace complete.
C:\Users\mbubl>tracert 52.42.109.244
Tracing route to ec2-52-42-109-244.us-west-2.compute.amazonaws.com [52.42.109.244]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.1.1]
2 9 ms 9 ms 11 ms 10.71.32.1
3 13 ms 8 ms 16 ms 100.120.104.134
4 12 ms 13 ms 10 ms 100.120.104.14
5 11 ms 11 ms 15 ms 68.1.1.61
6 12 ms 11 ms 28 ms ip70-167-151-86.at.at.cox.net [70.167.151.86]
7 16 ms 17 ms 15 ms 54.239.102.90
8 54 ms 64 ms 12 ms 54.239.102.99
9 39 ms 37 ms 35 ms 54.239.42.120
10 * * * Request timed out.
11 62 ms 64 ms 53 ms 52.93.12.50
12 41 ms 35 ms 41 ms 52.93.12.37
13 39 ms 39 ms 41 ms 52.93.12.108
14 38 ms 37 ms 44 ms 52.93.12.131
15 36 ms 38 ms 36 ms 205.251.232.255
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.
Here's another one thanks.
C:\Users\mbubl>tracert 52.42.109.244
Tracing route to ec2-52-42-109-244.us-west-2.compute.amazonaws.com [52.42.109.244]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.1.1]
2 9 ms 9 ms 11 ms 10.71.32.1
3 13 ms 8 ms 16 ms 100.120.104.134
4 12 ms 13 ms 10 ms 100.120.104.14
5 11 ms 11 ms 15 ms 68.1.1.61
6 12 ms 11 ms 28 ms ip70-167-151-86.at.at.cox.net [70.167.151.86]
7 16 ms 17 ms 15 ms 54.239.102.90
8 54 ms 64 ms 12 ms 54.239.102.99
9 39 ms 37 ms 35 ms 54.239.42.120
10 * * * Request timed out.
11 62 ms 64 ms 53 ms 52.93.12.50
12 41 ms 35 ms 41 ms 52.93.12.37
13 39 ms 39 ms 41 ms 52.93.12.108
14 38 ms 37 ms 44 ms 52.93.12.131
15 36 ms 38 ms 36 ms 205.251.232.255
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.
C:\Users\mbubl>52.76.29.199
'52.76.29.199' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\mbubl>tracert 52.76.29.199
Tracing route to ec2-52-76-29-199.ap-southeast-1.compute.amazonaws.com [52.76.29.199]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.1.1]
2 13 ms 9 ms 12 ms 10.71.32.1
3 9 ms 9 ms 9 ms 100.120.104.132
4 10 ms 16 ms 9 ms 100.120.104.12
5 12 ms 12 ms 12 ms 68.1.1.171
6 11 ms 13 ms 13 ms 68.105.30.159
7 184 ms 183 ms 186 ms TenGE0-0-0-16.br02.hkg15.pccwbtn.net [63.223.17.6]
8 184 ms 200 ms 184 ms 63-217-17-42.static.pccwglobal.net [63.217.17.42]
9 215 ms 193 ms 199 ms 52.93.35.68
10 185 ms 184 ms 194 ms 52.93.35.77
11 224 ms 227 ms 235 ms 54.239.43.164
12 202 ms 209 ms 203 ms 54.240.241.119
13 201 ms 203 ms 202 ms 52.93.8.128
14 199 ms 215 ms 203 ms 52.93.11.43
15 211 ms 210 ms 210 ms 52.93.11.42
16 217 ms 225 ms 216 ms 52.93.8.139
17 201 ms 201 ms 201 ms 203.83.223.31
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.
looks like two months later and still no fix awesome, great ISP!
Do you mind giving us destinations to traceroute to for testing?
52.42.109.244 is the Fortnite AWS server based in Oregon that I use for testing. When I ping Google's DNS of 8.8.8.8 I get no packet loss, but whenever I play Fortnite, Rocket League or any game that uses AWS servers, I get 50%+ upstream packet loss. I'm also pretty sure that it affects Twitch live streaming by causing dropped frames because Twitch is owned by Amazon.
Here are my tracerts to the Oregon Fortnite AWS server. Tests were performed at around 11:30 a.m. PST. https://pastebin.com/AMFuwwQV
Traceroute has started…
traceroute to 52.42.109.244 (52.42.109.244), 64 hops max, 72 byte packets
1 192.168.0.1 (192.168.0.1) 0.566 ms 0.226 ms 0.181 ms
2 10.117.0.1 (10.117.0.1) 6.738 ms 7.038 ms 7.817 ms
3 100.127.73.40 (100.127.73.40) 7.602 ms 7.865 ms 8.311 ms
4 100.120.100.0 (100.120.100.0) 7.664 ms 10.149 ms 8.829 ms
5 langbprj02-ae1.0.rd.la.cox.net (68.1.1.14) 25.165 ms 21.159 ms 21.711 ms
6 52.95.218.216 (52.95.218.216) 20.384 ms 20.269 ms 26.351 ms
7 54.239.102.102 (54.239.102.102) 39.988 ms 29.250 ms 43.874 ms
8 54.239.102.109 (54.239.102.109) 18.713 ms 21.932 ms 24.331 ms
9 54.239.42.118 (54.239.42.118) 49.365 ms 45.187 ms 45.627 ms
10 * * *
11 52.93.12.114 (52.93.12.114) 47.041 ms 57.170 ms 49.561 ms
12 52.93.12.109 (52.93.12.109) 44.979 ms 45.581 ms 45.404 ms
13 52.93.12.144 (52.93.12.144) 87.528 ms 65.235 ms 78.519 ms
14 52.93.12.167 (52.93.12.167) 45.233 ms 45.136 ms 46.575 ms
15 52.93.240.59 (52.93.240.59) 50.181 ms 52.409 ms 54.057 ms
16 * * *
17 * * *
18 * * *
Traceroute has started…
traceroute to 52.42.109.244 (52.42.109.244), 64 hops max, 72 byte packets
1 192.168.0.1 (192.168.0.1) 0.745 ms 0.248 ms 0.190 ms
2 10.117.0.1 (10.117.0.1) 8.593 ms 7.539 ms 7.268 ms
3 100.127.73.40 (100.127.73.40) 8.429 ms 7.939 ms 8.259 ms
4 100.120.100.0 (100.120.100.0) 8.116 ms 8.752 ms 9.041 ms
5 langbprj02-ae1.0.rd.la.cox.net (68.1.1.14) 19.563 ms 21.153 ms 19.961 ms
6 52.95.218.216 (52.95.218.216) 21.581 ms 21.402 ms 21.162 ms
7 54.239.102.102 (54.239.102.102) 35.866 ms 46.345 ms *
8 54.239.102.109 (54.239.102.109) 36.819 ms 20.812 ms 23.031 ms
9 54.239.42.118 (54.239.42.118) 47.760 ms 46.451 ms 46.458 ms
10 * * *
11 52.93.12.114 (52.93.12.114) 75.515 ms 63.136 ms 66.644 ms
12 52.93.12.109 (52.93.12.109) 44.347 ms 52.249 ms 44.491 ms
13 52.93.12.144 (52.93.12.144) 76.781 ms 63.742 ms 101.767 ms
14 52.93.12.167 (52.93.12.167) 45.891 ms 45.936 ms 45.258 ms
15 52.93.240.59 (52.93.240.59) 49.745 ms 51.219 ms 46.678 ms
16 * * *
17 * * *
18 * * *
I am now having download packet loss as well as upload as of today
