Kraken outage affects Spot and derivatives trading – Here’s what happened
- Published
- Updated
- Since then
- 1 new report
- In
- Exchanges
Kraken experienced a one-hour technical outage that disrupted spot and derivatives trading, along with access through its website, mobile app, and APIs. The exchange said there was no security breach or loss of customer funds, and the disruption has been placed in the context of a turbulent October for crypto exchanges.
Key claims & sources
What it means
Kraken is one of the larger venues for both spot and derivatives trading, so even a short interruption can affect how traders enter orders and access the platform. The outage covered the exchange’s website, mobile app, and APIs, which means both casual users and automated systems were hit at the same time. The incident also sits in a month already described as turbulent for crypto exchanges, which gives the outage a wider operational context.
For people using Kraken, the immediate effect was a break in trading access rather than a reported loss of funds. That means users who rely on the exchange for active execution had to wait for service to return before they could place or manage orders. The statement that no security breach was involved also separates this event from the kind of exchange incident that raises custody concerns.
Exchange outages test the reliability promise that sits underneath centralized crypto trading. Spot and derivatives markets depend on continuous connectivity, and any interruption highlights how much trading activity still runs through a single platform with matching engines, apps, and APIs tied together. The tension here is between fast, always-on markets and the fragility that comes with concentrating so much activity inside one venue.
Market reaction i
The move was larger before the first headline than after. That is an observation, not an explanation: the market also moves on things nobody publishes.
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Other recent incidents
| When | What happened | Figure |
|---|---|---|
| 1 days ago | Loopscale Lending · Unknown incident | no figure in dollars |
| 1 days ago | TENDRIL · Swap Logic Flaw incident | $550k |
| 1 days ago | $TENDRIL · Smart contract vulnerability incident | $555k |
| 3 days ago | InsurancePool/CoreVault · Flash loan attack incident | $112.3k |
| 4 days ago | Solana MEV Bot King · Hot wallet key compromise incident | $856k |
4280 incidents stored