Unbearable server lag since yesterday

[allenr]

Dropping in to say I'm oddly not having any lag today. Suffered problems all last week before servers went down. Today's been totally fine without needing any software. No idea what's going on but I hope a fix comes out for the rest of everyone else.

[Agarthas]

no more queue and lag since intra world transport closed !

[White_Wolf_X]

Seems the lag is gone today ( for now ) and didn't have any problems now when i did a trace.

[MilkieTea]

Seems the lag is gone today ( for now ) and didn't have any problems now when i did a trace.

either SE slapped a bandaid on it (in which case this might happen again to comcast users in another year or so? Or maybe even next patch. Seems like that's what happened last time, a few years back) or NTT fixed things on their end (in which case... I dunno when or if the problem *would* occur again.)

[TattersailNightwish]

I'm reporting that I didn't have any problems last night. I was debating doing the new raid, but didn't want to have to ditch if the lag/rubber banding became too bad. So I did a few Chocobo races (it had been REALLY bad in there), and was lag-free.
So I did the new raid and didn't have any lag problems whatsoever.

I can't blame my ten deaths on lag.

[MilkieTea]

I'm reporting that I didn't have any problems last night. I was debating doing the new raid, but didn't want to have to ditch if the lag/rubber banding became too bad. So I did a few Chocobo races (it had been REALLY bad in there), and was lag-free.
So I did the new raid and didn't have any lag problems whatsoever.

I can't blame my ten deaths on lag.

Rip af

/10char

[Cori_Xaayr]

This issue still isn't resolved for me. The same nodes are still experiencing problems.

5 21 ms 22 ms 23 ms cr2.nsvtn.ip.att.net [12.123.129.74]
6 24 ms 22 ms 23 ms attga22crs.ip.att.net [12.122.2.41]
7 16 ms 22 ms 22 ms attga402igs.ip.att.net [12.122.117.121]
8 17 ms 15 ms * 192.205.36.158
9 18 ms 16 ms 17 ms ae-16.r22.atlnga05.us.bb.gin.ntt.net [129.250.5.57]
10 34 ms 32 ms 29 ms ae-4.r25.dllstx09.us.bb.gin.ntt.net [129.250.4.116]
11 68 ms 70 ms 70 ms ae-2.r25.snjsca04.us.bb.gin.ntt.net [129.250.4.154]
12 * * * Request timed out.
13 76 ms 72 ms 73 ms ae-4.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.57]
14 74 ms 73 ms 73 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [192.80.16.2]
15 77 ms 73 ms 78 ms 204.2.229.234
16 85 ms 74 ms 71 ms 204.2.229.9

Trace complete.

Reply from 204.2.229.9: bytes=32 time=74ms TTL=51
Reply from 204.2.229.9: bytes=32 time=72ms TTL=51
Reply from 204.2.229.9: bytes=32 time=76ms TTL=51
Reply from 204.2.229.9: bytes=32 time=72ms TTL=51
Reply from 204.2.229.9: bytes=32 time=75ms TTL=51
Reply from 204.2.229.9: bytes=32 time=72ms TTL=51
Reply from 204.2.229.9: bytes=32 time=75ms TTL=51
Request timed out.
Request timed out.
Reply from 204.2.229.9: bytes=32 time=73ms TTL=51
Reply from 204.2.229.9: bytes=32 time=74ms TTL=51
Reply from 204.2.229.9: bytes=32 time=72ms TTL=51
Reply from 204.2.229.9: bytes=32 time=82ms TTL=51
Reply from 204.2.229.9: bytes=32 time=75ms TTL=51

[jonTron_Is_The_Bird]

I've been having this issue for the last 2 years, also on comcast. I live in cali used to get ~12ms ping to coeurl lobby where my character is but now my avg is 18-24ms.

Problems seem to only start after patch days and can last from 2 days all the way to 2 months later. I tracert most of the time and its always the Comcast node right before NTT that seems to be the issue. There have been a few times where the first NTT node was the problem but the internet issues were also more widespread that day affecting more than Comcast and isp's that are using Comcast lines.

I've tried different VPN's and pretty much every sensible route leads through a comcast clusters before you hit NTT from where I live. Comcast has a monopoly on the lines in my area and I have a feeling no matter what I do my traffic will always route through that problem node cluster to reach SE servers.

I'm starting to think NTT refused to pay comcast shakedown money and thats why we are cursed with constant packet issues.

[MilkieTea]

I'm starting to think NTT refused to pay comcast shakedown money and thats why we are cursed with constant packet issues.

This sounds like a joke but US ISPs are so crummy that it's entirely possible and that's a huge sign lol.

[Hacchan]

Just recently started to get network issue, the weirdest thing is it's only during instances.
Dungeon, Raid24 etc i start getting a lot of packet loss,lag with people skipping around, world hang, input delay or just input ignored.
Meanwhile open world, busy hub etc 0 issue, people walk fine and all, SSS dummy 0 input issue