Results 1 to 10 of 94

Hybrid View

  1. #1
    Player
    Whiz's Avatar
    Join Date
    Aug 2013
    Posts
    113
    Character
    Whiz Lightyear
    World
    Leviathan
    Main Class
    Lancer Lv 60
    maybe try switching service providers I hear time warner is decent. I signed a 2 yr with Fios so i'm screwed until next year if this issue isn't resolved.
    (0)

  2. #2
    Player
    remidi's Avatar
    Join Date
    Dec 2013
    Location
    Uldan
    Posts
    72
    Character
    Remi Dian
    World
    Gilgamesh
    Main Class
    Marauder Lv 50
    Quote Originally Posted by Whiz View Post
    maybe try switching service providers I hear time warner is decent. I signed a 2 yr with Fios so i'm screwed until next year if this issue isn't resolved.
    I had many issues with Time Warner. Their internet sucked and I would get throttled at random hours. FIOS is the best service in the USA next to Gfiber last I looked. This is the only game that has issues. Right now the game is running great for me though. Later I assume it will take a different route and turn to crap


    **Best big name service.
    (0)

  3. #3
    Player
    Lurkios's Avatar
    Join Date
    Aug 2013
    Posts
    422
    Character
    Lyli Hanabira
    World
    Sargatanas
    Main Class
    Arcanist Lv 70
    Quote Originally Posted by Whiz View Post
    maybe try switching service providers I hear time warner is decent. I signed a 2 yr with Fios so i'm screwed until next year if this issue isn't resolved.
    Just ran this between NY and the FFXIV:ARR server using Time Warner:

    1 ash1-pr1-xe-0-2-0-0.us.twtelecom.net (66.192.245.98) 36.439 ms 6.476 ms 6.450 ms
    2 xe-8-0-0.edge2.Washington4.Level3.net (4.53.114.9) 6.380 ms 6.360 ms 6.380 ms
    3 vlan60.csw1.Washington1.Level3.net (4.69.149.62) 31.778 ms vlan80.csw3.Washington1.Level3.net (4.69.149.190) 31.658 ms vlan70.csw2.Washington1.Level3.net (4.69.149.126) 31.762 ms
    MPLS Label=1191 CoS=0 TTL=1 S=1
    4 ae-72-72.ebr2.Washington1.Level3.net (4.69.134.149) 31.528 ms ae-62-62.ebr2.Washington1.Level3.net (4.69.134.145) 31.502 ms ae-92-92.ebr2.Washington1.Level3.net (4.69.134.157) 31.800 ms
    MPLS Label=1756 CoS=0 TTL=1 S=1
    5 4.69.201.94 (4.69.201.94) 31.683 ms ae-3-3.ebr1.NewYork2.Level3.net (4.69.132.90) 31.724 ms 4.69.201.86 (4.69.201.86) 44.695 ms
    MPLS Label=1172 CoS=0 TTL=1 S=1
    6 ae-1-100.ebr2.NewYork2.Level3.net (4.69.135.254) 32.862 ms 31.754 ms 31.767 ms
    MPLS Label=1172 CoS=0 TTL=1 S=1
    7 ae-45-45.ebr2.NewYork1.Level3.net (4.69.141.21) 31.539 ms 4.69.201.37 (4.69.201.37) 31.693 ms ae-47-47.ebr2.NewYork1.Level3.net (4.69.201.33) 31.365 ms
    MPLS Label=1197 CoS=0 TTL=1 S=1
    8 ae-5-5.car1.Montreal2.Level3.net (4.69.141.5) 31.546 ms 31.499 ms 31.476 ms
    MPLS Label=713 CoS=0 TTL=1 S=1
    9 ae-11-11.car2.Montreal2.Level3.net (4.69.141.1) 31.745 ms 31.805 ms 31.650 ms
    10 ORMUCO-COMM.car2.Montreal2.Level3.net (4.59.178.74) 31.907 ms 46.733 ms 33.759 ms
    11 192.34.76.10 (192.34.76.10) 50.813 ms 23.553 ms 23.541 ms

    As you can see, TW is also routing through Level3 and the problematic router.
    (1)

Tags for this Thread