Yesterday I had 2 "unable to join lobby" error
Printable View
Yesterday I had 2 "unable to join lobby" error
Use the official forum feedback thread to report your ping changes.
Answer the questions and be constructive.
http://forum.square-enix.com/ffxiv/t...ter-Relocation
Wow, what's going on with this? Mine's going through NTT in asbnva02 (second line 4) as well, but it gains about 20 pings while within Ashburn, VA and another 50+ when jumping to San Jose, CA. I have comcast tho.
Also, what causes the index numbers (first column) to get mixed around like that?
I'm from SEA, and high latency isn't new to me, but I used to play around 180ms and now I'm averaging 210ms, which has significant difference.
it seems once you hit 200+ms the lag is much more noticeable. I think my ISP (PLDT) is also the culprit, as it has an infamous reputation in my country, but I hope there's an alternative I could use before I resort to paying for VPN.
https://puu.sh/w2FlG.PNG
I could of course, transfer to the JP servers, but other than the cost, I can't just leave my current FC like that.
right now I've not touched the dungeons because I'm getting DC'd, just waiting until SB launch to see if anything changes.
any advice? thanks.
Dear mods
Can we have an update as to how things are going or what it's getting done to fix people's issues?
Thanks
The game feels so much better now. It's like I'm right there next to the datacenter.
http://i.imgur.com/DHmHaV7.png
Time to chime in:
neolobby4:
Reply from 204.2.229.10: bytes=32 time=30ms TTL=55
Quote:
Tracing route to neolobby04.ffxiv.com [204.2.229.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms *
2 15 ms 14 ms 5 ms *
3 8 ms 7 ms 8 ms 154.11.10.11
4 8 ms 8 ms 8 ms 10-1-2.ear3.Seattle1.Level3.net [4.16.169.73]
5 10 ms 8 ms 8 ms ae-1.r05.sttlwa01.us.bb.gin.ntt.net [129.250.8.217]
6 9 ms 9 ms 9 ms ae-1.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.88]
7 27 ms 26 ms 27 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
8 30 ms 30 ms 30 ms ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
9 30 ms 30 ms 30 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
10 35 ms 30 ms 30 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
11 30 ms 30 ms 30 ms 204.2.229.234
12 30 ms 30 ms 30 ms 204.2.229.10
neolobby2:
Reply from 204.2.229.9: bytes=32 time=32ms TTL=55
So Vancouver, Seattle (level 3), Seattle (ntt), Seattle (ntt), San Jose (ntt), San Jose (ntt), Sacramento (ntt), Sacramento (ntt)Quote:
Tracing route to neolobby02.ffxiv.com [204.2.229.9]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms *
2 63 ms 5 ms 5 ms *
3 8 ms 7 ms 7 ms ae0.100.STTLWAWBGR80.bb.telus.com [154.11.10.9]
4 8 ms 8 ms 8 ms 10-1-2.ear3.Seattle1.Level3.net [4.16.169.73]
5 9 ms 8 ms 8 ms ae-1.r05.sttlwa01.us.bb.gin.ntt.net [129.250.8.217]
6 8 ms 8 ms 8 ms ae-1.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.88]
7 28 ms 28 ms 28 ms ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
8 32 ms 32 ms 32 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
9 32 ms 32 ms 32 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
10 32 ms 32 ms 32 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
11 * 32 ms 32 ms 204.2.229.234
12 32 ms 31 ms 31 ms 204.2.229.9
Note that pinging the gateway is not representative of your game ping time. For that you need to trace the server ip.
In fact if I trace the ip address to Primal listed on arrstatus.com
It still shows the route going to Montreal. Which makes me wonder if the ip address is still the same or not.Quote:
Tracing route to 199.91.189.93 over a maximum of 30 hops
1 <1 ms 1 ms <1 ms *
2 5 ms 10 ms 18 ms *
3 8 ms 7 ms 8 ms 154.11.10.11
4 * 8 ms 7 ms 10-1-2.ear3.Seattle1.Level3.net [4.16.169.73]
5 * 78 ms 78 ms ae-1-11.bear1.Montreal2.Level3.net [4.69.203.133]
6 79 ms 79 ms 79 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
7 * * * Request timed out.
8 74 ms 88 ms 74 ms 192.34.76.2
9 75 ms 75 ms 74 ms 199.91.189.234
10 * * * Request timed out.
11 * * * Request timed out.
12 ^C
The gateway ip addresses are pretty much consistant with other stuff I've accessed in California, however perhaps Square-Enix can turn on IPv6?
Also point of interest, if you've "turned off nagle" at the OS level, you would notice the difference between 30 and 100ms quite noticably. If you never turned off nagle, then your PC is quite literately framing everything in 200ms intervals, and thus only if you had more than 200ms RTT would you notice it.
Most MMORPG players that I know, know better than to tamper with their network card settings or the cable/dsl modem settings.
If you have CABLE and it's not channel bonded, you should be able to get 30-70ms (due to RF noise,) Channel bonding on cable occurs at settings over 30Mbps. If you have DSL and it's not channel bonded you should be able to get 8-40ms (unless you have FM radio interference) before it leaves your state in the trace routes. There is no excuse for an increase of more than 40ms. If you have fiber, you should not have a ping time worse than 10ms realisticly, depends if you are in California or in a city with a carrier hotel. eg, if you're 300 miles away from the capital or largest city in your state, then yeah you might be hard pressed to get below 70.
If you have channel bonded cable or DSL, then you will likely be unable to get sub-70ms due to the nature of channel bonding favoring bandwidth over latency. If this is something you feel is important ask your ISP about switching to fiber, or downgrading from a channel bonded package.
Channel-bonding on cable tends to be a bit less painful, but at the same time it's also extremely difficult to get low-latency on cable because of it, and Cable ISP's are reluctant to upgrade hardware in areas that aren't congested. DSL can force channel bonding off by unplugging the second phone line.
This is a similar problem with Korean games in Korea. The games run fine at their sub-10ms latency, but when the games finally get localized for North America, latency makes the games so much more terrible, and PvP'ers who live in California end up ruling the server.
With FFXIV V1.0 all the servers were in Japan, with V2.0 North America's servers were actually in Montreal (and so were Europe's at the time.)
So no, FFXIV V2.0 was intentionally designed with the awful non-fiber internet of North America.