Horrible West Coast connection

Discussion in 'Player Support' started by SpartanZero, Jan 15, 2019.

  1. SpartanZero

    I've no idea what's going on with the connection routing along the west coast, but connecting to Connery from Vancouver is horrid right now. Maybe the lines are frozen huhuhu.

    Connery currently gives me 5 to 6x my normal latency connection (which should be 35-50ms, on both parts)

    1 11 ms 9 ms 9 ms 50.67.160.1
    2 12 ms 44 ms 12 ms rc1st-tge0-8-0-23-1.vc.shawcable.net [64.59.148.
    13]
    3 18 ms 18 ms 25 ms rc2wt-be50-1.wa.shawcable.net [66.163.70.106]
    4 16 ms 20 ms 17 ms ae-7.a00.sttlwa01.us.bb.gin.ntt.net [168.143.229
    .41]
    5 135 ms 127 ms 139 ms ntt-gw.st6wa.ip.att.net [192.205.34.117]
    6 197 ms 190 ms * cr82.st0wa.ip.att.net [12.122.158.134]
    7 198 ms 194 ms 200 ms cr2.ptdor.ip.att.net [12.122.5.230]
    8 189 ms 195 ms 196 ms cr1.ptdor.ip.att.net [12.122.30.141]
    9 193 ms 199 ms 199 ms cr2.la2ca.ip.att.net [12.122.28.178]
    10 * 198 ms 195 ms cr1.sl9mo.ip.att.net [12.122.18.9]
    11 192 ms 202 ms * ggr3.la2ca.ip.att.net [12.122.128.9]
    12 205 ms * 193 ms 12.126.45.46
    13 175 ms 169 ms 164 ms be73.las-n9s1-core2.switch.com [66.209.64.141]
    14 * 168 ms 172 ms be1912.las-agg7s3-2.switch.com [66.209.64.226]
    15 * * * Request timed out.
    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.
    Connecting to Emerald on the other hand while a higher overall latency of 90-100ms is solid, green lit.
    1 11 ms 9 ms 10 ms 50.67.160.1
    2 14 ms 11 ms 12 ms rc1st-tge0-8-0-23-1.vc.shawcable.net [64.59.148.
    13]
    3 19 ms 18 ms 21 ms rc2wt-be50-1.wa.shawcable.net [66.163.70.106]
    4 53 ms 20 ms 17 ms rc1wt-be18-1.wa.shawcable.net [66.163.64.81]
    5 18 ms 25 ms 18 ms be4476.ccr21.sea02.atlas.cogentco.com [38.88.252
    .161]
    6 15 ms 19 ms 15 ms level3.sea02.atlas.cogentco.com [154.54.10.246]
    7 * * * Request timed out.
    8 89 ms 90 ms 85 ms SONY-ONLINE.bear1.Washington111.Level3.net [4.53
    .112.6]
    9 84 ms 86 ms 85 ms 69.174.216.23

    Trace complete.
    SpartanZero, Jan 15, 2019
    #1

  2. SpartanZero

    I should also add, I'm running a wired cable connection. Nor am I running any programs that would soak up bandwidth. This is purely a Connery West Coast connection issue. I've no other issues with other online games or connection spikes with Emerald, or even Cobalt. Those numbers are consistent. An these changes in Connery server/Latency for me happened shortly after the "fixed" connectivity issues were implimented.
    SpartanZero, Jan 16, 2019
    #2 Last edited by SpartanZero, Jan 16, 2019