Forum Discussion
Traceroute to google.com
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router.asus.com - 23 | 183 | 142 | 0 | 0 | 2 | 0 |
| 10.170.0.1 - 0 | 351 | 351 | 2 | 9 | 61 | 7 |
| 68.6.10.140 - 0 | 351 | 351 | 3 | 10 | 62 | 10 |
| 100.120.108.0 - 0 | 351 | 351 | 3 | 12 | 62 | 7 |
| 68.1.1.167 - 1 | 347 | 346 | 10 | 16 | 95 | 18 |
| 72.14.196.240 - 5 | 295 | 281 | 21 | 30 | 89 | 27 |
| 108.170.247.179 - 12 | 243 | 216 | 24 | 31 | 84 | 28 |
| 108.170.247.161 - 7 | 274 | 255 | 20 | 30 | 80 | 33 |
| 216.239.40.169 - 7 | 280 | 262 | 0 | 30 | 82 | 33 |
| lax28s10-in-f14.1e100.net - 15 | 224 | 192 | 23 | 29 | 77 | 34 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
- Becky6 years agoModeratorHi eKayze, the two traceroutes to AWS server [34.204.152.174] show nothing of significance in regards to the Cox network. The timeouts once the trace reaches the Amazon network are to be expected. (Amazon Web Services servers don't return ping requests; they block ICMP packets for network security reasons.) The traceroute to Google shows packet loss beginning at hop 6 and carrying through to the end of the trace. What is most interesting about this packet loss is that it begins after the trace has left the Cox network and made it to the Google network. I ran a traceroute to 216.58.216.14 multiple times, but I'm unable to duplicate the packet loss, even though my trace also goes through the Google IP 108.170.247.161. Still, it could be due to my location. I'm curious to see if others on the west coast are also seeing packet loss within the Google network. -Becky, Cox Support Forums Moderator
- eKayze6 years agoNew Contributor
I think everyone in this post that are having issues are from the west coast. It happens everday from 5-6pm up until midnight.
- Juices6 years agoNew Contributor II
This is exactly the same time it happens to me^ I hope the investigation team is taking this issue seriously, Haven't been able to stream due to this issue, my only other option is DSL but i've had it before and it's absolutely garbage
Related Content
- 27 days agokcostel8621
- 6 years agoJamesM_
- 11 years agoPwar