Problems with connection (R0) lag

ISP: NTT
Location: Ibaraki, Japan
Started: A day ago.

-I've been playing on the NA server Ultros with friends.

http://images.bluegartr.com/bucket/g...dfe7b8e90d.png


:(

Noticed this problem two days ago and I tried everything I could think off on my end but the random lag spikes still persist. This thing is murder in the later dungeons where a 10 second lag is just unnaceptable...
ISP: RDS
Location: Romania

Try this... I just tried it as I have the lag problems and then 90k error.. I logged into a jap server... No lag and no 90k error... So it's not your ISP, it's NA/EU servers.

Connect to a jap server, there is no lag or 90k error... I'm having the lag and then 90k error. Not our ISPs that's for sure.

already posted this in the main P2P thread but this one is just as valid

Quote:

---

Backstory
ISP: RCN (philly metro area)
Started: ~1:30am EDT September 2nd
Problems: interment heavy lag spikes where Receiving goes to 0(R:0). Often leads to disconnects
Methodology: used the script outlined http://forum.square-enix.com/ffxiv/t...=1#post1109184

Results

First I ran ~90 minutes of tracert to the login server a clean one (omitting first 4 steps) looks like the following

5 16 ms 14 ms 12 ms 207.172.19.225
6 12 ms 13 ms 13 ms 207.172.19.205
7 16 ms 17 ms 14 ms 206.126.236.19
8 61 ms 38 ms 35 ms 89.149.185.41
9 27 ms 28 ms 26 ms 173.241.130.106
10 28 ms 28 ms 26 ms 67.205.127.82
11 26 ms 27 ms 26 ms 72.55.128.44
12 25 ms 26 ms 30 ms 184.107.107.176

This tracert ran 184 times meaning each step received 552 pings. Hops 3,4,5,6,9,10,11 never failed. The 7th failed 16 times, 8th failed 14 times and the 12th failed a single time.


Then I thought pinging the login server wasn't going to tell me a whole lot so I went for a server instead ( I believe this particular one is leviathan)
Test ran 181 times for 543 pings per hop. Healthy tracert looks like

5 14 ms 14 ms 13 ms 207.172.19.11
6 13 ms 15 ms 13 ms 207.172.19.9
7 15 ms 15 ms 22 ms 206.126.236.19
8 69 ms 34 ms 35 ms 89.149.185.41
9 36 ms 36 ms 37 ms 216.221.156.110
10 40 ms 38 ms 38 ms 192.34.76.2
11 39 ms 39 ms 40 ms 199.91.189.234
12 39 ms 38 ms 40 ms 199.91.189.21

This time I ran into a lot more hangs. hop 3,4,5,6 were still all clean however 7 had twenty fails, 8 had four, 9 had ten, 10 had eleven fails, 11 had three fails and 12 had eight fails. Also these fails were more clustered (getting 2 in a row).

Conclusion
This is beyond me but I'd certainly be looking into 206.126.236.19 as a potential problem spot. Please do try this on your own and hopefully we can narrow down issue a bit.

184.107.107.176_________1 fail/552
199.91.189.234__________3 fail/543
199.91.189.21___________8 fail/543
216.221.156.110_________10 fail/543
192.34.76.2_____________11 fail/543
89.149.185.41___________18 fail/1095
206.126.236.19__________36 fail/1095

total___________________87 fails
Also while typing this I did a simple ping test(leviathan server) 500 times and had a failure rate of 3%

---

Same problem...
Same lack of acknowledgement...
Same disappointment...

Started September 2nd and happens every time I log in.

yea its killing the game 4 me i hope it gets fixed cuz i hav to stay out of dungeons so it wont effect others... needless to say it has halted my story progress many times

I was hoping the maintenance would fix this but apparantly not. Wonder how long we're going to have to wait to even get this acknowledged.

BTW, try connecting to a jap server... I didn't get a single lag spike or 90k error.

Quote:

---

Originally Posted by SunnySun

BTW, try connecting to a jap server... I didn't get a single lag spike or 90k error.

---

This is true while the latency is 5x higher(200ms versus 40ms) I had a 0% ping time out in my sample to typhon compared to 6% to behemoth

bump. Same exact issues. Very frustrating as an arcanist. Century link DSL in Idaho (NW) Adding my stamp for a hopeful fix

I have the same issue with Century Link in Idaho. This may stem in part from the ISP though as they refuse to run full fiber in the area and limit to 896k up

Quote:

---

Originally Posted by Ratm3000

Same, since September 2nd been having horrible lag followed by a 90k error (disconnect).
It's still happening after the 10 hour maintenance on September 4th.

ISP: RCN
Location: Woodside, NY

http://forum.square-enix.com/ffxiv/t...P2P-throttling

---

Hey man, I'm also close by (In Astoria) and also on RCN. I was wondering if you were able to find a solution to the problem and/or any updates.

Quote:

---

Originally Posted by ReignmakerI

Hey man, I'm also close by (In Astoria) and also on RCN. I was wondering if you were able to find a solution to the problem and/or any updates.

---

tracert is pretty indicative that the problem is on their end or a middleman for us

Quote:

---

Originally Posted by Marishi-Ten

I have the same issue with Century Link in Idaho. This may stem in part from the ISP though as they refuse to run full fiber in the area and limit to 896k up

---

LAWL +1

I'm guessing Our ISPs aren't aware of the new ports SE is trying to use and are blocking them thinking they are viruses and malware. <.<

Character Name : Gino Zalbino, Eitheta Lombardi
World : Excalibur, Sargantanas
ISP : Time Warner (Greensboro, NC)
Does it happen only on one world or character ? : No. It happens on all characters, and on every server I've tried.
When the problem started happening ? : Monday, August 26th. I had no problems playing that first Saturday.

This is getting very frustrating. Even when I log in, I can't play the game AT ALL! I've rebooted my router, my modem, called Time Warner, my internet speed is fine... but I can't play at all! Help!

I tested running around in Camp Dragonhead... I lasted 3 minutes before disconnecting. Here's some "lag spike" highlights:

Sending: 30
Receiving: 0

Ten seconds later:
Sending: 30
Receiving: 19068

A minute later:
Sending: 231
Receiving: 0

15 seconds later:
Connection Lost - Error 90000

Will a Community Rep at least tell us that this problem has been forwarded to the team? (it's been 3 days already)...

P.S: I tried to push it but the lag spikes are omnipresent... I experienced some while doing Auto-Run in my Inn Room (monitoring the Send/Receive).

Yes, please, at least acknowledge that you're aware that many people are having this problem, SE. That is the worst part of it all. Not an ounce of communication. We have no clue if they're even aware of this or not. Like IronSoup said, it's been a few days already. A simple acknowledgement isn't very much to ask for, really.

They probably don't even know this problem exist

Disconnection #10 since 5 pm ET... meaning 10 disconnections in 5 hours !!! ... with lag spikes every time I'm in the game.

I'll keep writing about my experience with this issue.
More information can help solve this problem (and shows it's not fixing itself magically over time).

EDIT: I ended up with 20 Connection Lost (Error 90000) in 7 hours 30 minutes by doing gathering (the rate of DC was quicker while gathering in Coerthas and Mor Dhona)


P.S: No problem getting back on though (less than 1 min)... it's just a random disconnection because of the lag.

This is driving me nuts. Is there anyway to find out where I'm losing packets if I'm playing on PS3? If I could just contribute some more information to the cause it would make me feel a lot better.

Also, I second the notion that I would like to see some confirmation about this issue from a Square-Enix rep. Just knowing they are aware of it would do a lot to ease my mind.

I have been having severe lag as well since Monday. Prior to that it wasn't as bad... Now the game is almost unplayable due to lag. The game kind of pauses and than fast forwards to catch up to present time... As a healer this puts lots of strain on my job...

still no news anywhere?

Throwing my hat into the ring. This did not start happening to me since about 6 hours ago, and now it's just huge lag spikes, and eventually the server stops sending me data and boots me with a 90000. Behemoth server.

WHY has there been no answer from SE? It`s been 4 days now!

for the last 2 days, my lag hasnt came back whatsoever. I dunno how it was fixed.

Network maintenance tomorrow. Maybe there's still hope?

This is how pinging Phoenix looks:
Reply from 199.91.189.42: bytes=32 time=138ms TTL=240
Request timed out.
Reply from 199.91.189.42: bytes=32 time=136ms TTL=240
Reply from 199.91.189.42: bytes=32 time=148ms TTL=240
Reply from 199.91.189.42: bytes=32 time=143ms TTL=240
Reply from 199.91.189.42: bytes=32 time=136ms TTL=240
Reply from 199.91.189.42: bytes=32 time=147ms TTL=240
Reply from 199.91.189.42: bytes=32 time=152ms TTL=240
Reply from 199.91.189.42: bytes=32 time=135ms TTL=240
Reply from 199.91.189.42: bytes=32 time=135ms TTL=240
Reply from 199.91.189.42: bytes=32 time=141ms TTL=240
Reply from 199.91.189.42: bytes=32 time=136ms TTL=240
Reply from 199.91.189.42: bytes=32 time=137ms TTL=240
Reply from 199.91.189.42: bytes=32 time=138ms TTL=240
Reply from 199.91.189.42: bytes=32 time=135ms TTL=240
Reply from 199.91.189.42: bytes=32 time=129ms TTL=240
Reply from 199.91.189.42: bytes=32 time=137ms TTL=240
Reply from 199.91.189.42: bytes=32 time=131ms TTL=240
Reply from 199.91.189.42: bytes=32 time=130ms TTL=240
Reply from 199.91.189.42: bytes=32 time=134ms TTL=240
Reply from 199.91.189.42: bytes=32 time=129ms TTL=240
Reply from 199.91.189.42: bytes=32 time=138ms TTL=240
Reply from 199.91.189.42: bytes=32 time=137ms TTL=240
Reply from 199.91.189.42: bytes=32 time=131ms TTL=240
Reply from 199.91.189.42: bytes=32 time=148ms TTL=240
Reply from 199.91.189.42: bytes=32 time=139ms TTL=240
Reply from 199.91.189.42: bytes=32 time=137ms TTL=240
Reply from 199.91.189.42: bytes=32 time=139ms TTL=240
Reply from 199.91.189.42: bytes=32 time=144ms TTL=240
Reply from 199.91.189.42: bytes=32 time=130ms TTL=240
Reply from 199.91.189.42: bytes=32 time=131ms TTL=240
Reply from 199.91.189.42: bytes=32 time=133ms TTL=240
Request timed out.
Reply from 199.91.189.42: bytes=32 time=148ms TTL=240
Reply from 199.91.189.42: bytes=32 time=129ms TTL=240
Reply from 199.91.189.42: bytes=32 time=133ms TTL=240
Reply from 199.91.189.42: bytes=32 time=136ms TTL=240
Reply from 199.91.189.42: bytes=32 time=130ms TTL=240
Reply from 199.91.189.42: bytes=32 time=141ms TTL=240
Reply from 199.91.189.42: bytes=32 time=143ms TTL=240
Reply from 199.91.189.42: bytes=32 time=146ms TTL=240
Reply from 199.91.189.42: bytes=32 time=130ms TTL=240
Reply from 199.91.189.42: bytes=32 time=140ms TTL=240
Reply from 199.91.189.42: bytes=32 time=131ms TTL=240
Reply from 199.91.189.42: bytes=32 time=137ms TTL=240
Reply from 199.91.189.42: bytes=32 time=138ms TTL=240
Reply from 199.91.189.42: bytes=32 time=138ms TTL=240
Reply from 199.91.189.42: bytes=32 time=131ms TTL=240
Reply from 199.91.189.42: bytes=32 time=146ms TTL=240
Reply from 199.91.189.42: bytes=32 time=129ms TTL=240
Reply from 199.91.189.42: bytes=32 time=131ms TTL=240
Reply from 199.91.189.42: bytes=32 time=137ms TTL=240
Reply from 199.91.189.42: bytes=32 time=140ms TTL=240
Request timed out.
Request timed out.
Request timed out.
Reply from 199.91.189.42: bytes=32 time=139ms TTL=240

This is how pinging google looks:
Reply from 173.194.44.50: bytes=32 time=26ms TTL=56
Reply from 173.194.44.50: bytes=32 time=30ms TTL=56
Reply from 173.194.44.50: bytes=32 time=31ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=26ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=26ms TTL=56
Reply from 173.194.44.50: bytes=32 time=35ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=31ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=26ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=26ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=58ms TTL=56
Reply from 173.194.44.50: bytes=32 time=30ms TTL=56
Reply from 173.194.44.50: bytes=32 time=58ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=29ms TTL=56
Reply from 173.194.44.50: bytes=32 time=26ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=26ms TTL=56
Reply from 173.194.44.50: bytes=32 time=29ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=40ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=29ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=29ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=32ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=38ms TTL=56
Reply from 173.194.44.50: bytes=32 time=30ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Request timed out.
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=29ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=29ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=29ms TTL=56
Reply from 173.194.44.50: bytes=32 time=29ms TTL=56
Reply from 173.194.44.50: bytes=32 time=30ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=26ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=29ms TTL=56
Reply from 173.194.44.50: bytes=32 time=29ms TTL=56
Reply from 173.194.44.50: bytes=32 time=26ms TTL=56
Reply from 173.194.44.50: bytes=32 time=28ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=30ms TTL=56
Reply from 173.194.44.50: bytes=32 time=26ms TTL=56
Reply from 173.194.44.50: bytes=32 time=26ms TTL=56
Reply from 173.194.44.50: bytes=32 time=29ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56
Reply from 173.194.44.50: bytes=32 time=25ms TTL=56
Reply from 173.194.44.50: bytes=32 time=27ms TTL=56

I do get about 1% packet loss in general it seems, but it's not nearly as much as I get with phoenix.

They just did a network maintenance , didn;t change a damn thing i still lag everytime i get in the game and disconnect with error 90000 again. I am starting to think none of them know how servers work.

I am also randomly freezing for a period of time which varies, in dungeons it's usually a longer time than when I am questing on my own. I'm sure it has something to do with the fact I'm playing on a JP world and not an NA/EU world. I am hoping that server transfers which are due to come in mid-September will allow me to change to a NA/EU server, and hopefully sort out my issue.

I am having the same issue, sent in a help ticket with customer support, still no reply. I am getting very frustrated. I can't complete a single dungeon all the way through without lagging/R=0 every 30-90 seconds, and then error 90000 disconnecting me, which then prohibits me from joining back up into the instance I was just in, having to start ALL OVER again and again and again and again and again. Can SE please update us on the current situation with this issue? Has it even been addressed? ISP running great, modem and router the same. What is going on?

Quote:

---

Originally Posted by Lytir

I am also randomly freezing for a period of time which varies, in dungeons it's usually a longer time than when I am questing on my own. I'm sure it has something to do with the fact I'm playing on a JP world and not an NA/EU world. I am hoping that server transfers which are due to come in mid-September will allow me to change to a NA/EU server, and hopefully sort out my issue.

---

It is not the world you are on, myself and many others have attempted to create characters on other worlds to test this, and we still get the same lag, be it JP server or a NA/EU one.

They dont care, they just want the free month to go away and people to leave so they can spent as little as possible on servers. Its an outrage to add 1 new server when you know all the other servers where full but again most will leave after free month so from management point of view its a bad investment to get more servers for 1 month.

Quote:

---

Originally Posted by Gebeleizis

They dont care, they just want the free month to go away and people to leave so they can spent as little as possible on servers. Its an outrage to add 1 new server when you know all the other servers where full but again most will leave after free month so from management point of view its a bad investment to get more servers for 1 month.

---

is not that easy to find solutions...
I'm not network expert, but i know some things, there are tons of rules on routers/firewalls and you need time to find out which cause problem, because in my opinion, they added some rules on 2nd Sept which cause the problem we have. Or maybe they added a new device which is not properly configured.
We just have to hope they have an inspired guy in their NOC, who know where to look to fix the problem... if they dont have that guy, it might take days/weeks till the they find the problem :)

Quote:

---

Originally Posted by Horatium

is not that easy to find solutions...
I'm not network expert, but i know some things, there are tons of rules on routers/firewalls and you need time to find out which cause problem, because in my opinion, they added some rules on 2nd Sept which cause the problem we have. Or maybe they added a new device which is not properly configured.
We just have to hope they have an inspired guy in their NOC, who know where to look to fix the problem... if they dont have that guy, it might take days/weeks till the they find the problem :)

---

Its not the rules or software problem its a hardware problem, they dont have proper equipment to handle this and I dont think they will add more.

Quote:

---

Originally Posted by Gebeleizis

Its not the rules or software problem its a hardware problem, they dont have proper equipment to handle this and I dont think they will add more.

---

well, when you say "hardware" you have to know, that hardware device has an software also... :)
And i dont think they dont have good hardware, because if that was the cause, then WE ALL had lag/problems... but right now, there are players who play smooth...

Posting here is useless anyway. After hundreds of pages of complains, we have 0 replies / resolution from SE.

Quote:

---

Originally Posted by gigi_frana

Posting here is useless anyway. After hundreds of pages of complains, we have 0 replies / resolution from SE.

---

Ill disagree on the useless part but i agree on the part where you say SE didn't reply or fix anything. It's just that hard to keep us informed.

Quote:

---

Originally Posted by Vespar

It is not the world you are on, myself and many others have attempted to create characters on other worlds to test this, and we still get the same lag, be it JP server or a NA/EU one.

---

That's depressing, I hope it gets sorted out soon, after all the errors and inability to log on, this is a real kick in the pants as it's not very fun playing by myself, which for me is really the only option as joining dungeons with this sort of lag/freezing is rendering me useless.

If anyone has ever seen "Bernard's Watch" on UK Television, this is similar to what I am experience, I being in Bernards shoes, and I guess this "Receiving" thing to be the watch. At the end of this period of seemingly stopped time, everything goes very fast, playing out all the things that would have happened to/from me and to/from others, during that time.