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:
  • WFS (@_the_bull) reported

    @krakenfx It's is a bit of the world in reverse that the owners need to go to support if it's your fault in the first place. I mean you know who was involved so could fix it yourself...

  • 🇧🇪 Pinarello⚠️🇧🇪 (@pinarello) reported

    @bobanmil @krakenfx they lie i was liquidated and they refuse to talk or setle the problem

  • sam3794213 (@StylesGrant) reported

    @krakenfx This could have been prevented with a price band control like deribit, this isn' the first time, or the 20th time this has happened to a degree on kraken. This is an issue specifically problematic on kraken.

  • Alex S (@szeremeta) reported

    @krakenfx love your exchange and am a long time user. All of the money you spend on marketing makes you look stupid when easy engineering problems remain unsolved. Ex poor UX on mobile, poor app etc.

  • allyourbase 💰 (@allyouracid) reported

    @emalamisura @jespow @krakenfx A "unit test" isn't some fancy magic which uncovers/prevents any and all errors which might happen. You have to set up the tests for certain cases, e.g. to test your components, return types etc. And by no means does a well written test of a component ensure there's no errors.

  • Denakos (@denis_ve) reported

    @krakenfx @Poloniex faced some technical issues, and all they did was to hide behind their finger. Traders could not close their margin positions and got liquidated. Reply was that they acknowledged the error but can not refund as its traders risk...

  • 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.

  Check Current Status