I left Kraken last year due to their extremely bad service, but most important due to their unreliable trade engine. A buddy of mine told me that things were going better so I re-started trading on Kraken a month or 2 ago. However, the faults (even though they were a bit less often) were the same as when I left, maybe a bit less than last year, so one could argue that it was almost on an acceptable level. Nonetheless, from my perspective they did not solve an ancient problem. And from this week on we are definitely at the same level as last year.

And about the support, they give the same dronish answers as before, they might have gotten faster at replies, but the quality is even less than before. A social bot would suffice. And even worse, Kraken uses the same type of excuse for their bad service as the last time, only this time they have a fancy new website. So no, nothing has really changed at Kraken over the past year(s). ROFL. It is the same shitty trade engine and the same sort of dronish support without any relevant competence nor interest to actually solve these problems. But have fun trading there. I will just take the profits from this week, and move my funds to better and more reliable exchanges. (as also Totscha advises)

@LeGaulois: There is an almost countless number of exchanges which have better trade engines. Maybe they had some issue is in the past, but at least they fixed the issues and one can now reliably place and cancel orders without problems, even at the highest volume peaks.

Those issues are probably not update related, as they have been present long before the update and are regularly happening. And these issues have been going on for years, just proving that Kraken does not take care of the important problems.
Almost every other exchange provides a better and more reliable trading engine and a more competent service team than Kraken.
Again, STAY AWAY. LOL Kraken-Chase, just another Septimus.

Attention to all Kraken users and people wanting to use the platform.

Kraken's trade engine on Cryptowatch as well as using API calls is not worth the effort. STAY AWAY if you do not absolutely need to trade there.

Endless error messages, often being unable to place and/or cancel orders. In addition there have been serious funding issues in the past, in particular massive delay in funds transactions. Maybe these are solved right now, but just look at this thread in the past. But usually Kraken does not give a damn when a customer experiences problems. They even keep the trade engine running while knowing that the are massive problems for their users. Could be a schema to rip them off, who knows.

From experience in the past it can be said that Kraken has one of the worst service teams in cryptoland, and their trade engine is even worse. For years they know about several mayor issues, and so far they have not solved any of the problems.

Dont say you have not been warned when you have read this post.

ROFL.
Nope, these questions can and should be discussed here. In particular as they concern an earlier statement of Septimus on recognition of false and real peaks. An open discussion might be of interest to every customer, especially as they are about market manipulation.
And from own experience, opening a ticket does not lead anywhere, as you simply ignore them. Been there before.

About the informants ticket. How many times do you want to repeat this lie? The last email communication from your side to our informant about  this case is roughly 1 month ago. And let's not start on earlier cases, then Kraken's denial to solve this problem is going on for much longer. And your answer here is particularly questionable, because Kraken claims to know what the cause of the problem is. You simply just try to solve the case by doing nothing. Yeah. Kraken is taking this issue VERY serious. LOL (Just look back for how long this type of issue is being discussed here in this forum. Same problem reoccurring again and again, and always the same type of answer and no improvement by Kraken.)

Case remains unsolved. no email communication to our informant about his case, and also no answers to the questions in the previous post.

Yep, it is always the same with these Kraken frauds. Since, no communication has happened, it must be assumed that no one from Kraken is actually doing something about this issue. In other words, it is a lie that a specialized team is taking care of this case. Unless it is the special "lets-ignore-unfavorable-customers-requests" team. Then they are doing an excellent job. ROFL.

Still no news from your side to our informant, not even a status update. Seeing this it must be assumed that the statement that Kraken is taking care of this issue is a plain lie. Furthermore, please keep in mind that this type of issue is occurring on a regular basis, which makes your statement even more questionable.

Our own questions also remain unanswered. Could you please tell which of the previously mentioned peaks are real, and which are false?
These questions are not ticket specific and can be discussed here in the forum. Furthermore, the verified false peaks still show in the charts. LOL. The manipulation continues.

You know what the fault is (at least according to previous info), and your "specialized team" still needs this long to give an adequate answer? Your surely taking your time. Just raises more doubts about Kraken taking this issue serious.

Furthermore, the general questions in the previous posts which are not case specific remain unanswered.

Our informant is still waiting for an answer, so much for taking this issue serious. The last email he got was more than 3 weeks ago.
Furthermore, as long as the data shows these peaks/dips every customer must assume that these peaks are real. Especially when Kraken does not issue an official statement that warns ALL its customers about these occurrences. Therefore, claiming refunds and/or compensation is more than justified.

Do I understand you correct that one could distinguish between real and false peaks by taking a look at the volume? Thus a peak/dip with very low volume is a false peak/dip, and if it is real it is paired with a large trade volume.

Taking a look at the ETH/EUR peak on June 19 using a 1 h interval, the volume is rather low for this type of peak, especially when comparing to the dip on June 22th which is paired with a rather high volume. However, we need to put ourselves in the situation on June 19th. So, we only look at trade data before the peak and neglect the trade data after the peak. Then the volume is not particularly low, actually it is higher than in most other 1h intervals within the last 48h.

After taking a look at the Dash/BTC market, we could further test this way to distinguish between real and false peaks. 1h intervals are used as it is not possible in Cryptowatch to go back to all peaks using a 15min interval. Times are given in CET.
1)   June 29 04:00-06:00 a double peak of 2.5% with very low volume: Real or not real
2)   July 3rd around 08:00 a peak of 1.5% with a bit higher volume: Real or not real
3)   July 4th around 08:00 big dip and peak, both roughly 4%, relative high volume: Real or not real
According to your way to distinguish, the first is a false peak, as the volume is rather low, and peak 2 and 3 are real because they have relative high trade volumes.
Am I correct, or is number 1 also a real peak?

As you might see, the way to distinguish does not guarantee a correct result. And even if this technique would yield a guaranteed correct result, it seems a bit odd that traders need to check your data for consistency in order to know whether the data is real or false.
Last, but not least. You are right. A misprint/mistake can happen. However, if one is responsible and is aware of a fault then one should try to correct it. Especially, when your customers trust you to display correct OHLC data. Let's not forget that customers pay fees for your service. Furthermore, this mistake is happening on a regular basis since more than a year. Therefore, I doubt that Kraken has taken this issue seriously.

Interesting, so it is a "misprint" again. At least you are now in line with the Kraken support. If your statement can be trusted is another issue. You have lied before, so why shouldn't you do so again? A bit suspicious, because Kraken seems not to be able to check their data for consistency after server restarts. A year should have been enough to build some kind of automated check whether the data is correct or not. And this is issue is going on for more than a year.

Then regardless of what is happening to the ticket, I still have the question why you (Kraken) are not correcting the OHLC data? As long as you knowingly present false/faulty OHLC data you are conducting market manipulation, at the very least by neglecting to correct. Those peaks create a very deceptive picture for traders. And since countless occurrences have been reported to you since the very least May 2017, you are knowingly (maybe even intentionally) presenting false data.
(Note: This is a general question, and not about the ticket itself, so it should be no problem to answer it.)

Just for your info: "Manipulation according to SEC https://www.sec.gov/fast-answers/answerstmanipulhtm.html
Manipulation is intentional conduct designed to deceive investors by controlling or artificially affecting the market for a security. Manipulation can involve a number of techniques to affect the supply of, or demand for, a stock. They include: spreading false or misleading information about a company; improperly limiting the number of publicly-available shares; or rigging quotes, prices or trades to create a false or deceptive picture of the demand for a security. Those who engage in manipulation are subject to various civil and criminal sanctions."

About the ticket. Then let's hope you (or someone else from the Kraken support) will reply there. To my knowledge our informant is still waiting for a reply to his last email about this case.

hey septimus,

do you remember this issue (actually the same as the current one). According to our info Kraken still denies to pay refunds/compensation for the case on April 3rd, or better let's put it this way, Kraken just does not reply to email communication about this issue, not even the legal department. Additionally, according to you the issue on 3rd April was a misprint, but the OHLC data of that day still shows the false peak. Are you going to take as much care of the current case as you did for the one on 3rd of April?

Maybe you really could finally clarify how a customer can distinguish between false and real peaks. For the problem on 3rd April you claimed it to be false peak, for the similar issues on May 24th and June 19th you call the peaks real (whereby the Kraken support claims they are false).

Furthermore, you never answered the questions posted about the issue on 3rd of April.

So, actually everything give the impression that Kraken does not care to solve this problem.

Just checked with the informant. He hasn't been contacted by you, Kieren, or any other Kraken representative yet. Any news from your side Septimus?

Don't know whether you have the right one. Let's hope you do. Maybe just take care of all cases regarding this type of issue. Still, the contradictions of you and the Kraken support are interesting.

Please stop pretending. Our informant is being denied any kind of refund and/or compensation, even after contacting the legal departemnt after the initial contact with your pretense of a support. Kraken simply ignores answering the follow up emails. LOL, this is turning kind of funny Septimus.

And the issue is clear. Open positions were not closed even though Kraken's OHLC clearly shows those positions limits were clearly passed. The support claims no trades took place, so no closing of positions.... This means you display false OHLC data. And the same type of problem was reported several times over the past year. We even had contact about this issue here in the forum.

Now you claim, that the peaks are real. Maybe you can answer this general questions then. So, if this should be true, don't you agree that our buddies open positions should be closed when they were in the peak and opened before the peak?
And why does the Kraken support then tell that no trades took place in first place?

This is all very very weird. Don't you think?

This is a plain lie Septimus, either by you, or by the support team towards our informant. The support team claimed that no trades took place on both dates. and our informant has evidence that his open positions in those peaks were not closed. Furhtermore Kraken denied closing his position with the argument that no trades took place in those peaks.

So, either you are lying here in the forum, or the customers support is lying towards our informant. Neither of the possibilities looks well septimus.

If you want we can post screenshots showing the peaks and the non traded positions including the indications which clearly show the positions were opened
before the peak.

Case still not resolved, you freaking frauds. Please solve. This manipulation is now going on for at least almost a year. Actually none of the cases about this problem were solved.

if you can, then stay away from these frauds.

If you still have funds on your account, withdraw them ASAP after having access again.

Why do you suggest opening a ticket if Kraken does not care to take care of this problem? Again, why does Kraken still not keep to its own Tos? As far as we get it Kraken still denies to pay refunds and/or compensation when it is clearly Kraken's faults. Furthermore, why does Kraken not correct the OHLC data, and why are customers not informed about this issue?

Apparently we are not the only ones having doubts about your trade data. The CFTC seems to be interested in your data as well and apparently this lead to the start of an investigation on illicit trading practices. Please see the linked article on Coindesk https://www.coindesk.com/cftc-demands-crypto-exchange-data-in-market-investigation/