Fix The Lag For Hawaii Or Im Out

[Demonchld]

Love the game love the damn music the play style the graphics havent even got to 50 yet im so hooked.

But if u dont do something about the lag in Hawaii I wont be renewing at all whats the point of an awesome game is its unplayable.....

as much Japanese that come to Hawaii you would think that they would make Hawaii perfectly playable but I guess not....

Come on now Squarenix I get a better player experince with League of Legends and that game is Free

[Sanie_Kyoto]

It's not you, it's the servers. Everyone is having problems at this moment. Seems like they can't stop being cheap and buy better servers or sustain their servers from being congested.

[Demonchld]

they need to fix it asap this is crazy come on if a damn free to play game can handle the traffic then sure as hell a pay to play game can I dont want to see a rerun of version 1.0 I love this damn game too but if they cant get there shit together people are going to quit

[Sanie_Kyoto]

It'll get stable, just like any other game. League of Legends had that same problem on release launch, even after beta. Even Final Fantasy XI had those issues back in 2002-2003. It just takes patience, I'm just happy Yoshi take's responsibility, just wish they would focus on new content less and try to resolve their server and connection stability a bit more before releasing anymore crap which might congest the servers from more coding bugs and you know the who common sense deal.

[Demonchld]

I cant even get on at all now I can get Japan server fine but Diablos on us I cant login at all

[Raist]

In most cases it is an issue in route, usually the third party partner your ISP is using to cut across the US and/or into Canada. Your ISP is actually more likely your best advocate for getting assistance with it--but it will require getting it escalated beyond the help desk people that answer the phone. More likely to get action taken if you can identify the IP's the game is using and forward them to your ISP via email--if you can provide tracerts to them as well (might show where the problems occur) it may help nudge them into taking action.

[Demonchld]

In most cases it is an issue in route, usually the third party partner your ISP is using to cut across the US and/or into Canada. Your ISP is actually more likely your best advocate for getting assistance with it--but it will require getting it escalated beyond the help desk people that answer the phone. More likely to get action taken if you can identify the IP's the game is using and forward them to your ISP via email--if you can provide tracerts to them as well (might show where the problems occur) it may help nudge them into taking action.

thx mate will do

[Raist]

Here's an example to try to illustrate it:

Tracing route to 199.91.189.74 over a maximum of 30 hops

<initial hops removed for security>

  4    22 ms    24 ms    24 ms  xe-7-0-0.chrlncpop-rtr1.southeast.rr.com [24.93.64.42]
  5    29 ms    26 ms    36 ms  bu-ether34.atlngamq46w-bcr00.tbone.rr.com [107.14.19.48]
  6    28 ms    29 ms    29 ms  ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
  7    90 ms    78 ms    77 ms  te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109]
  8    79 ms    79 ms    80 ms  be2052.mpd21.atl01.atlas.cogentco.com [154.54.40.249]
  9    90 ms    89 ms    89 ms  be2168.ccr21.dca01.atlas.cogentco.com [154.54.31.94]
 10    97 ms    95 ms     *     be2150.mpd21.jfk02.atlas.cogentco.com [154.54.31.130]
 11     *      112 ms   111 ms  be2106.ccr21.ymq02.atlas.cogentco.com [154.54.3.50]
 12    70 ms    62 ms    68 ms  38.122.42.34
 13    55 ms    51 ms    50 ms  10.2.2.1
 14    48 ms    51 ms    50 ms  192.34.76.2
 15    49 ms    51 ms    49 ms  199.91.189.234
 16    49 ms    54 ms    48 ms  199.91.189.74

Trace complete.

Notice what is happening at hops 10 and 11. That is an intermittent timeout at those hops. This is happening because they are highly congested and traffic shaping rules are causing certain traffic to be assigned a lower priority, which potentially delays delivery and sometimes causes them to get discarded and retransmitted (this often referred to as throttling, mistakenly assumed to be P2P throttling, but it happens to all kinds of traffic during times of high congestion). This is something that needs to be addressed amongst the service providers--your ISP and the people they have partnered with to carry their traffic when it must go outside of their own segments. The trick is getting them to acknowledge the problem exists and getting them to commit to investigating it further (why submitting a tracert showing potential problems can help your cause).

[Demonchld]

Here's an example to try to illustrate it:

Tracing route to 199.91.189.74 over a maximum of 30 hops

<initial hops removed for security>

  4    22 ms    24 ms    24 ms  xe-7-0-0.chrlncpop-rtr1.southeast.rr.com [24.93.64.42]
  5    29 ms    26 ms    36 ms  bu-ether34.atlngamq46w-bcr00.tbone.rr.com [107.14.19.48]
  6    28 ms    29 ms    29 ms  ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
  7    90 ms    78 ms    77 ms  te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109]
  8    79 ms    79 ms    80 ms  be2052.mpd21.atl01.atlas.cogentco.com [154.54.40.249]
  9    90 ms    89 ms    89 ms  be2168.ccr21.dca01.atlas.cogentco.com [154.54.31.94]
 10    97 ms    95 ms     *     be2150.mpd21.jfk02.atlas.cogentco.com [154.54.31.130]
 11     *      112 ms   111 ms  be2106.ccr21.ymq02.atlas.cogentco.com [154.54.3.50]
 12    70 ms    62 ms    68 ms  38.122.42.34
 13    55 ms    51 ms    50 ms  10.2.2.1
 14    48 ms    51 ms    50 ms  192.34.76.2
 15    49 ms    51 ms    49 ms  199.91.189.234
 16    49 ms    54 ms    48 ms  199.91.189.74

Trace complete.

Notice what is happening at hops 10 and 11. That is an intermittent timeout at those hops. This is happening because they are highly congested and traffic shaping rules are causing certain traffic to be assigned a lower priority, which potentially delays delivery and sometimes causes them to get discarded and retransmitted (this often referred to as throttling, mistakenly assumed to be P2P throttling, but it happens to all kinds of traffic during times of high congestion). This is something that needs to be addressed amongst the service providers--your ISP and the people they have partnered with to carry their traffic when it must go outside of their own segments. The trick is getting them to acknowledge the problem exists and getting them to commit to investigating it further (why submitting a tracert showing potential problems can help your cause).

ok so what do I do how do i do this? im on Diablos server

[Raist]

A lot of how-to's have been posted over the months. Here's one post with a simplifed version:

system specs?

while logged into the game:
start > run > cmd
type "netstat"
look for listing that starts with 199.

in the same cmd window type
tracert 199.xxx.xxx.xxx

do this 4 or 5 times
post results

this will show if anywhere in your connection there is a provider having an issue keeping your data alive

Basically, you need to be able to alt-tab out of XIV and get to your desktop to open a command prompt (DOS Window) by running CMD from your search or run box. From there you run the commands by simply typing them and pressing the <ENTER> key. You can copy all the text from that window into the clipboard for pasting into notepad, email, forums, etc. by right-clicking in the DOS Window and clicking "Select All" to highlight all the text in that window and then pressing the <ENTER> key. Then you can paste it all into something else with the usual paste operations (CTRL-V or right-click and select "Paste", etc.). If you want to clear the screen to get a fresh window again, you can just type the command "CLS" and press <ENTER>. This may help avoid excessive editing. When done, just type the word "exit" and press the <ENTER> key to close the window.

Tracert is a very simple report, but if you are having a lot of trouble it should capture either a * event (time out) at a hop, or at least show very erratic variances in the 3 ping times taken at a hop. A slight variance is normal (like 85-100 range), but if you see a really big jump (like a 50% increase or more on the same hop) then there may be something they need to look at even though it didn't time out with a * on that hop. If you want to provide an even more detailed report, you can use Pathping in place of tracert (pathping 199.91.189.74). This will run 100 pings per hop instead of just 3 in tracert, and also tracks additional data on the quality of traffic when forwarding between hops as well. It can be a bit impractical for just taking a quick look because it takes a while to run (up to 10 minutes depending on the system and the route), but can be very helpful to a technician if they actually commit to opening an investigation.