Can't play with this 90k...

[lordparanoia]

This game is becoming unplayable.
Frequently I have 90k.

World: RAGNAROK
Time: ALWAYS since more or less 1 week

I could understand it for ONE DAY, but since one week I have this problem and my connection is ok. So please tell me if you're having problems with the servers.

[Volgera]

Just got 90ked three times now in the middle of Coil. This sux!!!

Goblin.

[Amiraa]

2 patch update caused me to dc non stop 90k error, i am annoyed se don't even bother to address the issue no wonder people hacking them easy. I never had problem connecting to the game but been more than a week for me i dc 4-20+ times a day 5-10min.

[Squa11_Leonhart]

patches don't cause DC's or 90k's

Bad internet connections, bad internet routes, bad network configurations or modems causes 90k's.
DDOS Congestions cause 90k and lobby errors

Patches don't.

This thread always comes up after a patch, its never the patch - most often the issues on the route your isp chooses to take to the servers: (Many US ISP's are causing these issues by refusing to expand links to third party peering/content networks unless paid to do so).

[Tusembobel]

Well, what can I say? Seems SE absolutly doesn't care for players experiencing problems trying to play the game they pay for. I'm not whining, it's a fact. I've been having lag/freeze problem for the whole time since ninja patch had been released. I sent a ticket - no answer, but before chat guy told me, that my computer maybe was too shitty to play this god-like game. But my PC is new, my connection is fast FTTx.. No problems in other games, 60 fps almost everywhere on ultra-options. And now these constant 90k/2002. In yesterday's expert I got a whole set of lag/freeze/90k/3102/2002. Unbearable..
I love Final Fantasy game-series, but in current state I cannot enjoy the game - it's a struggle versus bugs and lags. The worst thing - SE won't care for us.. Q_Q

[Raist]

Well, what can I say? Seems SE absolutly doesn't care for players experiencing problems trying to play the game they pay for. I'm not whining, it's a fact. I've been having lag/freeze problem for the whole time since ninja patch had been released. I sent a ticket - no answer, but before chat guy told me, that my computer maybe was too shitty to play this god-like game. But my PC is new, my connection is fast FTTx.. No problems in other games, 60 fps almost everywhere on ultra-options. And now these constant 90k/2002. In yesterday's expert I got a whole set of lag/freeze/90k/3102/2002. Unbearable..
I love Final Fantasy game-series, but in current state I cannot enjoy the game - it's a struggle versus bugs and lags. The worst thing - SE won't care for us.. Q_Q

Other games are hosted elsewhere and you take different paths to get there. Traffic is heavier in densely populated areas like downtown NYC, LA, or Chicago than you are likely to find in most areas. And guess where most of our traffic gets thrust through? It is very much like taking a drive across country where you may run into a heavy traffic jam. Could be because of an accident, construction, foul weather, lowered speed limits, or simply just too many people crammed into too few lanes. The same things happen across the internet...some transit/peering segments are simply overly congested regularly.

Such things are out of SE's hand's to address. Period. It is up to your ISP and their peering/transit providers to work out these congestion issues. You are paying them to maintain these internet exchanges...need to get in touch with your ISP's tier3 support and push them for escalation to fix it.

[Moonwolfthegrey]

thanx for the simple explanation Raist, but why is the game lagging so much with all the 90k errors etc only these last 2 weeks?, before that they were extremely rare for me. and why are other internet activities smooth whereas only ffxiv seems to be affected.
does this mean all ffxiv related info travels on a different path to everything else on the net? is there another way to ease this lag etc without pushing isp support (frankly because they are so poor, and im not getting anywhere with them)

[Tusembobel]

This Raist guy posts are found everywhere on forums, and all of them are like - do not ask SE to do anything, there's nothing to do with SE, all of your ISP are shits..etc.. We are trying to tell each other our problems, not to hear your lections Mr. Raist. I want to play the game I pay for, not to battle through lags.. Guess who must provide me with such opportunity? I mean they do not even answer my tickets, do not try to find out the reason..

[Raist]

thanx for the simple explanation Raist, but why is the game lagging so much with all the 90k errors etc only these last 2 weeks?, before that they were extremely rare for me. and why are other internet activities smooth whereas only ffxiv seems to be affected.
does this mean all ffxiv related info travels on a different path to everything else on the net? is there another way to ease this lag etc without pushing isp support (frankly because they are so poor, and im not getting anywhere with them)

yes... your traffic is routed differently according to where you are going. Here's some sample routes to FFXIV and some posted WoW IP's:
(Source from Blizzard: https://us.battle.net/support/en/art...ceroute)<br />
199.91.189.30 (IP I use for Midgard, Registered to Montreal, Canada)

C:\Windows\System32>tracert 199.91.189.30

Tracing route to 199.91.189.30 over a maximum of 30 hops

  1     2 ms     1 ms    <1 ms  LPTSRV [10.10.100.1]
  2    28 ms    22 ms    25 ms  cpe-075-176-160-001.sc.res.rr.com [75.176.160.1]
  3    20 ms    20 ms    18 ms  cpe-024-031-198-009.sc.res.rr.com [24.31.198.9]
  4    19 ms    18 ms    20 ms  24.31.196.212
  5    24 ms    21 ms    24 ms  be33.chrcnctr01r.southeast.rr.com [24.93.64.182]
  6    28 ms    28 ms    27 ms  bu-ether14.atlngamq46w-bcr00.tbone.rr.com [66.109.6.82]
  7    27 ms    28 ms    28 ms  107.14.19.99
  8    29 ms    25 ms    26 ms  te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109]
  9    25 ms    26 ms    28 ms  be2050.ccr41.atl01.atlas.cogentco.com [154.54.0.165]
 10    41 ms    33 ms    36 ms  be2168.ccr21.dca01.atlas.cogentco.com [154.54.31.94]
 11    41 ms    40 ms    41 ms  be2148.ccr41.jfk02.atlas.cogentco.com [154.54.31.118]
 12    44 ms    45 ms    45 ms  be2106.ccr21.alb02.atlas.cogentco.com [154.54.3.50]
 13    49 ms    50 ms    49 ms  be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43.17]
 14    64 ms    62 ms    62 ms  38.122.42.34
 15    49 ms    50 ms    46 ms  192.34.76.10
 16    50 ms    50 ms    48 ms  199.91.189.242
 17    51 ms    49 ms    48 ms  199.91.189.30

12.129.209.68 (WoW, West Coast--registered to Long Beach, California)

C:\Windows\System32>tracert 12.129.209.68

Tracing route to 12.129.209.68 over a maximum of 30 hops

  1     2 ms     1 ms    <1 ms  LPTSRV [10.10.100.1]
  2    25 ms    21 ms    26 ms  cpe-075-176-160-001.sc.res.rr.com [75.176.160.1]
  3    29 ms    26 ms    27 ms  cpe-024-031-198-009.sc.res.rr.com [24.31.198.9]
  4    20 ms    17 ms    17 ms  24.31.196.212
  5    26 ms    27 ms    20 ms  be33.chrcnctr01r.southeast.rr.com [24.93.64.182]
  6    29 ms    25 ms    28 ms  bu-ether34.atlngamq46w-bcr00.tbone.rr.com [107.14.19.48]
  7    25 ms    28 ms    29 ms  107.14.19.99
  8    25 ms    24 ms    25 ms  216.156.108.45.ptr.us.xo.net [216.156.108.45]
  9    27 ms    26 ms    30 ms  67.111.23.90.ptr.us.xo.net [67.111.23.90]
 10    40 ms    38 ms    40 ms  12.122.29.54
 11    43 ms    39 ms    42 ms  cr2.wswdc.ip.att.net [12.122.1.174]
 12    37 ms    37 ms    40 ms  12.123.250.113
 13     *        *        *     Request timed out.
 <Security is preventing final hop from responding to tracert, just times out until it stops trying>

63.240.104.93 (WoW, North East--registered to Somerset, New Jersey)

C:\Windows\System32>tracert 63.240.104.93

Tracing route to 63.240.104.93 over a maximum of 30 hops

  1     2 ms     1 ms     1 ms  LPTSRV [10.10.100.1]
  2    22 ms    21 ms    18 ms  cpe-075-176-160-001.sc.res.rr.com [75.176.160.1]
  3    26 ms    16 ms    17 ms  cpe-024-031-198-009.sc.res.rr.com [24.31.198.9]
  4    19 ms    18 ms    19 ms  24.31.196.212
  5    23 ms    24 ms    25 ms  be33.chrcnctr01r.southeast.rr.com [24.93.64.182]
  6    30 ms    27 ms    26 ms  bu-ether14.atlngamq46w-bcr00.tbone.rr.com [66.109.6.82]
  7    27 ms    27 ms    29 ms  107.14.19.11
  8    26 ms    26 ms    27 ms  216.156.108.97.ptr.us.xo.net [216.156.108.97]
  9    28 ms    26 ms    26 ms  67.111.23.90.ptr.us.xo.net [67.111.23.90]
 10    44 ms    43 ms    47 ms  12.122.29.54
 11    47 ms    48 ms    50 ms  cr2.wswdc.ip.att.net [12.122.1.174]
 12    44 ms    46 ms    47 ms  cr2.n54ny.ip.att.net [12.122.3.37]
 13    44 ms    43 ms    43 ms  gar1.nw2nj.ip.att.net [12.122.130.93]
 14    45 ms    43 ms    45 ms  12.122.251.10
 15     *        *        *     Request timed out
<Again, Security at end is preventing a response to trace>

Notice the differences in the middle of the routes. I get paired with a different routing partner to get me to the AT&T network segments hosting their servers. Also note, that I am going through the same region on the way to FFXIV in Canada as I do to get to Wow in New Jersey, but the pathing is considerably different as well: XIV goes Atlanta, DC, Chicago, New York and WoW went to Atlanta, bounced a few hops before hitting DC, then went straight to New York. There is a protocol specifically for determining the best-effort delivery for routing you to your destination. Depending on how often the routes are analyzed and metrics adjusted, they may not be detecting the congestion spikes and you can get stuck with a bad route.

It's like routing through traffic on a long trip. You may pick a known good route based on experience with the trip you are planning, but bad weather, accidents, or some special event can cause unexpected traffic delays or jams and you need to adjust on the fly. IF no one gives you a heads up so you can adjust your route, you get stuck in traffic and arrive late---possibly even missing a scheduled appointment---and everything thing that was planned to happen after your arrival may now be delayed, postponed or flat out missed because you weren't where you were expected to be at the expected time. The same thing can happen with your packets on the internet.

The internet is constantly fluctuating it's traffic patterns. Look at the patterns with these tools from Akamai:
http://www.akamai.com/html/technolog...b-metrics.html
http://www.akamai.com/html/technology/dataviz1.html
http://www.akamai.com/html/technolog...b-monitor.html


Tons of things affect it minute by minute--solar flare activity, weather, increased usage patterns, power outages for unforeseen reasons, failing hardware, electro-mechanical interference from nearby devices in a not-so-well planned implementation, attacks on someone's server that is overloading a node.... The list can go on and on, and it can render a connection intermittently good and bad at the drop of a hat anywhere along your route--so every one of those hops is a potential point of failure. And I have short routes... by default, you can have as many as 60 hops between client and server. On average it's only one or two dozen, but it can technically go all they way to 63 hops until TTL kills a session. And you can have a problem at any one of those hops along the way, for a myriad of reasons.

[NoF2P]

There's been a lot of massive DDoS attacks against various online games and media lately. All Sweden went down for about 45 minutes not long ago due to the scale of it. It's probably attempted extortion.