Horrible lag on Balmung the past two evenings.

[Gyson]

I have been having some pretty horrible lag on Balmung (and in the Duty Finder dungeons) the past two nights (October 21st and 22nd). Players, NPCs, and monsters in motion will suddenly stop moving, then suddenly speed up and/or appear in new positions, then suddenly stop moving again, then start, rinse repeat.

Also, abilities/skills that I attempt to activate on my client aren't always responding and have to be pressed several times.

Assuming Balmung's IP address is 199.91.189.30, I think this might be an indication of where the problem rests:

13 49 ms 50 ms 50 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
14 49 ms 49 ms 51 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
15 51 ms 51 ms 51 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
16 66 ms 66 ms * ms 192.34.76.10
17 66 ms * 66 ms 199.91.189.242
18 * 65 ms * 199.91.189.30
19 66 ms 65 ms 67 ms 199.91.189.30


Pinging 199.91.189.30 with 32 bytes of data:
Request timed out.
Reply from 199.91.189.30: bytes=32 time=67ms TTL=234
Request timed out.
Reply from 199.91.189.30: bytes=32 time=66ms TTL=234

Ping statistics for 199.91.189.30:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss)

Can you please look into this? Usually I don't have any latency of note in the game, but this is two days in a row now.

Edit: Balmung's IP appears to be 199.91.189.139. I just wanted to comment and say that this issue is still ongoing (day 4). I know threads here have habit of being marked resolved and closed if updates aren't being given.

====================== PING ======================

Pinging 199.91.189.139 with 32 bytes of data:
Reply from 199.91.189.139: bytes=32 time=65ms TTL=42
Request timed out.
Reply from 199.91.189.139: bytes=32 time=66ms TTL=42
Reply from 199.91.189.139: bytes=32 time=66ms TTL=42

Ping statistics for 199.91.189.139:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

====================== TRACE ======================

13 57 ms 57 ms 56 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
14 56 ms 56 ms 56 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
15 50 ms 54 ms 50 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
16 67 ms 66 ms 67 ms 192.34.76.10
17 * 67 ms 66 ms 199.91.189.242
18 66 ms 65 ms * 199.91.189.139
19 66 ms 66 ms 66 ms 199.91.189.139

Hops prior to #13 are in the 10-25 ms range with no issues.

[Cena]

Same but with Behemoth. Many friends having issues too.

[JedahJohnny]

It's ISP Issue... we must organizate and SE must talk with EU ISP

French Forum has a Sticky Thread where people can post for this problem. ISP (ORANGE,FREE) issue

--> English Forum... No <-- ..:s

http://forum.square-enix.com/ffxiv/t...-et-FAI/page21

[Gyson]

It's ISP Issue... we must organizate and SE must talk with EU ISP

Balmung is a North American server, though.

[Raist]

Going with just the snippet provided it could be an issue with a VLAN again...TWC suspected the same over a year or so back when we were tracking things down. They contacted Ormuco about it and it cleared a couple days later and never saw it come back and I used that same IP for about a year.

Double check there aren't signs of issues in the section of the route you omitted. An issue at hop 3 can show up again at hop 12 and then again at hop 17. The trace is checking each hop in order with each separate ping, so you sort of have to go down the line verifying/correcting the first sign, then the next in the list, and so forth.

Everyone may want to double check the IP you are testing as well. Things got mixed up again with the Chaos move. I used .30 almost exclusively for Migard the last year or more, but am now on .148.

If unsure, you can use the DNS names for the lobbies. Aether is neolobby02.ffxiv.com, Primal is neolobby04.ffxiv.com, and Chaos is neolobby06.ffxiv.com.

[Gyson]

Going with just the snippet provided it could be an issue with a VLAN again...TWC suspected the same over a year or so back when we were tracking things down. They contacted Ormuco about it and it cleared a couple days later and never saw it come back and I used that same IP for about a year.

Double check there aren't signs of issues in the section of the route you omitted. An issue at hop 3 can show up again at hop 12 and then again at hop 17. The trace is checking each hop in order with each separate ping, so you sort of have to go down the line verifying/correcting the first sign, then the next in the list, and so forth.

Everyone may want to double check the IP you are testing as well. Things got mixed up again with the Chaos move. I used .30 almost exclusively for Migard the last year or more, but am now on .148.

If unsure, you can use the DNS names for the lobbies. Aether is neolobby02.ffxiv.com, Primal is neolobby04.ffxiv.com, and Chaos is neolobby06.ffxiv.com.

The hops (1-12) prior to the ones listed in the original post are all in the 10-20 ms range and showed no issues throughout the repeated trace tests that I ran.

Also, as far as I've been able to tell, it gets worse during North America prime-time (evening) hours.

"neolobby02.ffxiv.com" (Aether) is taking the same route as the IP I'm using for Balmung, save for a difference in the last hop (199.91.189.74 vs 199.91.189.30). Having said that, in either case the problem never seems to show up on the last hop, but rather the three hops prior to it.

[Raist]

Curious if .30 still being used for world service. Last time we saw them change up things like this people were reporting timeouts to the address they thought they were using, only to find they were no longer valid and were actually using a different one that was responding better when tested. Arrstatus was still showing them as in use and within about a week they went completely unresponsive to pings...but the site still showed them as in use. To this day it still shows 4 or 5 worlds as being on .57, which was one of the ones that went "dark" back in April.

Just saying...if you haven't verified it yet, might want to pull up resmon or netstat to confirm what you actually connect to before filing any formal ticket...won't get far if testers start testing a dead link.

[Risvertasashi]

As others have said, this is an ISP issue; not an issue with Square. You can use WinMTR to get a better diagnosis of how each node between you and the server is performing. A VPN may help you (it helps in my case a lot), especially during those peak hours of internet traffic.

[Raist]

Just did some poking around with a looking glass and histories were showing some shifts in metrics for level3 routes to Ormuco. Apparently someone somewhere has picked up on some issues through their vectors. Some were still putting level3 ahead if others, but seeing them get pushed to 200+ while tata is dropping below 70. Saw one from Kansas that completely flipped--Tata was assigned 15 and level3 was saddled with 443, while cogent stayed at 125.

So it looks like some areas are sort of "retraining" this week. Hopefully it sorts out better soon. It may be worth triggering a lease renewal or at least a hard modem reboot this weekend if it doesn't clear up. Who knows...you might get lucky and get gated differently at the headend, depending on just how much things are changing. Works sometimes with TWC at least.

[Gyson]

Looks like Balmung's IP is 199.91.189.139 - however hoops 13 and beyond are all still the same as those listed in the original post (save for the last hop, obviously).

As others have said, this is an ISP issue; not an issue with Square.

I really don't understand this type of response. I can, in no way, exert any influence upon Ormuco-Comm to fix this. Square, however, can (since apparently that's the provider they're using - Balmung's IP is owned by Ormuco-Comm, as are the IP addresses that are dropping packets). Blizzard has been known to step in on cases like this in an attempt to resolve persistent latency problems for its subscribers. Why should I expect any less from Square?

Actually, in the past when FFXIV players have attempted to bring the issue up with Ormuco directly, the ISP turned around and opened a ticket with Square while citing the problem was on their end. These two businesses need to get together and fix this. All I can do is report how miserable it's been making my FFXIV experience this week while forking over my monthly sub - that's my job, now it's time for them to do theirs.