Latency more than 130ms

[Axgard]

LOL quit your crying, try playing over here in Australia, then you will see what real delay is like.

LOL, do you realize what we all trying to say same thing about troubles while playing not from CA/NA regions? =)

[Iselore]

The 130+ms latency is almost manageable but far from a perfect raiding experience... what's ruining the game for me personally is the 130+ms coupled with the intermittent spike latency and 300ms server side positioning delay.

I'm glad the game is tuned in a way that the mechanics are challenging but when myself and other members of my raid are suffering from lag/dcs and eating AoE's then magically corpse teleporting to the other side of the room because the server just updated their position, it makes me wonder why I bother.

...really not looking forward to PvP with the game the way it is now.

[Yochanan]

I say we all bombard the ask the producer thread and twitter and bomb the hell out of the live twitter feed with pre translated from English to Japanese questions about the lag then maybe we might get some form of acknowledgement even if it is more bullshit about zooming the camera out as if that's ever going to fix the cheap shitty coding se outsourced.......

[Bryson]

I play on Goblin, this is what I get. is there anything I can do, to offset the delay?

1 31.918 ms 15.240 ms 14.225 ms cpe-75-80-208-1.hawaii.res.rr.com (75.80.208.1)

2 8.979 ms 10.065 ms 15.179 ms 24.25.231.225 (24.25.231.225)

3 14.218 ms 13.597 ms 16.094 ms tge0-5-0-7.milnhixd-ccr01.hawaii.rr.com (72.129.46.192)

4 61.223 ms 63.114 ms 63.750 ms agg31.lsancarc01r.socal.rr.com (72.129.45.0)

5 63.142 ms 63.285 ms 67.792 ms bu-ether26.lsancarc0yw-bcr00.tbone.rr.com (66.109.6.212)

6 62.381 ms 59.755 ms 62.907 ms ae-0-0.pr0.lax00.tbone.rr.com (66.109.6.135)

7 75.022 ms 76.375 ms 81.471 ms ix-5-2-1-0.tcore2.LVW-LosAngeles.as6453.net (64.86.252.157)

8 171.498 ms 169.506 ms 174.971 ms if-22-2.tcore2.PDI-PaloAlto.as6453.net (66.198.144.73)

9 166.653 ms 169.979 ms 170.194 ms if-11-3.tcore2.CT8-Chicago.as6453.net (66.198.144.58)

10 172.053 ms 173.600 ms 172.126 ms if-3-2.tcore1.W6C-Montreal.as6453.net (66.198.96.45)

11 176.699 ms 169.904 ms 168.615 ms 66.198.96.50 (66.198.96.50)

12 186.211 ms 206.455 ms 184.535 ms 192.34.76.2 (192.34.76.2)

13 169.017 ms 172.955 ms 174.433 ms 199.91.189.234 (199.91.189.234)

14 189.362 ms 185.332 ms 185.377 ms 199.91.189.26 (199.91.189.26)

[ZohnoReecho]

I play on Goblin, this is what I get. is there anything I can do, to offset the delay?

1 31.918 ms 15.240 ms 14.225 ms cpe-75-80-208-1.hawaii.res.rr.com (75.80.208.1)

2 8.979 ms 10.065 ms 15.179 ms 24.25.231.225 (24.25.231.225)

3 14.218 ms 13.597 ms 16.094 ms tge0-5-0-7.milnhixd-ccr01.hawaii.rr.com (72.129.46.192)

4 61.223 ms 63.114 ms 63.750 ms agg31.lsancarc01r.socal.rr.com (72.129.45.0)

5 63.142 ms 63.285 ms 67.792 ms bu-ether26.lsancarc0yw-bcr00.tbone.rr.com (66.109.6.212)

6 62.381 ms 59.755 ms 62.907 ms ae-0-0.pr0.lax00.tbone.rr.com (66.109.6.135)

7 75.022 ms 76.375 ms 81.471 ms ix-5-2-1-0.tcore2.LVW-LosAngeles.as6453.net (64.86.252.157)

8 171.498 ms 169.506 ms 174.971 ms if-22-2.tcore2.PDI-PaloAlto.as6453.net (66.198.144.73)

9 166.653 ms 169.979 ms 170.194 ms if-11-3.tcore2.CT8-Chicago.as6453.net (66.198.144.58)

10 172.053 ms 173.600 ms 172.126 ms if-3-2.tcore1.W6C-Montreal.as6453.net (66.198.96.45)

11 176.699 ms 169.904 ms 168.615 ms 66.198.96.50 (66.198.96.50)

12 186.211 ms 206.455 ms 184.535 ms 192.34.76.2 (192.34.76.2)

13 169.017 ms 172.955 ms 174.433 ms 199.91.189.234 (199.91.189.234)

14 189.362 ms 185.332 ms 185.377 ms 199.91.189.26 (199.91.189.26)

The problem is the 8th node. There was a thread about people lagging after los angeles node.

[Kallisti]

130ms is fine. If you're getting spikes then ask your ISP to check your routing and fix it.

[Axgard]

130ms is fine. If you're getting spikes then ask your ISP to check your routing and fix it.

Once again, 130 ms is ping to datacenter directly. Game server usually triple it in my case. And ISP can't do anything with routing outside his domain.

[Kallisti]

ISP can't do anything with routing outside his domain.

They can change how they are routing traffic to the server. You need to talk to them, as it has to be your end/the way you are being routed.

[ntall1]

They can change how they are routing traffic to the server. You need to talk to them, as it has to be your end/the way you are being routed.

This is not a practical solution because most ISP's will just ignore you, or you will never really get to speak to anyone who has the power to make these changes. The issues is fully SE's fault for choosing to have all NA/EU servers in the same location. This is a huge noob mistake. Players paying for a service should not have to work so hard to get the service to work properly. Part of ensuring quality service to all customers would have been to open up servers in multiple locations to not only lower ping based on location, but to also deal with these routing issues.

I feel bad for TATA, and Cogneto because their lines would not be so crowded if SE's game traffic didnt all flow thru their lines at the same time due to a crappy server administration department. I am sure the release of FF14 has also caused packet loss for other non related services using these same lines.

[Kallisti]

This is not a practical solution because most ISP's will just ignore you, or you will never really get to speak to anyone who has the power to make these changes.

Then escalate your issue, and if that fails change your ISP. Something is going wrong with the routing if you are getting spikes greater than the actual distance ping to server.