Constant Lag Spikes

I was running everything smoothly, got down HM Titan with only me and one other healer, then Square announces their God-forsaken maintenance on 9/18 and ever since that I have been lagging, and so have several others, to the point where we can't even decently get HM Titan down, even with a group of 3 healers so I can slack off a bit. When the lead calls out stuff in voice chat, I find myself popping sprint all the time and just strafing all the time until the lag spike passes and I see the aoes have passed, praying I didn't get hit. I understand something like this (them breaking something) will take a while to fix, but it doesn't help when today they shut down the NA / EU servers randomly, then put them back up a few minutes later, and the server announces that it will be taken down for scheduled maintenance (which it never went down, kept playing with everybody and no such thing happened) and then went on the website to find there was no scheduled maintenance for NA / EU servers, but only for the JP group.

This game is purely unenjoyable now.

I started experiencing this horrible lag today I'm Australian playing on saragantas nothing to do with my end

I got it today as well. Everyone stops moving in town all at the same time, then just runs away at the speed of sound.

Very frustrating.

I guess I spoke too soon when I said it had improved. The lag fest and d/cing has started again. :mad:

It seems a large ammount of us are in Australia.

as of this morning when i woke up i've been having the exact same issues

Quote:

---

It seems a large ammount of us are in Australia.

---

im wondering if those of us are in aus are perhaps using the same ISP?
im with Vivid


hopefully we get an aswer and get to the bottom of this

Quote:

---

Originally Posted by BrendohxD

as of this morning when i woke up i've been having the exact same issues





hopefully we get an aswer and get to the bottom of this

---

Nah I'm on Telstra, already contacted, not throttling on their end.
This will be square enix's fault, but they will ignore it for as long as possible because they are just terrible at technical support or customer support.

I'm getting this now too. The problem didn't exist for me at all until last night after the maintenance. I really hope it gets fixed soon because the game has basically become unplayable for me.

Location: California (Southern)
ISP: Time Warner
Server: Balmung

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Windows\system32>ping 184.107.107.176

Pinging 184.107.107.176 with 32 bytes of data:
Reply from 184.107.107.176: bytes=32 time=444ms TTL=49
Reply from 184.107.107.176: bytes=32 time=430ms TTL=49
Reply from 184.107.107.176: bytes=32 time=442ms TTL=49
Reply from 184.107.107.176: bytes=32 time=423ms TTL=50

Ping statistics for 184.107.107.176:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 423ms, Maximum = 444ms, Average = 434ms

C:\Windows\system32>tracert 184.107.107.176

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 1 ms 2 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 134 ms 122 ms 108 ms 10.112.0.49
4 74 ms 74 ms 93 ms 10.112.0.254
5 63 ms 123 ms 123 ms 119.225.139.57
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 148 ms 123 ms 113 ms 59.154.57.12
10 109 ms 108 ms 108 ms 61.88.241.109
11 254 ms 318 ms 274 ms 203.208.192.41
12 396 ms 379 ms 378 ms 203.208.153.46
13 327 ms 335 ms 278 ms be2020.ccr22.lax01.atlas.cogentco.com [154.54.88
.17]
14 330 ms 469 ms 425 ms be2066.ccr22.iah01.atlas.cogentco.com [154.54.7.
53]
15 540 ms 423 ms 444 ms be2147.ccr22.dfw01.atlas.cogentco.com [154.54.27
.18]
16 409 ms 324 ms 319 ms be2010.ccr22.mci01.atlas.cogentco.com [154.54.46
.217]
17 339 ms 343 ms 359 ms te0-4-0-3.ccr22.ord01.atlas.cogentco.com [66.28.
4.34]
18 405 ms 399 ms 419 ms be2080.ccr22.yyz02.atlas.cogentco.com [154.54.42
.6]
19 394 ms 383 ms 404 ms te7-1.mag02.yyz02.atlas.cogentco.com [154.54.40.
166]
20 395 ms 389 ms 448 ms te4-1.ccr01.yyz03.atlas.cogentco.com [154.54.45.
118]
21 354 ms 354 ms 439 ms 38.122.70.182
22 424 ms 368 ms 374 ms te8-2.cr1.mtl.iweb.com [67.205.127.121]
23 360 ms 388 ms 398 ms te7-4.dr9.mtl.iweb.com [184.107.1.110]
24 394 ms 408 ms 379 ms 72.55.128.44
25 382 ms 411 ms 394 ms 184.107.107.176

Trace complete.

Brendoh, since your spiking after your internal network, it's most likely the cause of your ISP (not SE).
On hop 3, your ping is spiking and continues throughout your route. I would contact your ISP to inquire about it.