Regarding Reports on Recent Connection Problems with the NA Data Center

Today I've been getting error 90002 instead of the usual 90006.

Lower number is better right? Progress?! Only need to drop it down 90002 more times! (Yes, this is sarcasm. :P)

Monitored at 5:00AM(Sunday) GMT / 00:00AM(Sunday) EST / 9:00PM(Saturday) PST.

Code:

|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | SkyRouter.Home - 0 | 126 | 126 | 0 | 0 | 4 | 0 | | 97e7fe6a.skybroadband.com - 0 | 126 | 126 | 4 | 7 | 95 | 5 | | be365.pr2.hobir.isp.sky.com - 0 | 126 | 126 | 16 | 17 | 23 | 17 | | 62.73.179.165 - 0 | 126 | 126 | 16 | 16 | 18 | 16 | | ae-4.r24.londen12.uk.bb.gin.ntt.net - 0 | 126 | 126 | 15 | 16 | 24 | 16 | | ae-5.r24.nycmny01.us.bb.gin.ntt.net - 43 | 47 | 27 | 87 | 87 | 94 | 87 | | ae-2.r20.sttlwa01.us.bb.gin.ntt.net - 20 | 70 | 56 | 154 | 162 | 355 | 155 | | ae-0.r21.sttlwa01.us.bb.gin.ntt.net - 41 | 49 | 29 | 162 | 165 | 241 | 162 | | ae-3.r23.snjsca04.us.bb.gin.ntt.net - 0 | 126 | 126 | 174 | 175 | 183 | 175 | | ae-41.r02.snjsca04.us.bb.gin.ntt.net - 0 | 126 | 126 | 177 | 177 | 182 | 177 | | ae-3.r00.scrmca02.us.bb.gin.ntt.net - 0 | 126 | 126 | 179 | 179 | 181 | 180 | |xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net - 0 | 126 | 126 | 176 | 176 | 179 | 176 | | 204.2.229.234 - 36 | 53 | 34 | 0 | 176 | 177 | 176 | | 204.2.229.10 - 0 | 126 | 126 | 182 | 182 | 184 | 182 | |________________________________________________|______|______|______|______|______|______|

It really does come down to the server's location. California is not a good place to host all of NA. A central location is ideal. Less nodes to travel across for everyone and a more reliable location to boot.

Had a 90006 about 10:45 CST after being fine earlier this morning. Again, this was at Castrum Oriens, where the new Ananta beast tribe quests are. Seems to hit me more there than anywhere else. When I ported to Limsa, it took almost a full minute to load, and I arrived at an empty Limsa -- it took all the players and NPCs some time to load.

Not sure what the heck is going on here.

Update: And I'm back to regular 90006 errors at the same interval as they were before. Great.
Update 2: Was able to get in for about 10-15 minutes around 6:00 CST but got another 90006. Sigh.

ggr2.la2ca.ip.att.net averaging at 100.1 ms to...

ae-5.a00.lsanca20.us.bb.gin.ntt.net averaging at 215 ms. What is up with this terrible isp? This has been going on all stormblood. Starts at around 2 PM hawaii time and can last until as late as 8 or 9 PM. Sometimes only an hour, sometimes several. This is so much worse than it was back in the data center's old location and it is significantly closer to me. Under no circumstances should my ping literally double once it reaches NTT.

This is at 10:31pm CST

Code:

Tracing route to 204.2.229.10 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms RT-AC68U-5570 [192.168.1.1] 2 10 ms 10 ms 10 ms 96.120.28.53 3 11 ms 9 ms 16 ms te-0-7-0-8-sur03.chicago301.il.chicago.comcast.net [68.85.180.45] 4 9 ms 8 ms 9 ms 68.85.183.142 5 11 ms 12 ms 10 ms be-144-ar01.area4.il.chicago.comcast.net [162.151.45.69] 6 12 ms 12 ms 12 ms be-33491-cr02.350ecermak.il.ibone.comcast.net [68.86.91.165] 7 10 ms 10 ms 10 ms be-10577-pe03.350ecermak.il.ibone.comcast.net [68.86.86.2] 8 11 ms 11 ms 9 ms ae-26.a02.chcgil09.us.bb.gin.ntt.net [129.250.66.65] 9 68 ms 76 ms 78 ms ae-4.r08.chcgil09.us.bb.gin.ntt.net [129.250.4.157] 10 11 ms 14 ms 11 ms ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.205] 11 175 ms 67 ms 176 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17] 12 164 ms 161 ms 167 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121] 13 181 ms 185 ms 180 ms ae-3.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.11] 14 180 ms 186 ms 192 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46] 15 165 ms 108 ms 78 ms 204.2.229.234 16 67 ms 68 ms 65 ms 204.2.229.10 Trace complete.

Any time after about 6pm CST looks like this. And this'll go past midnight (checked it last night). In what universe is this acceptable performance?

Was able to stay online after a 90006 and 90002 for a little over an hour with no issues; then got another 90006 at 8:20 CST. I guess I'll just take whatever pockets of time I'm allowed and see what I can do -- but it's an awful way to try and play a game, especially one like this.

This is between 8 - 9 PM EST. Two days in a row with lot of packets drop, latency. I am using AT&T as ISP.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router - 0 | 136 | 136 | 0 | 0 | 1 | 0 |
| 192.168.255.254 - 0 | 136 | 136 | 0 | 0 | 6 | 0 |
| 172.26.96.169 - 0 | 136 | 136 | 48 | 62 | 157 | 49 |
| 107.72.174.92 - 0 | 136 | 136 | 48 | 64 | 153 | 58 |
| No response from host - 100 | 28 | 0 | 0 | 0 | 0 | 0 |
| 12.83.185.153 - 0 | 136 | 136 | 64 | 81 | 163 | 70 |
| 12.122.28.125 - 0 | 136 | 136 | 63 | 83 | 166 | 76 |
| attga402igs.ip.att.net - 0 | 136 | 136 | 61 | 80 | 159 | 72 |
| No response from host - 100 | 28 | 0 | 0 | 0 | 0 | 0 |
| ae-1.r04.atlnga05.us.bb.gin.ntt.net - 2 | 128 | 126 | 118 | 170 | 278 | 175 |
| ae-4.r21.atlnga05.us.bb.gin.ntt.net - 0 | 136 | 136 | 74 | 92 | 165 | 114 |
| ae-6.r23.dllstx09.us.bb.gin.ntt.net - 0 | 136 | 136 | 89 | 112 | 328 | 94 |
| ae-8.r23.snjsca04.us.bb.gin.ntt.net - 1 | 132 | 131 | 134 | 158 | 322 | 154 |
| ae-41.r02.snjsca04.us.bb.gin.ntt.net - 0 | 136 | 136 | 158 | 237 | 332 | 179 |
| ae-3.r00.scrmca02.us.bb.gin.ntt.net - 1 | 132 | 131 | 176 | 233 | 333 | 203 |
|xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net - 0 | 136 | 136 | 140 | 162 | 328 | 148 |
| 204.2.229.234 - 39 | 54 | 33 | 166 | 237 | 285 | 166 |
| 204.2.229.9 - 1 | 132 | 131 | 173 | 232 | 334 | 202 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

ive found another besides those ntt.net nodes that should be looked into

ix-ae-24-0.tcore1.LVW-Los-Angeles.as6453.net [66.110.59.81]

while other nodes on the route have some slight loss % it is like 0.02% or 0.05% of loss until it gets to this node where it suddenly has 5.5% loss. tested it 3 days in a row and it is always this node specifically that i see such loss % on and my ping jumps up by 30-40.
but as im sure has been stated, if you choose to move server locations again, somewhere like colorado would be a better choice simply due to less network congestion unlike the west coast and it is more central to the vast majority of players on the NA servers. also, i seem to really only be lagging in dungeons and almost never on the overworld areas

Just a note that I tried a full reinstall last night and I'm still getting constant 90006 errors this morning.

Quote:

Originally Posted by Aurorae

ive found another besides those ntt.net nodes that should be looked into

ix-ae-24-0.tcore1.LVW-Los-Angeles.as6453.net [66.110.59.81]

while other nodes on the route have some slight loss % it is like 0.02% or 0.05% of loss until it gets to this node where it suddenly has 5.5% loss. tested it 3 days in a row and it is always this node specifically that i see such loss % on and my ping jumps up by 30-40.
but as im sure has been stated, if you choose to move server locations again, somewhere like colorado would be a better choice simply due to less network congestion unlike the west coast and it is more central to the vast majority of players on the NA servers. also, i seem to really only be lagging in dungeons and almost never on the overworld areas

Those areas have a very slow update rate so you won't see the packet loss as much compared to dungeons. Extreme Primals and Raids have the highest update rate, dungeons are probably in the middle.