Well, I can relate to your experiences and laid out the problems for whom (traders) and the main issue with their website is. Personally, I have no serious issues using Kraken and until now have great experiences with their support team. Yes, it's annoying to spend a good 5 minutes to get an order in lately, but I'm not daytrading anymore, because I couldn't close a short position as well (with profit) and ended up with a loss in the heat of the moment 10 minutes later. Compared to their competitors who deal with euro fiat, Kraken still is by far the best than the very few alternatives, unless you like to make selfies when you withdraw a good amount of fiat each time, which imho is childish and makes me want go back to the stock market, which I'm not. Like I said, why not use Kraken for short term trades and/or investments, rather than daytrade until the problems are fixed. If your living depends on daytrading, you can use the exchange you want and sent it to kraken to withdraw to fiat. I don't see the problem here, unless withdrawals are disabled for sustained periods of time.
I have spent the last hour (8-9AM GMT) trying to close a short position which was on profit and just closed it now on LOSS...thx...
@crypt0dude I'm very familiar with scaling challenges and Kraken does not have a "http requests" problem but a strategy/management one. You cannot handle peoples money this bad for so long. There is no transparency with what is going on, no communication, no time-frame, nothing etc. "Our dev are working hard on fixing" is not an answer. You cannot have your dev team work on your site on "black-friday" to optimize/scale it, you have to prepare for that long before.
Looking at trading volume kraken has more than $3mil monthly revenue, renting 100x high performance physical(baremetal) servers not that virtual machine rubbish, costs no more than $40k(which is obviously overkill). So why are we getting so many cloudflare errors? Api-enpoint failures? Is it because key systems where designed to scale just vertically or because they didn't bother to automate the horizontal scaling process and now is failing!?
I have registered specially to post this because recent comments said that things might have gotten back to normal which is just not true.
I hope Kraken get's back on track soon, but in the mean time somebody should tell us what is going on!!
Well, that's a pretty self defeating argument. As I've said, you cannot scale on http requests (which makes me think you don't know the difference between websockets vs http)... unless you want to make it more slow and eventually dos it. If you're so familiar with scaling challenges, you'd have agreed with me that web sockets is the way to go... and it's not that this is not known and being used by others. Renting more servers (scaling) does nothing when your fundamentals (networking stack) are not right. You cannot build a house on sand, build new rooms next to it to increase capacity and expect it will get better than it get worse. Just my 2 cents.