Problems with connection (R0) lag

[ryan92084]

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

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%

[IronSoup]

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

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

[Brobotnik]

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.

[comander21]

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

[SunnySun]

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

[ryan92084]

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

[Xyphre]

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

[Gammatron]

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!

[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

[Xyphre]

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. <.<