Fix The Lag For Hawaii Or Im Out

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

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.

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

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.

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

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.

Quote:

Originally Posted by 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.

thx mate will do

Here's an example to try to illustrate it:

Code:

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).

Quote:

Originally Posted by Raist

Here's an example to try to illustrate it:

Code:

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

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

Quote:

Originally Posted by ninesunz

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.

Core i7 4500
8GB Ram
Geforce 745M 2GB Dedicated
Windows 8.1 Full Updates
5200 RPM 1 TB HD

Oceanic Time Warner Cable 35 down 5 up

HTML Code:

Microsoft Windows [Version 6.3.9600] (c) 2013 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>netstat Active Connections Proto Local Address Foreign Address State TCP 127.0.0.1:5354 Asus:53774 ESTABLISHED TCP 127.0.0.1:5354 Asus:53775 ESTABLISHED TCP 127.0.0.1:5939 Asus:53915 ESTABLISHED TCP 127.0.0.1:27015 Asus:53833 ESTABLISHED TCP 127.0.0.1:53774 Asus:5354 ESTABLISHED TCP 127.0.0.1:53775 Asus:5354 ESTABLISHED TCP 127.0.0.1:53833 Asus:27015 ESTABLISHED TCP 127.0.0.1:53913 Asus:53914 ESTABLISHED TCP 127.0.0.1:53914 Asus:53913 ESTABLISHED TCP 127.0.0.1:53915 Asus:5939 ESTABLISHED TCP 192.168.1.2:61798 69.90.201.9:7710 ESTABLISHED TCP 192.168.1.2:61803 server22405:5938 ESTABLISHED TCP 192.168.1.2:61808 bn1wns2011604:https ESTABLISHED TCP 192.168.1.2:61961 lax02s19-in-f22:https ESTABLISHED TCP 192.168.1.2:62001 199.91.189.42:55006 ESTABLISHED TCP 192.168.1.2:62002 199.91.189.42:55006 ESTABLISHED TCP 192.168.1.2:62008 a96-7-48-43:http ESTABLISHED TCP 192.168.1.2:62018 lax17s02-in-f7:https SYN_SENT TCP 192.168.1.2:62019 lax17s02-in-f7:https ESTABLISHED TCP 192.168.1.2:62020 lax17s02-in-f7:https SYN_SENT C:\WINDOWS\system32>tracert 199.91.189.42 Tracing route to 199.91.189.42 over a maximum of 30 hops 1 2 ms 50 ms 9 ms 192.168.1.1 2 5 ms 6 ms 39 ms 192.168.0.1 3 42 ms 37 ms 27 ms cpe-98-150-240-1.hawaii.res.rr.com [98.150.240.1 ] 4 20 ms 23 ms 21 ms tge7-2.hnllhiku-cer02.hawaii.rr.com [24.25.232.6 1] 5 17 ms 34 ms 18 ms tge0-6-0-3.hnllhiik01r.hawaii.rr.com [72.129.47. 40] 6 18 ms 19 ms 55 ms agg21.milnhixd01r.hawaii.rr.com [72.129.45.42] 7 71 ms 66 ms 77 ms agg31.lsancarc01r.socal.rr.com [72.129.45.0] 8 69 ms 70 ms 78 ms bu-ether16.lsancarc0yw-bcr00.tbone.rr.com [66.10 9.6.102] 9 68 ms 90 ms 69 ms 107.14.19.138 10 104 ms 81 ms 80 ms 66.109.9.122 11 142 ms 161 ms 141 ms vlan70.csw2.LosAngeles1.Level3.net [4.69.144.126 ] 12 183 ms 181 ms 221 ms ae-72-72.ebr2.LosAngeles1.Level3.net [4.69.137.2 1] 13 158 ms 218 ms 386 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78] 14 203 ms 222 ms * ae-83-83.csw3.Dallas1.Level3.net [4.69.151.157] 15 143 ms 156 ms 144 ms ae-81-81.ebr1.Dallas1.Level3.net [4.69.151.150] 16 136 ms 140 ms 138 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117] 17 171 ms 143 ms 149 ms ae-5-5.ebr2.Chicago1.Level3.net [4.69.140.193] 18 146 ms 147 ms 150 ms ae-1-100.ebr1.Chicago1.Level3.net [4.69.151.177] 19 144 ms 139 ms 142 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86] 20 159 ms 140 ms 147 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 21 176 ms 178 ms 208 ms 10.2.2.1 22 162 ms 158 ms 161 ms 192.34.76.2 23 195 ms 251 ms 177 ms 199.91.189.234 24 179 ms 175 ms 178 ms 199.91.189.42 Trace complete.

C:\WINDOWS\system32>

Have you tried pingzaper? Our FC is a Hawaii based core so a lot of us play in HST. We started using pingzaper when one of our members suggested it. IMHO it has helped out a lot.

Quote:

Originally Posted by 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.

Not true, I play from Europe and have no problems at all, stop exaggerating simply to hate on SE.

I am not sure KraggyKor...

If I play with my PS3 with an 5400rpm HD then i have terrible problems.
As soon as i switch to another PS3 with an 7200rpm HD everything runs better.

Its just... the PS3 originally uses an 5400rpm HD so...

Quote:

Originally Posted by Abunailakshmi

Have you tried pingzaper? Our FC is a Hawaii based core so a lot of us play in HST. We started using pingzaper when one of our members suggested it. IMHO it has helped out a lot.

I'll check it out tho I don't wanna pay another fee for playing this game thanks

That's a pretty terrible route you're taking to get to Montreal. Hawaii > LA > Dallas > Chicago. Not within your control of course, but there's obviously a problem after the LA > Dallas jump.

Quote:

Originally Posted by Orophin

That's a pretty terrible route you're taking to get to Montreal. Hawaii > LA > Dallas > Chicago. Not within your control of course, but there's obviously a problem after the LA > Dallas jump.

Ya this is so stupid route which is sure the reason I have such terrible lag over here. Tho if I go any play on the Japan side I have no lag at all but I really like the FC I'm in now as they have been helping me learn the game a lot >< come on square Enix fix this issue I know 15$ a month loss is nothing to you but wouldn't u rather have 15$ then 0$?

Make the game more stable instead of giving us more content just cause the game works fine in Japan doesn't mean the rest of the world is fine.

Quote:

Originally Posted by Demonchld

Ya this is so stupid route which is sure the reason I have such terrible lag over here. Tho if I go any play on the Japan side I have no lag at all but I really like the FC I'm in now as they have been helping me learn the game a lot >< come on square Enix fix this issue I know 15$ a month loss is nothing to you but wouldn't u rather have 15$ then 0$?

Make the game more stable instead of giving us more content just cause the game works fine in Japan doesn't mean the rest of the world is fine.

That's just it though... SE has no control over who your ISP uses as a routing partner. Mostly why they tell people to contact their ISP first. I'm with TWC also, and depending on which corridor TWC has put me on while they've been working on this the last 10 weeks or so, I've been dealing with mostly either Cogent or TATA as my routing partner. SE didn't make those choices--Time Warner Cable did.

No Final Fantasy in Paradise Brah
https://encrypted-tbn3.gstatic.com/i...Y0dTAwN3BZ_DEQ

PHP Code:

going to run a test over my t mobile connection via iPhone tether and my god its way worse lol they still go thru so many servers to get to the main one [HTML]TWC Tracing route to 199.91.189.74 over a maximum of 30 hops 1 8 ms 6 ms 8 ms 192.168.1.1 2 5 ms 4 ms 21 ms 192.168.0.1 3 46 ms 32 ms 29 ms cpe-98-150-240-1.hawaii.res.rr.com [98.150.240.1 ] 4 20 ms 14 ms 20 ms tge7-2.hnllhiku-cer02.hawaii.rr.com [24.25.232.6 1] 5 23 ms 17 ms 16 ms tge0-6-0-2.hnllhiik01r.hawaii.rr.com [72.129.47. 38] 6 24 ms 29 ms 37 ms agg21.milnhixd01r.hawaii.rr.com [72.129.45.42] 7 68 ms 68 ms 65 ms agg31.lsancarc01r.socal.rr.com [72.129.45.0] 8 78 ms 71 ms 75 ms bu-ether16.lsancarc0yw-bcr00.tbone.rr.com [66.10 9.6.102] 9 74 ms 68 ms 73 ms 107.14.19.138 10 84 ms 82 ms 84 ms 66.109.9.122 11 142 ms 143 ms 145 ms vlan60.csw1.LosAngeles1.Level3.net [4.69.144.62] 12 141 ms 144 ms 144 ms ae-62-62.ebr2.LosAngeles1.Level3.net [4.69.137.1 7] 13 148 ms 150 ms 153 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78] 14 150 ms 155 ms 154 ms ae-93-93.csw4.Dallas1.Level3.net [4.69.151.169] 15 152 ms 147 ms 140 ms ae-91-91.ebr1.Dallas1.Level3.net [4.69.151.162] 16 157 ms 139 ms 143 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117] 17 143 ms 146 ms 146 ms ae-5-5.ebr2.Chicago1.Level3.net [4.69.140.193] 18 149 ms 158 ms 155 ms ae-1-100.ebr1.Chicago1.Level3.net [4.69.151.177] 19 141 ms 142 ms 143 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86] 20 150 ms 144 ms 147 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 21 174 ms 180 ms 175 ms 10.2.2.1 22 * 164 ms 157 ms 192.34.76.2 23 172 ms 173 ms 173 ms 199.91.189.234 24 248 ms * 216 ms 199.91.189.74 Trace complete. T-Mobile Tracing route to 199.91.189.42 over a maximum of 30 hops 1 3 ms 3 ms 3 ms 172.20.10.1 2 93 ms 84 ms 85 ms 10.170.208.48 3 156 ms 76 ms 82 ms 10.170.208.137 4 116 ms 80 ms 89 ms 10.162.130.68 5 238 ms 75 ms 79 ms 10.162.130.89 6 106 ms * 145 ms 10.170.208.6 7 170 ms 95 ms 74 ms 10.170.208.10 8 144 ms 77 ms 90 ms 10.177.18.37 9 84 ms 84 ms 87 ms 10.177.24.206 10 103 ms 153 ms 82 ms xe-8-0-0.bar1.Tustin1.Level3.net [4.53.180.25] 11 213 ms 160 ms 218 ms vl-3501-ve-115.ebr1.Tustin1.Level3.net [4.69.158 .65] 12 224 ms 155 ms 286 ms ae-6-6.ebr1.LosAngeles1.Level3.net [4.69.153.221 ] 13 282 ms 190 ms 157 ms ae-61-61.csw1.LosAngeles1.Level3.net [4.69.137.2 ] 14 272 ms 194 ms 157 ms ae-62-62.ebr2.LosAngeles1.Level3.net [4.69.137.1 7] 15 165 ms 381 ms 157 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78] 16 433 ms 194 ms 157 ms ae-73-73.csw2.Dallas1.Level3.net [4.69.151.145] 17 537 ms 195 ms 158 ms ae-71-71.ebr1.Dallas1.Level3.net [4.69.151.138] 18 253 ms 177 ms 222 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117] 19 534 ms 194 ms 157 ms ae-5-5.ebr2.Chicago1.Level3.net [4.69.140.193] 20 223 ms 158 ms 160 ms ae-1-100.ebr1.Chicago1.Level3.net [4.69.151.177] 21 280 ms 320 ms * ae-10-10.car2.Montreal2.Level3.net [4.69.153.86] 22 280 ms 315 ms 204 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 23 581 ms 166 ms 150 ms 10.2.2.1 24 343 ms 168 ms 156 ms 192.34.76.2 25 588 ms 202 ms 207 ms 199.91.189.234 26 193 ms 155 ms 156 ms 199.91.189.42 Trace complete. C:\Users\Josh

programs like battleping help a good bit with players away from the server location.

Ya with pingzaper I got straight to Chicago then canada. Just bypass the other routes. There is a post on here with our member Desolo explaining how to do it. All of us in DmP who live in Hawaii use it and have no complaints.

Quote:

Originally Posted by 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

Quote:

Originally Posted by Demonchld

Ya this is so stupid route which is sure the reason I have such terrible lag over here. Tho if I go any play on the Japan side I have no lag at all but I really like the FC I'm in now as they have been helping me learn the game a lot >< come on square Enix fix this issue I know 15$ a month loss is nothing to you but wouldn't u rather have 15$ then 0$?

Make the game more stable instead of giving us more content just cause the game works fine in Japan doesn't mean the rest of the world is fine.

What, exactly, is it that you expect SE to do about your ISPs poor routing? SE doesn't control your Internet connection. They have zero control over the route you take.

You're barking up the wrong tree.

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.

- Furlamseere