All the lag, network issues are server side [CONFIRMED]

[Ganglia]

I lag during most of the day but periodically the rubber banding becomes intolerable in even fate play. I've got no throttling and in tracert I can see the issues in lag are definitely occurring once I reach Montreal. I live in California and all things are good from there to New York. No jitter, no packet loss, no significant latency...77ms to NY and that is consistent.

Obviously hard modes are fruitless for me. I can do Garuda and Ifrit because I know the fights well enough to move where I need and do what I need to heal folks. But Titan is out of the question.

I am going to set my account pay from quarterly to monthly and then stop it completely if it is still an issue by the end of this month.

[ntall1]

If it was really a server issue it would affect 100% of the players online at the time. Not just 85% of them......

[Appleh4x]

If it was really a server issue it would affect 100% of the players online at the time. Not just 85% of them......

It is if the server is specifically timing out certain IPs to improve service going to others. I think it's kind of funny that an SE rep specifically told me it was the server, and you guys are still acing like that isn't the problem.

[Nekodar]

It is if the server is specifically timing out certain IPs to improve service going to others. I think it's kind of funny that an SE rep specifically told me it was the server, and you guys are still acing like that isn't the problem.

1) Lag issues are from congestion
2) A small number of 90k's can be from the server
3) As can be proven by plenty of people, not all 90k's are SE's fault

Don't read more into the reply you got than is needed.

[Appleh4x]

1) Lag issues are from congestion
2) A small number of 90k's can be from the server
3) As can be proven by plenty of people, not all 90k's are SE's fault

Don't read more into the reply you got than is needed.

I'm not reading more into it, the SE guys didn't have me run any tests, this is what they flat out told me was the problem. My own traceroutes I have run here on the forums are fine and the ones you are referring to about other people "proving" some aren't SE's fault is BS. A 200 ms ping is 1/5 of a second. That is what cogent is giving those people, 1/5 a sec of lag. What everyone is complaining about is actually several full seconds of lag, timeouts, etc that are the fault of the server. You guys have been wrong from the start and know next to nothing about how a traceroute actually even works. I saw someone blame a lone * (timeout) as the problem in someone's traceroute, not a full timeout mind you, but 1 lone asterisk.

[Nekodar]

I'm not reading more into it, the SE guys didn't have me run any tests, this is what they flat out told me was the problem. My own traceroutes I have run here on the forums are fine and the ones you are referring to about other people "proving" some aren't SE's fault is BS. A 200 ms ping is 1/5 of a second. That is what cogent is giving those people, 1/5 a sec of lag. What everyone is complaining about is actually several full seconds of lag, timeouts, etc that are the fault of the server. You guys have been wrong from the start and know next to nothing about how a traceroute actually even works. I saw someone blame a lone * (timeout) as the problem in someone's traceroute, not a full timeout mind you, but 1 lone asterisk.

90000 disconnect is not the same as the lag issues. They are two separate problems.
Lag issues come from two main points: 1) Server congestion (affects most people on at the time), 2) Packet shaping (affects only people whose path is being shaped)

I'm not saying the 90000 error is never on SE's side, but in general it's not, and it's also not the same thing as the lag issues... Please understand the difference between these issues and that there are more ways than one that things can go wrong.

[Gonzothegreat198]

It is if the server is specifically timing out certain IPs to improve service going to others. I think it's kind of funny that an SE rep specifically told me it was the server, and you guys are still acing like that isn't the problem.

Another issue? You weren't told jack by an SE rep, you were given an automated response, one that had been given countless times before. You mentioned you 90k'd so they gave you the generic automated response for 90k issues. That in and of itself is not enough evidence to then go and say "HEY GUYZ I KNOW WHAT YOUR PROBLEM IS". If you would actually look at the various other threads in this forums you would see that there is strong evidence for there being either a server-side network infrastructure(ie routing/cabling) or network hardware(Router, switch, access point) issue. Especially since the latest posts have almost nothing to do with 90k. Its all about major lag, rubberbanding, strobe effect...etc.

[Brises]

It is if the server is specifically timing out certain IPs to improve service going to others. I think it's kind of funny that an SE rep specifically told me it was the server, and you guys are still acing like that isn't the problem.

Most businesses outsource their tech support to agencies who are not even involved with the product, and are given a list of things to say when someone contacts them. It is very rare that an issue needs to be forwarded to the actual contracting business. Many times people will get answers from these "support" agencies that are completely false.

And as far as "all problems"? I have never had a 9000 error, but have had others. That message only specified the 9000 error code.

[FearMyLazorFace]

well, its good to see that i'm not the only one getting the 90k error every 5 minutes or so

[Nekodar]

A majority of all 90k I have experienced have NOT been from SE servers disconnecting me, but from issues with my network provider.
Whenever it happens, the gateway at my network provider stops responding to ping, and there's no way that SE can cause that.
My network provider keep saying there is no problem, even when I can prove there is A problem on their side.

The times I've been certain that it was on SE's side the disconnection occurred, it also affected everyone connected to the same instance/world server.

The lag issues are in general separate from the 90k issues and mostly happen during peak times when servers are congested.