ISP: NTT
Location: Ibaraki, Japan
Started: A day ago.
-I've been playing on the NA server Ultros with friends.
ISP: NTT
Location: Ibaraki, Japan
Started: A day ago.
-I've been playing on the NA server Ultros with friends.
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
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.
Last edited by IronSoup; 09-05-2013 at 05:26 AM.
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
wish i had a cool sig..
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.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.