So when does SE plan to credit our accounts for the multiple ongoing service issues?

[Alien_Gamer]

Well to be fair the ddos attacks are not the only issues at hand, it is also the very bad coding and the not so great servers SE still use, lol
Granted yes ddos attacks are not a SE thing but we still have issues from time to time when not attacked

SE servers were upgraded in the move, the hardware isn't a bottleneck in this issue. The game's back end is horribly antiquated but also irrelevant to this issue. The problem is with the connection between the datacenter and customers; the game itself has remained fairly stable during this. So to be fair, this is not SE fault and we deserve no compensation from them.

[ManuelBravo]

Well to be fair the ddos attacks are not the only issues at hand, it is also the very bad coding and the not so great servers SE still use, lol
Granted yes ddos attacks are not a SE thing but we still have issues from time to time when not attacked

Seems kind of odd when you think about it. Last time there was a DDOS attack every server was being effected, now it seems some people are affected it could be a DDOS. I doubt is SE most likely its local/user net connection/band being congested. Some internet companies throttle their connection based on usage/time of day/ hot zone location/. It could also be do to multiple users sharing a line that can cause those DC. I use to have that problem back in the day until I said EF it, got an individual line for my gaming. It's rare I even see any lag now. If it does DC is normally do to internet company issue. Coding may have something to do with it in the back end true, not likely though in this situation.

[Rymm]

Seems kind of odd when you think about it. Last time there was a DDOS attack every server was being effected, now it seems some people are affected...

It's pretty well established at this point that it is a DDoS attack. The difference between the DDoS at Stormblood's launch and now is that this time FF14 is not being directly attacked. They are attacking SE's ISP, which is why only users in certain areas are having issues and why it's not just FF14 that is being affected. And also why SE is not responsible and "owes" us, the customers, nothing. The last 10 pages of this thread have repeated this ad nauseam.

[silverlunarfox]

The issue is these interruptions arent affecting everyone. Out of everyone I know, I have had maybe one issue of a server boot, one of the mass disconnect during the worst of the DDoS attacks last week. I have however watched when half my RC hit the lag spikes, while the other half had no issue (including myself). I have my dungeon parties have at least one or two people lagging all over, and I have been fine.

I wouldn't feel right receiving a credit when I myself haven't had issues, and the ones I've had are negligible in the grand scheme of internet gaming.

[Lorglath]

It's pretty well established at this point that it is a DDoS attack. The difference between the DDoS at Stormblood's launch and now is that this time FF14 is not being directly attacked. They are attacking SE's ISP, which is why only users in certain areas are having issues and why it's not just FF14 that is being affected. And also why SE is not responsible and "owes" us, the customers, nothing. The last 10 pages of this thread have repeated this ad nauseam.

I don't think SE "owes" us anything, and it doesn't really sound like most people suggesting this think that either. At some point there comes a time that regardless of the reasons this isn't SEs fault, people will start dropping subs. Just from my own experience it's rare that I can go 30 minutes in an instance without seeing a couple big spikes where half the group shows as DCing. Again, it doesn't matter if it's SE's fault or not, at some point people just won't want to deal with it.

[ManuelBravo]

It's pretty well established at this point that it is a DDoS attack. The difference between the DDoS at Stormblood's launch and now is that this time FF14 is not being directly attacked. They are attacking SE's ISP, which is why only users in certain areas are having issues and why it's not just FF14 that is being affected. And also why SE is not responsible and "owes" us, the customers, nothing. The last 10 pages of this thread have repeated this ad nauseam.

Point is SE does not owe us anything,. It is placed in their terms of use. We all pay our subscription and we are all vulnerable to this situation. People need to stop bitching and realize in the online gaming world this is to be expected. I never said they owe us anything. If anything I have mention this prior,

[Claviusnex]

SE's back end is pretty standard. Most databases can only handle about 5000-10000 connections at once, which is why SE's server cap is 5000 players at a time, with the lobby server slowing things down to 100 new connections per minute. The servers themselves are pretty stable, only crashing completely once ever few weeks. When it's their fault, SE admits it was a "server programming error" in the recovery notes, usually some bug that caused a memory leak or somesuch.

The network infrastructure itself isn't that great, but again it's also industry standard. Every character is a constant query upon 3-4 servers as we navigate between duties, instances, party finder, etc. They could lift the query cap on the database, but past experimentation has found that the database gets gummed up at 5000+ characters, and that matches my own experience in a development environment whereupon a relationship database chokes and dies beyond 10,000 simultaneous queries. We keep our Oracle databases capped at 10K as well.

Actually there are many systems that handle many more connections and DB queries with ease. For the stuff I worked on most of my career having 20K-50K concurrent users per image was not uncommon. I also worked with some large database design and we could easily get well beyond 10K transactions per second. It typically isn't the DB or operating system software that is the limiting factor but the hardware and application itself. Given the little I know about FF XIV's environment I would say they are hardware constrained and some of that constraint is due to poor application design. I would also say some of the hardware constraints are also based on how much SE is willing to spend in relation to profit margins. So forgoing the DDoS issue which is not their problem SE could probably improve game performance if they were willing to invest in it.

I just want to add onto the DDoS attacks a bit. While SE is using NTT for their backbone access it is important to realize they are not the only backbone provider to be attacked. L3 has also had DDoS problems over this same period of time. L3 also had a routing error that affected Comcast customers during this same time frame. So the current problems really are beyond the control of SE.

[Rymm]

I never said they owe us anything.

I never said you did. The reason I quoted you in my post was because you seemed to believe that it wasn't a DDoS attack because it wasn't affecting the same people (i.e. everyone) as the last big attack. You even posted several alternative problems you thought might be causing it. I was just correcting you that it is, in fact, a DDoS just with a different target (hence the discrepancies with the last one.)

The comment about SE not owing us anything was just to clarify my own stance on the subject.

[Kerwin]

Lol, then it will never be enough. He is the official representative for them regarding network issues, you aren't going to get a more official statement than what he gives. Yoshi may be the guy in charge but he won't be giving any different information than what Noc is posting.

https://na.finalfantasyxiv.com/lodes...7d341dbcf750b1

There we go. That wasn't so hard. A little extra response goes a long way.

[Raikki]

Also for DDoS attacks? Wouldn't it be seen as a sign as just do more DDoS attacks to get more free stuff?

The black market value of a weeks-long sustained DDoS campaign grossly exceeds whatever small trinket of compensation the playerbase would be satisfied with.