1. Home
  2. Companies
  3. Kraken
  4. Outage Map
Kraken

Kraken Outage Map

The map below depicts the most recent cities worldwide where Kraken users have reported problems and outages. If you are having an issue with Kraken, make sure to submit a report below

Loading map, please wait...

The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.

Kraken users affected:

Less
More
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.

Most Affected Locations

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

Location Reports
Paris, Île-de-France 1
Bordeaux, Nouvelle-Aquitaine 1
Valence, Auvergne-Rhône-Alpes 1
Stockholm, Stockholm 1
Check Current Status

Community Discussion

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

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

Kraken Issues Reports

Latest outage, problems and issue reports in social media:

  • afanazizoutbind
    Afan Aziz (@afanazizoutbind) reported

    DAY 10. STILL NOTHING. 10 days since @krakenfx blocked my funds. 5 days since a human finally responded and said my case was being escalated to a specialized team and still zero actual resolution. No access to my funds. Just another generic “we received your request” email.

  • BMess181
    Bob.DGB (@BMess181) reported

    @krakenfx Sell that garbage

  • Recovery_Daniel
    Daniel Castillo (@Recovery_Daniel) reported

    Investor Caution: #AscendEX #Kraken #KrakenFX Before investing, conduct proper research and verify platform details independently. If your withdrawal remains pending or stuck, keep all transaction records, wallet details, and support conversations secure. Message me to discuss your situation and explore possible recovery options.

  • urban_meyerr
    urban meyer (@urban_meyerr) reported

    @PardonMyTake @krakenfx Missing pumpkin patch during football season is terrible.

  • SaltySheriKoko
    Salty Sherry (@SaltySheriKoko) reported

    @Timmcgrew91 @caniok1111 @krakensupport Don’t even try to get help here. They are scammers. My Kraken funds were held for 90 days. I got scammed trying to fix it

  • Shibain23980681
    LAO (@Shibain23980681) reported

    @krakenfx Sold immediatly this ****

  • cryptoslshy
    Cryptoslshy (@cryptoslshy) reported

    @krakensupport App is still buggy for me. Delayed and slow. Signed out and signed back in and its actually stuck signing me in. Web version also doesnt show full account - are you sure the maintenance is comolete?

  • John95172987954
    John (@John95172987954) reported

    @krakensupport @krakenfx @Krak u/KrakenSupport I sent £1,200 by bank transfer for a P2P trade. The recipient’s account was then restricted, and my payment is now stuck. I’ve asked for days for it to either be credited to the account holder or returned to me. Can you help?

  • JW_WWJD
    WWJD (@JW_WWJD) reported

    Kraken Funded — can someone explain this? I’ve been experiencing unusually fast losses on my Funded accounts, so I started documenting the pricing. These two screenshots were taken at 6:00 PM — same token, KAITO, inside Kraken. Regular Kraken: $0.7211 Kraken Funded: $0.7008 That’s about a 2.8% difference at the exact same time. Earlier today I documented even larger discrepancies of roughly 8–9%. When a Funded Challenge has strict maximum-loss limits, these price differences can have a major impact on whether an account survives. This has happened repeatedly over several days and across two of my Funded accounts. I’ve contacted Kraken Support and asked for a formal investigation. I have timestamped screenshots documenting everything. I’d like an explanation of what price feed Kraken Funded is using and why it differs this substantially from Kraken’s own displayed market price. @krakenfx Please investigate and rectify this.

  • Algloverand
    Joseph Glover (@Algloverand) reported

    @krakensupport The issue is that it is possible to get filled $10,000 away from the spot price after setting a $10 stop loss. It's absolutely ridiculous and there is no reason why a person should be liquidated at such an extreme price.

  • toledanogonzalo
    Xavier Xemard (@toledanogonzalo) reported

    @IanKipc43248389 @krakensupport @elrobadv Hi! 👋 Let me know if you need any help. I’m here to support you.

  • SaltySheriKoko
    Salty Sherry (@SaltySheriKoko) reported

    @moropeza1930 @krakenfx Kraken was holding my btc for 90 days. I tried to get help and was scammed.

  • CryptoMemeRaj
    Raj (@CryptoMemeRaj) reported

    @krakenfx this is how you actually handle scam calls, smart ****. now if only my own sanity could get a verification code lol

  • powerman1973gm1
    Powerman (@powerman1973gm1) reported

    @krakenfx I write the Kraken Support that there was a wrong transaction to my account.

  • JW_WWJD
    WWJD (@JW_WWJD) reported

    this? I’ve been experiencing unusually fast losses on my Funded accounts, so I started documenting the pricing. These two screenshots were taken at 6:00 PM — same token, KAITO, inside Kraken. Regular Kraken: $0.7211 Kraken Funded: $0.7008 That’s about a 2.8% difference at the exact same time. Earlier today I documented even larger discrepancies of roughly 8–9%. When a Funded Challenge has strict maximum-loss limits, these price differences can have a major impact on whether an account survives. This has happened repeatedly over several days and across two of my Funded accounts. I’ve contacted Kraken Support and asked for a formal investigation. I have timestamped screenshots documenting everything. I’d like an explanation of what price feed Kraken Funded is using and why it differs this substantially from Kraken’s own displayed market price. @krakenfx Please investigate and rectify this. @krakenfx

Check Current Status