Kraken Outage Map

  Check Current Status

Kraken is a US based prominent bitcoin exchange operating in Canada, the EU, Japan, and the US, and the world's largest bitcoin exchange in euro volume and liquidity.

Kraken Most Affected Locations

Outage reports and issues in the past 15 days originated from:

Location Reports
Phoenix, AZ 1
Maynooth, Leinster 1
Karlsruhe, Baden-Württemberg Region 1
Amsterdam, nh 1
Peoria, AZ 1
Wald, ZH 1
Zürich, ZH 1
Burnaby, BC 1
Mosbach, Baden-Württemberg Region 1
Birmingham, AL 1
Glendale, AZ 1
Inca, Comunitat Autònoma de les Illes Balears 1
Birmingham, England 1
Cape Town, Western Cape 1
Turin, Piemonte 1
Nijmegen, GLD 1
Cesano Maderno, Lombardia 1
Vienna, Wien 1
Liège, Wallonia 1
Tramonti, Campania 1
Dublin, Leinster 1
Gräfelfing, Bavaria 1
Minneapolis, MN 1
Madrid, Comunidad de Madrid 1
Kaiserslautern, Rheinland-Pfalz 1
Copenhagen, Region Hovedstaden 1
Roding, Bavaria 1
Paris, Île-de-France 1
Brussels, Bruxelles-Capitale 1
Tirana, Qarku i Tiranës 1

  Check Current Status

Kraken Comments

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Kraken Issues Reports

Latest outage, problems and issue reports in social media:
  • Jon Phillips (@jrichphillips) reported

    @jespow @JonnyMoeTrades @ChainWho @Jomarvel12 @krakenfx The exchage error kicked off the events that occurred after. That's the problem. The fact they executed "properly" based on a faulty input is immaterial.

  • Jesse Powell (@jespow) reported

    @jrichphillips @JonnyMoeTrades @ChainWho @Jomarvel12 @krakenfx I'm not sure how "a legitimate trade for pricing purposes" is defined. Agree that matching at trade to the wrong side of the book is an exchange error. Everything that happened after that worked as expected. Trade printed, stops triggered, other orders matched just fine.

  • Jon Phillips (@jrichphillips) reported

    @jespow @JonnyMoeTrades @ChainWho @Jomarvel12 @krakenfx I'm not following your logic on this. If order matching skips 20% of the orders on the books, that can't be considered a legitimate trade for pricing purposes. That's an exchange error. By your team's own admission, the orders matched to the wrong side of the book. That's on you.

  • Jonny Moe (@JonnyMoeTrades) reported

    @jespow @ChainWho @jrichphillips @Jomarvel12 @krakenfx Wasn't affected, but as an active trader I can say this: triggering stop orders up to 20% away from the actual market price because the exchange reported an incorrect market price is, to put it plainly, a big ******* problem

  • cryptofrappachino (@CryptoFrappe) reported

    @krakenfx Testing in production FTW! From the exchange that gave us a trading engine slower than mtgox and a multiple day outage while they upgraded it with no comms to customers!

  • LisaCoin (@LCoinn) reported

    @krakenfx Error again. I’m using barginex because no problem

  • Chan-Ho Suh (@chanhosuh) reported

    @bobanmil @jespow @NigelEvans4219 @krakenfx Yeah, that caught my eye too. I worked on a trading system and we always had redundant checks, and yes, they slowed things down, but we figured better safe than sorry... on the other hand, it was our company's money at risk, not clients...

  • Ahmad Dukhan (@dukhans) reported

    @krakenfx WTH, do you have test units for the code. An exchange your size should be following the basics of best practice testing. How about TDD as seems these issues never stop happening at your Ex Looks like you guys test live and don't have a sandbox. You should compensate

  • ETHΞAD (@pumpdumpalts) reported

    @rotkehlchenio @LefterisJP @krakenfx If someone proves they had a buy order set at lets say 9k that didn’t get filled, only then does kraken have a problem that needs to be investigated.

  • Crypto Fam Brad (@CryptoScottyStu) reported from Phoenix, Arizona

    @trajanmex @krakenfx The one time I needed a lack of liquidity on kraken, it didn't happen. Which is probably telling of foul play on other exchanges When BTC ripped through 6k, I had shorts in the mid 8ks that filled. I set buy orders to close at $6200. Every exchange wicked down, except kraken.

  • Max Boonen (@maxboonen) reported

    @krakenfx your websocket is down

  • Adam James ⚡🔑🎮 (@Shasdam) reported

    @CryptoMichNL It's legitimately absurd that people even thought for a second that said wick was some kind of actual whale-driven whipsaw. All anyone had to do was check @krakenfx 's outage tracker to see that it was an obvious bug.

  • PanAnalytics (@Chalet_spar) reported

    @derrick198S @SalsaTekila @trajanmex @krakenfx yeah, it wasn't a real move, it was a printing error.

  • Selam Levinas (@selamlevinas) reported

    @RJ_Killmex @SmartContracter That was only a chart print error and afaik no stops triggered. I had no open positions on kraken but saw many people saying this. @krakenfx @krakensupport needs to officially clarify this though, too much fud.

  • Ultra XBT (RIP AP_Trades) (@UltraXBT) reported

    @aBlock0 @bit_cosby @cryptoSqueeze @krakenfx @krakensupport No, it filled my market take profit order at $11,500... but it filled it at $10,200, a few bucks below my entry. Order slipped $1300, essentially. I took all my funds off of kraken. Didnt lose much from it because price went up before down, but not worth it

  Check Current Status