Forum Discussion
Becky
7 years agoModerator
Hi User, since you've posted on several other threads regarding packet loss and the AWS servers, you know that my team and the network engineering team are investigating these reports. Please bypass your router, connect a device directly to your modem, and reset the modem. Then, run 2 traceroutes (or PingPlotters) to the AWS server in question and one traceroute to www.google.com. Post your results here or email them to cox.help@cox.com. -Becky, Cox Support Forums Moderator
Tikerz
7 years agoNew Contributor II
Here's pingplotter from my latest RL game.
You can see huge packet loss to Level3.net servers.
Target Name: 104.153.85.100
IP: 104.153.85.100
Date/Time: 9/10/2018 11:37:01 PM - 9/10/2018 11:47:01 PM
Hop Sent PL% Min Max Avg Host Name / [IP]
1 19 0 0.83 55.14 7.55 192.168.1.1 [192.168.1.1]
2 19 0 9.45 14.51 11.28 10.48.128.1 [10.48.128.1]
3 19 0 8.12 146.06 25.53 100.127.74.28 [100.127.74.28]
4 19 0 8.49 98.42 24.88 100.120.100.12 [100.120.100.12]
5 18 67 11.20 22.42 13.85 lag-103.bear2.Phoenix1.Level3.net [4.14.52.225]
6 5 80 63.52 63.52 63.52 ae-1-3502.ear2.Washington12.Level3.net [4.69.140.117]
7 19 0 66.78 171.64 79.90 INTERACTIVE.ear2.Washington12.Level3.net [4.16.76.162]
8 19 0 65.17 287.28 80.31 104.153.85.100 [104.153.85.100]