Still getting CONSTANT 90k errors

[PEANUT]

Raist! Thank you very much for your advise and information. I am STILL getting dc'ed with an Error 90000 all the time. I called my ISP Tier 1 and of course like you said, they couldn't help me much, but he did advise me even before I read your post on using a tracert to find out where I'm getting latency issues. Here is a post of my tracert, it seems my issue is constantly around #5. I have no idea what or where it is or how I can fix it. I will call up my ISP again and try and speak to a Tier 3 person to help, but in the meantime could I have your opinion or any other advise you can give me, because now I pretty much can't even play because it happens to frequently, and it saddens me because I love this game :"(

Also, this started happening on Tuesday, which was 4 days ago. My ISP is Verizon, I am on Wireless(I know I know, but I have been playing perfectly fine for a whole year -_-) and my speeds are on 50/50 mbps.

tracert 184.107.107.176

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 1 ms 1 ms 1 ms
2 6 ms 5 ms 5 ms L100.NYCMNY-VFTTP-145.verizon-gni.net [98.113.50
.1]
3 10 ms 6 ms 8 ms G101-0-0-0.NYCMNY-LCR-21.verizon-gni.net [100.41
.211.224]
4 * * * Request timed out.
5 9 ms 9 ms 9 ms 0.ae1.BR2.NYC4.ALTER.NET [140.222.229.91]
6 9 ms 9 ms 10 ms 204.255.168.114
7 10 ms 9 ms 9 ms be2061.ccr22.jfk02.atlas.cogentco.com [154.54.3.
69]
8 15 ms 15 ms 15 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30
.42]
9 20 ms 19 ms 21 ms be2302.ccr21.alb02.atlas.cogentco.com [154.54.43
.14]
10 23 ms 24 ms 25 ms be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43
.17]
11 26 ms 27 ms 26 ms te8-4.cl-core06.cogent.mtl.iweb.com [38.104.154.
202]
12 27 ms 26 ms 27 ms te7-4.dr9.mtl.iweb.com [184.107.1.110]
13 24 ms 24 ms 25 ms 72.55.128.44
14 27 ms 26 ms 24 ms 184.107.107.176

Trace complete.

tracert neolobby02.ffxiv.com

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms
2 7 ms 17 ms 25 ms L100.NYCMNY-VFTTP-145.verizon-gni.net [98.113.50
.1]
3 8 ms 10 ms 6 ms G0-11-0-3.NYCMNY-LCR-21.verizon-gni.net [130.81.
131.76]
4 8 ms 7 ms 14 ms ae3-0.NY325-BB-RTR2.verizon-gni.net [130.81.199.
154]
5 * * * Request timed out.
6 23 ms 6 ms 8 ms 2.ae0.XT2.NYC4.ALTER.NET [140.222.227.27]
7 17 ms 12 ms 12 ms TenGigE0-7-4-0.GW8.NYC4.ALTER.NET [152.63.21.133
]
8 27 ms 26 ms 28 ms tinet-gw.customer.alter.net [152.179.72.122]
9 72 ms 31 ms 29 ms xe-7-3-0.mtl10.ip4.gtt.net [141.136.106.106]
10 26 ms 27 ms 26 ms ormuco-gw.ip4.gtt.net [216.221.156.110]
11 29 ms 26 ms 26 ms 192.34.76.2
12 31 ms 29 ms 28 ms 199.91.189.234
13 29 ms 29 ms 30 ms 199.91.189.74

Trace complete.

tracert neolobby04.ffxiv.com

Tracing route to neolobby04.ffxiv.com [199.91.189.93]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms
2 7 ms 5 ms 5 ms L100.NYCMNY-VFTTP-145.verizon-gni.net [98.113.50
.1]
3 8 ms 11 ms 10 ms G0-11-0-3.NYCMNY-LCR-22.verizon-gni.net [130.81.
131.254]
4 * * * Request timed out.
5 8 ms 8 ms 8 ms 2.ae0.XT2.NYC4.ALTER.NET [140.222.227.27]
6 13 ms 12 ms 13 ms TenGigE0-5-2-0.GW8.NYC4.ALTER.NET [152.63.16.125
]
7 21 ms 20 ms 19 ms tinet-gw.customer.alter.net [152.179.72.122]
8 37 ms 51 ms 32 ms xe-4-2-0.mtl10.ip4.gtt.net [141.136.107.125]
9 28 ms 30 ms 31 ms ormuco-gw.ip4.gtt.net [216.221.156.110]
10 28 ms 27 ms 26 ms 192.34.76.2
11 25 ms 26 ms 32 ms 199.91.189.234
12 29 ms 28 ms 28 ms 199.91.189.93

Trace complete.

tracert neolobby06.ffxiv.com

Tracing route to neolobby06.ffxiv.com [199.91.189.106]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms
2 5 ms 10 ms 6 ms L100.NYCMNY-VFTTP-145.verizon-gni.net [98.113.50
.1]
3 9 ms 7 ms 8 ms G0-11-0-3.NYCMNY-LCR-21.verizon-gni.net [130.81.
131.76]
4 14 ms 82 ms 25 ms ae0-0.NY325-BB-RTR1.verizon-gni.net [130.81.209.
102]
5 * * * Request timed out.
6 49 ms 118 ms 6 ms 3.ae1.XT1.NYC4.ALTER.NET [140.222.228.121]
7 8 ms 10 ms 11 ms TenGigE0-4-2-0.GW8.NYC4.ALTER.NET [152.63.16.73]

8 22 ms 20 ms 20 ms tinet-gw.customer.alter.net [152.179.72.122]
9 31 ms 30 ms 30 ms xe-1-3-0.mtl10.ip4.gtt.net [89.149.184.74]
10 26 ms 26 ms 25 ms ormuco-gw.ip4.gtt.net [216.221.156.110]
11 29 ms 24 ms 24 ms 192.34.76.2
12 32 ms * 31 ms 199.91.189.234
13 27 ms 26 ms 26 ms 199.91.189.106

Trace complete.

[Raist]

@ Peanut:

Please, don't test against that 184.107.107.176 IP address. That is in no way connected to the game servers. It is a webserver hosted on i-web in a different section of town. The neolobby's though are on Ormuco lines and are in the subnet of the servers used for the game. If you want to test against your specific game server, you can get the IP by running netstat in a CMD prompt or loading Resource Monitor (resmon) and looking for the IP in the Network or TCP sections. All the servers in Canada that the game uses will start with 199 (the ones in JP that it uses periodically start with 124 for the most part).

It looks like alter.net may be one for them to look at. It was periodically getting a wide variance in response times:

6 23 ms 6 ms 8 ms 2.ae0.XT2.NYC4.ALTER.NET [140.222.227.27]

6 49 ms 118 ms 6 ms 3.ae1.XT1.NYC4.ALTER.NET [140.222.228.121]

This is more the kind of thing you want to look for... very erratic results happening at the same areas in your route(s). Those triple star events are not necessarily a sign of a problem, so long as they consistently show * * *. This usually means they have a policy to always drop ICMP ECHO requests. However, if that hop sometimes responds with a time, and then *'s at others--this means traffic shaping rules are kicking in to try to manage high congestion--that would definitely be something for them to investigate if it is happening often enough to be causing noticeable packet loss or delays (skip/pause, rubber-banding, excessive buffering for Netflix/Hulu/Roku/etc.).

Looks like there may be some issues on the other side of the alter.net peering section of your route as well when it is trying to hand off into Ormuco (SE's ISP). So yeah... your traces to the neolobby's may give them something they can work with at Tier3.

Verizon may have some work they need to do internally as well. There were a couple hops that were also getting a little weird within their segments. You may want to run some traces to something like google/youtube, netflix, or hulu as well because there may be some hiccups within the Verizon segments that may show up better against a busier streaming content provider.

Bear in mind, you aren't necessarily trying to diagnose this yourself. It is more a test for smoke before getting someone else to look for the fire. The traces can demonstrate that there may be a problem within their network or their partners, and gives them specific details so they can do additional testing on their own to make sure if/where/who they need to get involved.

[Rindali]

I too am using Verizon and have been getting frequent errors of the same sort in the past couple of days. I've noticed Verizon having issues with a number of other things (Youtube for one) as well in the same time span, but it seems very selective on what it'll cause problems for and what runs fine uninterrupted. I'll work on getting some tracers done, just adding to the pile.

[PEANUT]

Thanks so much for reply and taking the time to type that all out. It was very informative. However, I have been running tons of tracert tests for the past 2 or 3 days, figuring out what exactly the problem might be. Both from my cmd and from a software called PingPlotter to help. I also called and explained this to a Tier 1 tech. representative who then is sending the information to a Verizon Technician who should be contacting me by Monday and hopefully will be able to solve this.

But yes, I am getting constant * * * Request timed out, from Alter.net(#5) and occasionally from Verizon(#4), so I truly believe that is what is causing the issue with my frequent Error 90000's.

[PEANUT]

I have noticed that too with Youtube, a lot of videos will stop at a certain point then take forever to load, then I have to refresh and fast forward for them to start working again, even ran some tests from Youtube and am getting latency results.

[kram]

Same problem here, always disconnected after 3-5mins then when connecting it takes so much time that I decided to let it go. LOL!

To make the story short, my internet is working fine with other games except FFXIV and found out about this thread http://forum.square-enix.com/ffxiv/t...P2P-throttling

During prime time hours I experienced this errors and lags, but after that it's fine. However, during Fridays and Saturdays FFXIV is completely fine.

What seems to be the problem?