There isn't actually a slow-down or bottleneck shown yet. All we've seen thus far is "when you were in-game saying there was an issue, trying to traceroute you from Dallas showed many more routers (and an unknown number of additional hops) the traffic was taking once it reached Hawaii.Thonger wrote:But it sounds like the paths between my IP and EA117 has a bottleneck somewhere.
We can only suspect this may relate to the issue, until a stronger correlation is shown between "every time the problem happens, the route has also changed in this manner." Or the additional observations will end up disproving it, by seeing "the problem occurs even when the route doesn't have all these additional hops."
No, they aren't by definition identical, although in many cases they can be. It is suspicious -- but not by definition "wrong" -- that at the same time your /outbound/ traceroute showed only one hop inside Hawaii, my /inbound/ traceroute to your address showed the traffic passing through three or more different routers inside Hawaii. If you didn't need more than one hop to get out of Hawaii, it seems likely an error on TWC's part that the return packets are having to go through three or more routers inside Hawaii.Thonger wrote:Is my tracert going to be identical to yours (in reverse)? That is, does the signal coming back to me return through its original path or does it take the path you're seeing from your end?
I think a useful analogy is to think about it like a highway, where the northbound side doesn't have exactly all the same exits as the southbound side, and/or some of them are closed or detoured due to construction. If I'm headed /to/ you, I may be able to make different and/or smarter decisions that aren't necessarily the same as the decisions available to me later when I'm headed back home /from/ you. Even though "I intended to take the same main highway" both coming and going.
There is no way for you to see "what route will my traffic take when getting /back/ to me?" when running traceroute from your computer. All you can see is "which route did it take to get /to/ my destination?" Something would have to run a traceroute "from the destination back to you" (like I am doing) in order to see what route the packets in that direction are taking.
Just now when I looked (5:30am your time) the route is now "back to normal" for traffic I send your way. Meaning we're back to just one hop inside Hawaii:
We'll check again some time you're playing and you /don't/ see the lag, to see whether presence of the extra return hops correlates to when you're seeing the issue.tracert 184.108.40.206 wrote:Tracing route to xe-0-0-12.hnllhiqe01h.hawaii.rr.com [220.127.116.11]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms FIOS_Quantum_Gateway.fios-router.home [xx.xx.xx.xx]
2 4 ms 4 ms 4 ms xxxxxxxxxxx.xxxxxxxxxx.verizon-gni.net [xx.xx.xx.xx]
3 9 ms 6 ms 7 ms 18.104.22.168
4 * * * Request timed out.
5 36 ms 49 ms 38 ms 0.ae1.XL3.LAX15.ALTER.NET [22.214.171.124]
6 36 ms 46 ms 46 ms TenGigE0-6-0-5.GW5.LAX15.ALTER.NET [126.96.36.199]
7 36 ms 74 ms 36 ms tba.customer.alter.net [188.8.131.52]
8 37 ms 39 ms 39 ms bu-ether24.tustca4200w-bcr00.tbone.rr.com [184.108.40.206]
9 40 ms 39 ms 39 ms agg1.tustcaft01r.socal.rr.com [220.127.116.11]
10 39 ms 39 ms 39 ms agg10.lsancarc01r.socal.rr.com [18.104.22.168]
11 84 ms 84 ms 84 ms agg1.milnhixd01r.hawaii.rr.com [22.214.171.124]
12 96 ms 86 ms 96 ms xe-0-0-12.hnllhiqe01h.hawaii.rr.com [126.96.36.199]