Results -9 to 0 of 6

Threaded View

  1. #3
    Player
    Raist's Avatar
    Join Date
    Aug 2013
    Posts
    2,457
    Character
    Raist Soulforge
    World
    Midgardsormr
    Main Class
    Thaumaturge Lv 60
    Quote Originally Posted by Zephanoa View Post
    Here is a tracert; here it looks like the problem is even further upstream; infact the issue looks like its Canada inet.

    2 12 ms 12 ms 7 ms 173-26-34-1.client.mchsi.com [173.26.34.1]
    3 9 ms 58 ms 9 ms 172.30.81.25
    4 13 ms 10 ms 7 ms 172.30.3.209
    5 13 ms 14 ms 18 ms 12.94.137.41
    6 26 ms 26 ms 23 ms cr1.kc9mo.ip.att.net [12.122.150.10]
    7 27 ms 27 ms 21 ms cr2.dlstx.ip.att.net [12.122.2.169]
    8 29 ms 27 ms 31 ms ggr3.dlstx.ip.att.net [12.122.138.17]
    9 21 ms 23 ms 25 ms 192.205.36.222
    10 23 ms 38 ms 29 ms be2031.ccr21.dfw01.atlas.cogentco.com [154.54.7.
    45]
    11 38 ms 41 ms 36 ms be2012.ccr21.mci01.atlas.cogentco.com [154.54.2.
    113]
    12 49 ms 50 ms 51 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.
    86]
    13 63 ms 60 ms 59 ms be2079.ccr21.yyz02.atlas.cogentco.com [154.54.27
    .182]
    14 67 ms 69 ms 68 ms be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30
    .206]
    15 71 ms 78 ms 74 ms 38.140.46.2
    16 159 ms 212 ms 242 ms te7-4.dr9.mtl.iweb.com [184.107.1.110]
    17 76 ms 76 ms 77 ms 72.55.128.44
    18 75 ms 76 ms 76 ms 184.107.107.176
    For the upteenth time.... that's a webserver--it hosts websites for projects from the EIDOS library. No connection to gameplay, and hosted on a completely different ISP's segments physically across town. All the game's servers in Canada start with 199 and are hosted on Ormuco segments.

    If you aren't going to look up the actual IP your client uses, at least use one of the lobby servers. Here they are again:

    neolobby02.ffxiv.com
    neolobby04.ffxiv.com
    neolobby06.ffxiv.com


    And you are showing signs of congestion starting earlier in your route that is likely stacking and making things much worse than they otherwise would be. One spot right near the start of your route, and another near the handoff to the routing partner Cogent. In that short sample, you are showing potentially almost 50ms of jitter where you should have around 5 or less...that can lead to some heavy skewing of the packet queues.
    (0)
    Last edited by Raist; 12-11-2014 at 03:14 PM.