Skip to content

Outage tracker / Kraken

Is Kraken down?

I'm having a problem

Operationalchecked 7 minutes ago

We reached Kraken from all 10 regions we check.

As of Oct 5, 2026, 8:11 PM UTC, Kraken answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 44 days we have measured Kraken (since Aug 22, 2026).

Kraken reports an active incident: "Cross-Exchange Transfer Delays" (minor incident, since Oct 2, 2026, 8:59 AM UTC). That is their claim, not our measurement: our probes are currently reaching Kraken, and an incident they declare can affect parts of the service our checks do not exercise. We show both and never merge them.

our independent probeslive · checked Oct 5, 2026, 8:11 PM UTC
US-East567 msOperational
US-West1108 msOperational
Europe91 msOperational
Asia-Pacific577 msOperational
US-Central485 msOperational
Canada242 msOperational
UK235 msOperational
Southeast Asia506 msOperational
Australia325 msOperational
South America639 msOperational
their status pagetheir claim, not our reading

Kraken publishes no status feed we can read, so the only independent reading here is ours on the left.

Kraken response time, by region

US-East
902msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 279ms2026-09-07 UTC: p95 237ms2026-09-08 UTC: p95 673ms2026-09-09 UTC: p95 693ms2026-09-10 UTC: p95 294ms2026-09-11 UTC: p95 494ms2026-09-12 UTC: p95 371ms2026-09-13 UTC: p95 308ms2026-09-14 UTC: p95 322ms2026-09-15 UTC: p95 366ms2026-09-16 UTC: p95 318ms2026-09-17 UTC: p95 481ms2026-09-18 UTC: p95 621ms2026-09-19 UTC: p95 591ms2026-09-20 UTC: p95 621ms2026-09-21 UTC: p95 512ms2026-09-22 UTC: p95 491ms2026-09-23 UTC: p95 514ms2026-09-24 UTC: p95 755ms2026-09-25 UTC: p95 676ms2026-09-26 UTC: p95 369ms2026-09-27 UTC: p95 480ms2026-09-28 UTC: p95 393ms2026-09-29 UTC: p95 420ms2026-09-30 UTC: p95 379ms2026-10-01 UTC: p95 526ms2026-10-02 UTC: p95 539ms2026-10-03 UTC: p95 854ms2026-10-04 UTC: p95 848ms2026-10-05 UTC: p95 902ms
Sep 6Sep 20Oct 5
US-West
786msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 395ms2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 791ms2026-09-09 UTC: p95 310ms2026-09-10 UTC: p95 326ms2026-09-11 UTC: p95 406ms2026-09-12 UTC: p95 558ms2026-09-13 UTC: p95 677ms2026-09-14 UTC: p95 512ms2026-09-15 UTC: p95 316ms2026-09-16 UTC: p95 638ms2026-09-17 UTC: p95 612ms2026-09-18 UTC: p95 600ms2026-09-19 UTC: p95 522ms2026-09-20 UTC: p95 493ms2026-09-21 UTC: p95 502ms2026-09-22 UTC: p95 597ms2026-09-23 UTC: p95 536ms2026-09-24 UTC: p95 613ms2026-09-25 UTC: p95 543ms2026-09-26 UTC: p95 706ms2026-09-27 UTC: p95 594ms2026-09-28 UTC: p95 764ms2026-09-29 UTC: p95 863ms2026-09-30 UTC: p95 776ms2026-10-01 UTC: p95 517ms2026-10-02 UTC: p95 607ms2026-10-03 UTC: p95 410ms2026-10-04 UTC: p95 808ms2026-10-05 UTC: p95 786ms
Sep 6Sep 20Oct 5
Europe
315msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 207ms2026-09-07 UTC: p95 226ms2026-09-08 UTC: p95 727ms2026-09-09 UTC: p95 569ms2026-09-10 UTC: p95 200ms2026-09-11 UTC: p95 211ms2026-09-12 UTC: p95 299ms2026-09-13 UTC: p95 212ms2026-09-14 UTC: p95 177ms2026-09-15 UTC: p95 158ms2026-09-16 UTC: p95 167ms2026-09-17 UTC: p95 208ms2026-09-18 UTC: p95 190ms2026-09-19 UTC: p95 170ms2026-09-20 UTC: p95 176ms2026-09-21 UTC: p95 197ms2026-09-22 UTC: p95 198ms2026-09-23 UTC: p95 223ms2026-09-24 UTC: p95 341ms2026-09-25 UTC: p95 516ms2026-09-26 UTC: p95 351ms2026-09-27 UTC: p95 356ms2026-09-28 UTC: p95 390ms2026-09-29 UTC: p95 355ms2026-09-30 UTC: p95 199ms2026-10-01 UTC: p95 390ms2026-10-02 UTC: p95 327ms2026-10-03 UTC: p95 254ms2026-10-04 UTC: p95 321ms2026-10-05 UTC: p95 315ms
Sep 6Sep 20Oct 5
Asia-Pacific
837msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 923ms2026-09-07 UTC: p95 931ms2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 1.0s2026-09-10 UTC: p95 744ms2026-09-11 UTC: p95 799ms2026-09-12 UTC: p95 642ms2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 740ms2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.6s2026-09-22 UTC: p95 727ms2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 794ms2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.6s2026-09-28 UTC: p95 957ms2026-09-29 UTC: p95 816ms2026-09-30 UTC: p95 779ms2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 878ms2026-10-05 UTC: p95 837ms
Sep 6Sep 20Oct 5
US-Central
615msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 417ms2026-09-07 UTC: p95 457ms2026-09-08 UTC: p95 420ms2026-09-09 UTC: p95 519ms2026-09-10 UTC: p95 517ms2026-09-11 UTC: p95 617ms2026-09-12 UTC: p95 427ms2026-09-13 UTC: p95 438ms2026-09-14 UTC: p95 657ms2026-09-15 UTC: p95 950ms2026-09-16 UTC: p95 436ms2026-09-17 UTC: p95 478ms2026-09-18 UTC: p95 558ms2026-09-19 UTC: p95 543ms2026-09-20 UTC: p95 511ms2026-09-21 UTC: p95 452ms2026-09-22 UTC: p95 460ms2026-09-23 UTC: p95 676ms2026-09-24 UTC: p95 654ms2026-09-25 UTC: p95 601ms2026-09-26 UTC: p95 517ms2026-09-27 UTC: p95 346ms2026-09-28 UTC: p95 427ms2026-09-29 UTC: p95 471ms2026-09-30 UTC: p95 549ms2026-10-01 UTC: p95 419ms2026-10-02 UTC: p95 522ms2026-10-03 UTC: p95 412ms2026-10-04 UTC: p95 336ms2026-10-05 UTC: p95 615ms
Sep 6Sep 20Oct 5
Canada
512msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 571ms2026-09-07 UTC: p95 480ms2026-09-08 UTC: p95 423ms2026-09-09 UTC: p95 549ms2026-09-10 UTC: p95 347ms2026-09-11 UTC: p95 491ms2026-09-12 UTC: p95 412ms2026-09-13 UTC: p95 502ms2026-09-14 UTC: p95 518ms2026-09-15 UTC: p95 722ms2026-09-16 UTC: p95 528ms2026-09-17 UTC: p95 578ms2026-09-18 UTC: p95 484ms2026-09-19 UTC: p95 337ms2026-09-20 UTC: p95 355ms2026-09-21 UTC: p95 341ms2026-09-22 UTC: p95 321ms2026-09-23 UTC: p95 491ms2026-09-24 UTC: p95 508ms2026-09-25 UTC: p95 708ms2026-09-26 UTC: p95 429ms2026-09-27 UTC: p95 398ms2026-09-28 UTC: p95 607ms2026-09-29 UTC: p95 580ms2026-09-30 UTC: p95 733ms2026-10-01 UTC: p95 607ms2026-10-02 UTC: p95 614ms2026-10-03 UTC: p95 501ms2026-10-04 UTC: p95 508ms2026-10-05 UTC: p95 512ms
Sep 6Sep 20Oct 5
UK
433msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 126ms2026-09-07 UTC: p95 404ms2026-09-08 UTC: p95 252ms2026-09-09 UTC: p95 132ms2026-09-10 UTC: p95 133ms2026-09-11 UTC: p95 109ms2026-09-12 UTC: p95 156ms2026-09-13 UTC: p95 293ms2026-09-14 UTC: p95 332ms2026-09-15 UTC: p95 160ms2026-09-16 UTC: p95 254ms2026-09-17 UTC: p95 357ms2026-09-18 UTC: p95 272ms2026-09-19 UTC: p95 209ms2026-09-20 UTC: p95 212ms2026-09-21 UTC: p95 183ms2026-09-22 UTC: p95 409ms2026-09-23 UTC: p95 460ms2026-09-24 UTC: p95 444ms2026-09-25 UTC: p95 707ms2026-09-26 UTC: p95 629ms2026-09-27 UTC: p95 144ms2026-09-28 UTC: p95 193ms2026-09-29 UTC: p95 147ms2026-09-30 UTC: p95 294ms2026-10-01 UTC: p95 295ms2026-10-02 UTC: p95 239ms2026-10-03 UTC: p95 238ms2026-10-04 UTC: p95 448ms2026-10-05 UTC: p95 433ms
Sep 6Sep 20Oct 5
Southeast Asia
1.1sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.0s2026-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 960ms2026-09-09 UTC: p95 775ms2026-09-10 UTC: p95 998ms2026-09-11 UTC: p95 902ms2026-09-12 UTC: p95 928ms2026-09-13 UTC: p95 1.0s2026-09-14 UTC: p95 897ms2026-09-15 UTC: p95 601ms2026-09-16 UTC: p95 723ms2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 894ms2026-09-19 UTC: p95 647ms2026-09-20 UTC: p95 671ms2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 951ms2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.0s2026-09-27 UTC: p95 1.6s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 883ms2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 891ms2026-10-03 UTC: p95 342ms2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
Australia
857msp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.7s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 837ms2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 1.0s2026-09-14 UTC: p95 1.0s2026-09-15 UTC: p95 1.6s2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.6s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.6s2026-09-21 UTC: p95 811ms2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 1.6s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 1.0s2026-09-27 UTC: p95 733ms2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 2.5s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 865ms2026-10-04 UTC: p95 676ms2026-10-05 UTC: p95 857ms
Sep 6Sep 20Oct 5
South America
1.2sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.1s2026-09-07 UTC: p95 882ms2026-09-08 UTC: p95 870ms2026-09-09 UTC: p95 648ms2026-09-10 UTC: p95 722ms2026-09-11 UTC: p95 615ms2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 695ms2026-09-16 UTC: p95 988ms2026-09-17 UTC: p95 955ms2026-09-18 UTC: p95 635ms2026-09-19 UTC: p95 675ms2026-09-20 UTC: p95 567ms2026-09-21 UTC: p95 677ms2026-09-22 UTC: p95 602ms2026-09-23 UTC: p95 711ms2026-09-24 UTC: p95 833ms2026-09-25 UTC: p95 988ms2026-09-26 UTC: p95 852ms2026-09-27 UTC: p95 665ms2026-09-28 UTC: p95 599ms2026-09-29 UTC: p95 872ms2026-09-30 UTC: p95 867ms2026-10-01 UTC: p95 663ms2026-10-02 UTC: p95 692ms2026-10-03 UTC: p95 932ms2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.2s
Sep 6Sep 20Oct 5

Is it Kraken, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Kraken -- it cannot diagnose Kraken's own systems.

What we measured, function by function

Kraken answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see Kraken go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Kraken, and again when they can reach it again. That is our own measurement from ten regions, not Kraken's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 567msstatus code: 200checked: Oct 5, 2026, 8:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Kraken normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 1108msstatus code: 200checked: Oct 5, 2026, 8:08 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Kraken normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 485msstatus code: 200checked: Oct 5, 2026, 8:06 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Kraken normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 242msstatus code: 200checked: Oct 5, 2026, 7:59 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Kraken normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 639msstatus code: 200checked: Oct 5, 2026, 8:06 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Kraken normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 91msstatus code: 200checked: Oct 5, 2026, 8:10 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Kraken normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 235msstatus code: 200checked: Oct 5, 2026, 8:08 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Kraken normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 577msstatus code: 200checked: Oct 5, 2026, 8:11 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Kraken normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 506msstatus code: 200checked: Oct 5, 2026, 7:58 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Kraken normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 325msstatus code: 200checked: Oct 5, 2026, 8:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Kraken normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Kraken, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Kraken yet, which is not evidence that nothing is wrong.

Recent outages

Sui (SUI) Funding Delays, 1h 7mdeclared on their status page2026-10-02
Aleo (ALEO) Funding Delays, 48h 28mdeclared on their status page2026-10-02
Cross-Exchange Transfer Delaysdeclared on their status page2026-10-02
Futures Market Data Delays, 1h 7mdeclared on their status page2026-10-01
FIX API order placement issues for recently listed markets, 9mdeclared on their status page2026-09-30
Hedera (HBAR) Funding Delays, 11h 55mdeclared on their status page2026-09-29
Delays with Ethereum (ERC-20) deposits, 43h 20mdeclared on their status page2026-09-26
Delayed withdrawals on Ethereum network, 3h 49mdeclared on their status page2026-09-25

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Kraken since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Kraken covering any window you pick, with our measurements and Kraken's own claim at the time, side by side.

Full availability history for Kraken: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

Kraken uptime measured by RealUptimeLive, from this page's own readings.
[![Kraken uptime measured by RealUptime](https://realuptime.io/outages/kraken/badge.svg?days=30)](https://realuptime.io/outages/kraken)
<a href="https://realuptime.io/outages/kraken"><img src="https://realuptime.io/outages/kraken/badge.svg?days=30" alt="Kraken uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Kraken's SLA implies, from our measurement

At or above your target

We measured none of downtime for Kraken over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Kraken's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.kraken.com/0/public/Time
secondary
https://www.kraken.com/
secondary
https://status.kraken.com/api/v2/status.json
RealUptime is not affiliated with Kraken; the name identifies what we measured, and nothing here speaks for Kraken's own team. We send a single web request to Kraken from 10 regions on our own schedule and time the response. We do not see inside Kraken's systems, do not use an account or real transaction, and are not the same signal Kraken's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Kraken is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.