Yeah I have never had lag before and I am getting crazy spikes right now. Really messing with my Titan runs. Seems to be on multiple if not all NA/EU servers.
Yeah I have never had lag before and I am getting crazy spikes right now. Really messing with my Titan runs. Seems to be on multiple if not all NA/EU servers.
Nazura Azure
Excalibur
The Vanguard - http://ffxiv-thevanguard.enjin.com/
Twitch: http://www.twitch.tv/azure1354
Having that same problem with Titan tonight. Normally I do very well with dodging Titan's attacks but tonight, I'm having too much problem with this. one of our party member said that everything keeps skipping.
Suirieko Mizukoshi ofExcaliburLamia
On DSL internet and having this problem
These lag spikes are horrendous.
I'm on Comcast, and I know a lot of others have been seeing issues with other ISPs. I also have some other folks in my FC who haven't had issues, which is partially why I'm leaning towards a path issue from the NA server cluster to a whole lot of people.
My toon is on Hyperion, which appears to be an ip of 199.91.189.23. Whois says it was owned by Eidos, which was bought by Square-Enix.
Tracing out to that shows the outbound going from Comcast to Cogent (using winmtr, I'm seeing large spikes later in the path; pings of 400-500ms) to iweb to SE.
3 6 ms 8 ms 8 ms xe-2-0-1-0-ar01.bearcreek.tx.houston.comcast.net [68.85.87.165]
4 15 ms 15 ms 17 ms 68.86.94.121
5 16 ms 15 ms 16 ms pos-0-0-0-0-pe01.1950stemmons.tx.ibone.comcast.net [68.86.86.90]
6 51 ms 53 ms 55 ms 173-167-56-166-static.hfc.comcastbusiness.net [173.167.56.166]
7 55 ms 54 ms 53 ms be2031.ccr21.dfw01.atlas.cogentco.com [154.54.7.45]
8 63 ms 68 ms 66 ms be2141.mpd22.mci01.atlas.cogentco.com [154.54.5.157]
9 83 ms 77 ms 82 ms te0-7-0-1.mpd22.ord01.atlas.cogentco.com [154.54.25.78]
10 105 ms 107 ms 105 ms be2082.ccr22.yyz02.atlas.cogentco.com [154.54.28.10]
11 107 ms 107 ms 107 ms be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30.206]
12 108 ms 111 ms 109 ms 38.122.42.34
13 * * * Request timed out.
14 58 ms 59 ms 59 ms 192.34.76.2
15 69 ms 68 ms 69 ms 199.91.189.234
16 59 ms 60 ms 59 ms 199.91.189.23
Trace complete.
Tracing back to myself on iweb's looking glass, I'm seeing a pretty hefty spike on that first hop from iweb to level3, but then it clears up.
1 67.205.86.106 (67.205.86.106) 0.529 ms 0.619 ms 0.652 ms
2 te-9-3.cr3.mtl.iweb.com (67.205.127.213) 0.745 ms 0.837 ms 0.879 ms
3 po21.cr4.mtl.iweb.com (67.205.127.145) 13.552 ms 13.596 ms 13.688 ms
4 te-8-2.car1.Montreal2.Level3.net (4.59.176.9) 92.705 ms 92.746 ms 92.838 ms
5 ae-5-5.ebr2.NewYork1.Level3.net (4.69.141.6) 8.217 ms 8.260 ms 8.303 ms
6 ae-46-46.ebr2.NewYork2.Level3.net (4.69.201.30) 8.446 ms 8.335 ms 4.69.201.38 (4.69.201.38) 8.249 ms
7 ae-2-52.edge1.NewYork2.Level3.net (4.69.138.226) 8.252 ms 8.243 ms 8.233 ms
8 COMCAST-IP.edge1.NewYork2.Level3.net (4.71.186.6) 21.399 ms COMCAST-IP.edge1.NewYork2.Level3.net (4.71.186.14) 21.691 ms COMCAST-IP.edge1.NewYork2.Level3.net (4.71.186.34) 25.329 ms
9 he-4-11-0-0-cr01.ashburn.va.ibone.comcast.net (68.86.85.13) 26.619 ms 30.607 ms 26.430 ms
10 he-4-5-0-0-cr01.56marietta.ga.ibone.comcast.net (68.86.89.158) 41.081 ms 41.082 ms 41.073 ms
11 68.86.91.234 (68.86.91.234) 58.668 ms 58.262 ms 61.450 ms
From Level3's looking glass in Montreal back to me, that's a pretty hefty ping.
1 ae-5-5.ebr2.NewYork1.Level3.net (4.69.141.6) 208 msec 144 msec 364 msec
2 ae-46-46.ebr2.NewYork2.Level3.net (4.69.201.30) 180 msec
ae-45-45.ebr2.NewYork2.Level3.net (4.69.141.22) 172 msec
4.69.201.38 204 msec
3 ae-2-52.edge1.NewYork2.Level3.net (4.69.138.226) 204 msec 204 msec 208 msec
4 COMCAST-IP.edge1.NewYork2.Level3.net (4.71.186.46) 84 msec 28 msec 28 msec
5 he-4-10-0-0-cr01.ashburn.va.ibone.comcast.net (68.86.85.9) [AS7922 {COMCAST-IBONE}] 32 msec 36 msec 32 msec
6 he-4-2-0-0-cr01.56marietta.ga.ibone.comcast.net (68.86.89.146) [AS7922 {COMCAST-IBONE}] 48 msec 48 msec 48 msec
7 68.86.94.134 [AS7922 {COMCAST-IBONE}] 64 msec 64 msec 64 msec
It kind of looks like something with the Level3 <> iweb connection, or possibly just with Level3. Could be something, could be nothing. But it definitely would be good for someone at SE to reach out to their peering provider to troubleshoot with the tier 1 peers.
Yes the lag is bad. I had to drop out of a duty finder group because I could not properly heal. Characters would freeze for over 20 seconds. Time that is too crucial in a boss fight.
Same here, was running fine until I ran Ifrit with my FC. Now I have constant lag spikes every few seconds..It started about 1hour ago for me on Hyperion
I am having the same kind of lag.
Never had this issue before.
I've had LS members complain about this issue since day one and I never experienced it myself -- until tonight. Makes a fun and fairly straightforward fight like Ifrit pretty difficult with the whole raid freezing and rubberbanding every few seconds. My internet connection is completely fine at the moment but the game is nearly unplayable. I have pretty constant lag spikes where things freeze up for a second and every now and then I experience freezes for up to 5 seconds or so. I feel terrible for folks that are having this issue all the time...
Its super bad right now, just got 90000 error twice
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.