Unbearable server lag since yesterday

[Eumen]

Aaaand it's back for night #3.

[Xbob42]

Aaaand it's back for night #3.

Yup. Just came back like 45 minutes ago. There goes the rest of my FFXIV time.

[Alcaine]

Xfinity user from Ultros here. I quit out last night it was so bad, and it's happening again today.

[icy_]

happening to me too, I want to say Square Enix is doing something to their servers, because all is fine until like 10pm EST, which iirc is near start of workday over in Japan?
For the last three days the lags have been starting around this time until it's magically fine again next morning. So I suspect SE doing something o.O

[eaudaemon]

coming back to say that Lag is still active in the game

[DiviDevout]

I have been having these issues for a while now outside of FFXIV with Comcast. This usually starts around 6-8PM PDT, and ends 2-4AM PDT.

However, recently, it has been happening in FFXIV a lot more.

I don't think its a FFXIV only issue, but routing centers along the way to the server.

Here are a couple tracerts:


1 3 ms <1 ms <1 ms (Removed)
2 8 ms 8 ms 7 ms (Removed)
3 10 ms 7 ms 8 ms (Removed)
4 8 ms 8 ms 7 ms (Removed)
5 23 ms 21 ms 23 ms be-36942-cs04.losangeles.ca.ibone.comcast.net [96.110.45.141]
6 19 ms 18 ms 19 ms be-2401-pe01.losangeles.ca.ibone.comcast.net [96.110.44.110]
7 25 ms 23 ms 18 ms 50.242.151.62
8 31 ms 28 ms 28 ms ae-11.r25.lsanca07.us.bb.gin.ntt.net [129.250.2.187]
9 34 ms 28 ms 27 ms ae-3.r24.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
10 * 58 ms * ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
11 57 ms 64 ms 62 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
12 64 ms 61 ms * 204.2.229.234
13 * 56 ms 58 ms 204.2.229.9

----

1 <1 ms <1 ms <1 ms (Removed)
2 7 ms 7 ms 7 ms (Removed)
3 8 ms 7 ms 7 ms (Removed)
4 8 ms 8 ms 9 ms (Removed)
5 20 ms 19 ms 19 ms be-36942-cs04.losangeles.ca.ibone.comcast.net [96.110.45.141]
6 39 ms 95 ms 94 ms be-2401-pe01.losangeles.ca.ibone.comcast.net [96.110.44.110]
7 18 ms 25 ms 20 ms 50.242.151.62
8 * 28 ms 27 ms ae-11.r25.lsanca07.us.bb.gin.ntt.net [129.250.2.187]
9 28 ms 27 ms 28 ms ae-3.r24.snjsca04.us.bb.gin.ntt.net [129.250.4.150]
10 195 ms * 57 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
11 62 ms 66 ms 62 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
12 54 ms * * 204.2.229.234
13 59 ms 64 ms 62 ms 204.2.229.9

Anyway, this affects more than just FFXIV for me, as other data that gets sent through these routing hubs probably has the same problems. However, I am receiving a lot more 90K errors the last two days.

Anyway, hope for a fix soon! Will also contact Comcast.

[NinuSkeith]

Been having issues since Monday. Sargatanas and Xfinity. Can barely get through Main Scenario roulette, nevermind something challenging. Sample tracerts:

1 <1 ms <1 ms <1 ms x
2 9 ms 8 ms 8 ms x
3 8 ms 9 ms 8 ms x
4 9 ms 16 ms 9 ms x
5 12 ms 11 ms 11 ms be-298-ar01.santaclara.ca.sfba.comcast.net [162.151.86.57]
6 12 ms 11 ms 11 ms be-36331-cs03.sunnyvale.ca.ibone.comcast.net [96.110.41.73]
7 11 ms 11 ms 11 ms be-1312-cr12.sunnyvale.ca.ibone.comcast.net [96.110.46.30]
8 12 ms 13 ms 15 ms be-302-cr01.9greatoaks.ca.ibone.comcast.net [96.110.37.174]
9 11 ms 12 ms 12 ms be-2212-pe12.9greatoaks.ca.ibone.comcast.net [96.110.33.38]
10 42 ms 42 ms 42 ms 50.208.234.10
11 13 ms 13 ms 12 ms ae-11.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.120]
12 * 46 ms 46 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
13 46 ms 45 ms 45 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
14 49 ms 46 ms 46 ms 204.2.229.234
15 45 ms 48 ms 45 ms 204.2.229.9

1 <1 ms <1 ms <1 ms x
2 8 ms 8 ms 10 ms x
3 10 ms 9 ms 11 ms x
4 9 ms 17 ms 8 ms x
5 11 ms 12 ms 11 ms be-298-ar01.santaclara.ca.sfba.comcast.net [162.151.86.57]
6 12 ms 10 ms 11 ms be-36331-cs03.sunnyvale.ca.ibone.comcast.net [96.110.41.73]
7 14 ms 13 ms 13 ms be-1312-cr12.sunnyvale.ca.ibone.comcast.net [96.110.46.30]
8 20 ms 14 ms 15 ms be-302-cr01.9greatoaks.ca.ibone.comcast.net [96.110.37.174]
9 12 ms 14 ms 11 ms be-2212-pe12.9greatoaks.ca.ibone.comcast.net [96.110.33.38]
10 * * * Request timed out.
11 13 ms 12 ms 13 ms ae-11.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.120]
12 51 ms 47 ms 46 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
13 52 ms 47 ms 46 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
14 47 ms * * 204.2.229.234
15 47 ms 45 ms 47 ms 204.2.229.9

1 <1 ms <1 ms <1 ms x
2 9 ms 8 ms 11 ms x
3 9 ms 8 ms 9 ms x
4 9 ms 8 ms 8 ms x
5 11 ms 12 ms 11 ms be-298-ar01.santaclara.ca.sfba.comcast.net [162.151.86.57]
6 14 ms 12 ms 12 ms be-36331-cs03.sunnyvale.ca.ibone.comcast.net [96.110.41.73]
7 13 ms 11 ms 12 ms be-1312-cr12.sunnyvale.ca.ibone.comcast.net [96.110.46.30]
8 16 ms 13 ms 11 ms be-302-cr01.9greatoaks.ca.ibone.comcast.net [96.110.37.174]
9 11 ms 11 ms 11 ms be-2212-pe12.9greatoaks.ca.ibone.comcast.net [96.110.33.38]
10 43 ms * * 50.208.234.10
11 12 ms 11 ms 14 ms ae-11.r24.snjsca04.us.bb.gin.ntt.net [129.250.3.120]
12 57 ms 48 ms 46 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
13 46 ms 56 ms 47 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
14 * * 50 ms 204.2.229.234
15 46 ms * 47 ms 204.2.229.9

[TattersailNightwish]

Well I have to say it wasn't near as bad tonight as last night. Only had problems in instances and even then only past 10:00 (central) - was ok before that.
It does sound like SE is doing something, and as I said in an earlier post, this sounds familiar..it seems like the week before a big patch, we see behavior like this. I'd love to think that's the case.

[Yitsy]

Bumping this thread, 4 people from my raid group, tons of people on reddit + 5-6 people on ffxiv/discord all xfinity/comcast customers.

[MadCabbit]

I've also been having these issues using Xfinity.

7 29 ms 28 ms 28 ms be-33122-cs02.350ecermak.il.ibone.comcast.net [96.110.42.229]
8 * * * Request timed out.
9 32 ms 28 ms 30 ms ae-3.r08.chcgil09.us.bb.gin.ntt.net [129.250.8.65]
10 33 ms 35 ms 30 ms ae-4.r23.chcgil09.us.bb.gin.ntt.net [129.250.2.205]
11 76 ms 76 ms 78 ms ae-1.r24.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
12 112 ms 108 ms 114 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
13 114 ms 106 ms 113 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
14 * 116 ms 105 ms 204.2.229.234
15 109 ms 112 ms 106 ms 204.2.229.10

Trace complete.

The packet loss starts off at the last hop on Xfinity's network, that hop resolves as be-2211-pe11.350ecermak.il.ibone.comcast.net when I get a response to it.