Getting higher ping during the day on Comcast.

[Raist]

Looks like evidence of congestion in the middle actually. And as many have been reporting, it may be happening on TATA lines (as6453.net) as well as Comcast (your ISP?), not just Ormuco (SE's ISP):

ix-0-2-2-0.tcore1.00S-Seattle.as6453.net -    0 |  478 |  478 |   14 |   29 |  115 |   18 |
|if-13-0-0-4.core1.00S-Seattle.as6453.net -    0 |  478 |  478 |   14 |   45 |  234 |   23 |
|if-8-1-2-4.tcore2.CT8-Chicago.as6453.net -    0 |  478 |  478 |   96 |  107 |  149 |  111 |
|   if-3-2.tcore1.W6C-Montreal.as6453.net -    0 |  478 |  478 |   86 |   96 |  157 |   88 |

Note the bolded sections...look at the wide variance between your best and worst pings. The delay is increasing anywhere from about 55% increase (96 best to 149 worst, average 107 in Illinois) all the way up to a 15X increase in Washington (14 to 115 and 14 to 234 on two different hops, with their averages at 29 and 45 respectively). For just that one segment, your worst ping was 15x your best ping (not 15%, but 1500%), and 4 times your average ping. To put it another way, looking at just that one leg, you had at least one spike that took 400% longer for a response as the average response time on that leg, and 1500% longer than it's best response time--all within the short time frame of when you ran that test. Even if you throw that one 234ms response out of the mix, your average is STILL 44.6, with the best being 14 ms (45 X478 pings=21510, subtract 234 to get 21276 and divide that by the remaining 477 pings and you get 44.6). So it isn't just a single odd ball ping--- you still have a freakishly wide range of response times getting to/through that one hop alone.

Going back and looking at all your numbers more closely, it seems to be a bit off in general across the board. 7 to 153 with 23 average. and 13 to 116, with 25 average when in Washington on Comcast. Even the hops closer to you are showing an odd variance as well: 6-21 with 9 average, and 7 to 21 with 10 average.

There definitely seems to be some heavy congestion in route causing problems when going through the Washington area (both the Comcast and TATA networks there are showing issues), but it looks like there may be something close to home causing extra jitter as well.

Keep in mind that this can stack, as you aren't going just from your system directly to each hop in turn. Depending on the routing policies in effect, you may be passing through some if not all previous hops each time you move forward pinging each hop in your route in turn. So if you have multiple hops with problems, it may appear to get progressively worse as you go further down the list in the trace. For instance, if hop 4 and 5 are both having problems and they are also used in getting to hop 6--they may stack and make 6 look really bad, but 6 may actually be OK. The trick is for the techs at the ISP's responsible for those segments to figure out where it starts and move forward from there with testing. Why it's important to provide this information when filing a bug report--it gives them a road map to work with.

[Boretalith]

Greetings,

It seems that there have not been any further posts about this concern being an ongoing issue. Because of this, we are considering it to be resolved. If this does continue to be a concern, please create another thread to further discuss resolutions or contact the Support Center at support.na.square-enix.com for assistance.