[ANN] KRAKEN.COM - Exchange with USD EUR GBP JPY CAD BTC LTC XRP NMC XDG STR ETH

[gotmilk_]

Not good!!!

[1713880719]

1713880719

[1713880719]

1713880719

[soullyG]

I could expect this from somewhere like Cryptsy or Btc-e but this is really unacceptable for a "professional" exchange like Kraken

[Dargo]

Hi all - we understand your frustration and will be doing what we can to increase protection against DDOS. DDOS protection is only a matter of degree though and no matter what you do, it's still possible for someone with enough resources to successfully attack. Unfortunately there are people out there who can't make money on their own trading/investing skills and have to resort to this crap in an effort to make a buck. 

[poordude]

when even btc-e starts looking tempting, you know your own exchange has some big issues

[KrakenTrader]

Hi all - we understand your frustration and will be doing what we can to increase protection against DDOS. DDOS protection is only a matter of degree though and no matter what you do, it's still possible for someone with enough resources to successfully attack. Unfortunately there are people out there who can't make money on their own trading/investing skills and have to resort to this crap in an effort to make a buck. 

Dargo,

Absolutely. If someone wants to get your site down, they probably will be able to do so depending on how much resources they are willing to use against it.
You said "...[we] will be doing what we can to increase protection against DDOS..."

Question:
Is it possible to be more specific, without giving out knowledge to potential attackers?

[Dargo]

Just about everyone should have access now, though the DDoS is ongoing and some may still experience zero or slow access.

To answer KrakenTrader's Q above, I don't have any information I can share at this time, but we always strive to be as transparent as we can so long as it doesn't compromise security. So I'll see what I can do to share info about improved anti-DDoS measures later.

[Serpens66]

the DDOS starts exactly to the moment of the big price movement?? (right now)

[Morecoin Freeman]

the DDOS starts exactly to the moment of the big price movement?? (right now)

That is exactly what I pointed out too:

It seems like you guys at Kraken can't handle the volume lately...

However, Kraken claims that the trade volume and this problem are not related.
I am not sure what to believe.

[becoin]

the DDOS starts exactly to the moment of the big price movement?? (right now)

That is exactly what I pointed out too:

It seems like you guys at Kraken can't handle the volume lately...

However, Kraken claims that the trade volume and this problem are not related.
I am not sure what to believe.

I don't believe there are DDoS atacks. The 'DDoS' attacks, as Serpens66 pointed out, always coincide with strong price movements. Kraken's customers can't take advantage of obvious trading and arbitrage opportunities. Usually this is unmistakable sign of insider manipulating profit taking and margin liquidation price levels.

[gotmilk_]

WHERE IS YOUR SUPPORT?

[KrakenTrader]

the DDOS starts exactly to the moment of the big price movement?? (right now)

I experience the exact same behavior. Once price movement gets heavy, it starts lagging and then ... site becomes inaccessible.
After heavy price movement is over, site becomes accessible again.
And exactly this lets many of us think twice about the officially reason given (DDoS).
Whatever it is, I am sure tech staff is working to resolve it. Why? Because it's a normal thing to do for professional folks at Kraken.
After all, Kraken's reputation is at stake here.

Problems happen, but it's the way how to deal with / solve them, which sets a company apart from the rest.


Release the Kraken !
Cheers

[KrakenTrader]

I don't believe there are DDoS attacks. The 'DDoS' attacks, as Serpens66 pointed out, always coincide with strong price movements. Kraken's customers can't take advantage of obvious trading and arbitrage opportunities. Usually this is unmistakable sign of insider manipulating profit taking and margin liquidation price levels.

No way that Kraken would risk doing just that. (IMO)
Plenty of other possible bottlenecks "could" play a part  (just brainstorming here) :
Just to name a few:
- server/hardware configuration/setup (tweaking/upgrade needed?)
- database processes handling (tweaking needed?)
- general coding (rewriting parts of code to use resources more effective - that takes long but often makes the difference)
- Cloudflaire protection filter tuning (balancing between fastest possible access of clean traffic while malicious traffic gets blocked)
etc etc.





(edited for wording)

[Dargo]

Hi All,

We've been under DDoS all day (since about 5 am PDT). We managed to mitigate it pretty well but it never went away, has varied in intensity, and still impacts site performance. Whoever is doing the DDoS is probably doing it to manipulate price and of course they are going to try to cause trouble right when the market starts to move and is most ripe for manipulation. Also, heavy trade action puts more load on our resources and, when we're also under DDoS, could contribute to the site being less responsive.

So, yes, there's a correlation right now between site access/performance and heavy price action. I'm not sure why people think this correlation is reason to question the DDoS explanation because the explanation fits perfectly well. Sure, there are other explanations that fit too, and ultimately we can't prove to you that it's in fact DDoS and not something else. I understand why people are inclined to distrust exchanges though in light of history.

We are investigating to see if we can find a connection between the DDoS and trading on our site and will take appropriate action if we can identify someone, but it may be very hard to do so.

As I already mentioned, we will also further enhance our DDoS protection. But DDoS protection only comes in degrees, so making it stronger can't rule out the possibility of being impacted by a larger attack.

 

[gotmilk_]

Dargo. Please check request 65448. Thank you.

[becoin]

Whoever is doing the DDoS is probably doing it to manipulate price and of course they are going to try to cause trouble right when the market starts to move and is most ripe for manipulation.

If your website is down and API unaccessible how is price moved? Who can place market orders while all the rest can't? Why the attackers are so confident they can trade at Kraken while all the rest can't?

We are investigating to see if we can find a connection between the DDoS and trading on our site and will take appropriate action if we can identify someone, but it may be very hard to do so.

Is there a customer or group of customers that have privileged access to your trading engine? They must also have access to the order book, including hidden orders! They can profit only if they know at what price level majority of 'take profit' and 'margin liquidation' orders are grouped.

[gotmilk_]

Whoever is doing the DDoS is probably doing it to manipulate price and of course they are going to try to cause trouble right when the market starts to move and is most ripe for manipulation.

If your website is down and API unaccessible how is price moved? Who can place market orders while all the rest can't? Why the attackers are so confident they can trade at Kraken while all the rest can't?

We are investigating to see if we can find a connection between the DDoS and trading on our site and will take appropriate action if we can identify someone, but it may be very hard to do so.

Is there a customer or group of customers that have privileged access to your trading engine? They must also have access to the order book, including hidden orders! They can profit only if they know at what price level majority of 'take profit' and 'margin liquidation' orders are grouped.

The same moment that happened to them, they should stop the trading. Many got margin called, while they were unable to close the positions because their site was unavailable!

[Slavewarrior]

Dargo can you please check request 65457. It`s very urgent. Thanks a lot!

[Dargo]

Dargo. Please check request 65448. Thank you.

I've alerted support to your request and they will respond as soon as they can.

[Dargo]

Dargo can you please check request 65457. It`s very urgent. Thanks a lot!

I've alerted support to your request and they will respond as soon as they can.

[InvestorPerson]

action starts, and kraken goes belly up 

bad habit for a business