Kraken REST · depth outage, 52 min on 09 NOV 2026
Kraken REST · depth — 100% of checks failing over the last minute (timeout) — from every region. up24 opened this incident from its own measurements of Kraken's public API on 09 NOV 2026 20:51 UTC. It lasted 52 min and ended 09 NOV 2026 21:44 UTC, when the component started answering again.
WHAT HAPPENED
- up24 opened the incident at degraded, timeout.
- up24 raised it to outage — the same incident, not a second one.
- Kraken published its own notice.
- The component started answering again. up24 dates the incident from this moment, not from when its clearing rule finished.
- Kraken marked its notice resolved.
HOW IT FAILED
Over the window, 1,730 of 5,652 checks failed: timeout ×1,719, bad_body ×10, http_5xx ×1.
REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 09 NOV 2026 19:59 UTC to 09 NOV 2026 22:36 UTC. The gap in the line is where nothing answered.
DID KRAKEN SAY SO?
Kraken published a notice within six hours of this incident, on 09 NOV 2026 21:38 UTC: “Spot REST API market data errors”. It is paired by time alone, within six hours — nothing checks that it is about this fault, so it is linked to be judged rather than taken on faith.
Spot REST API market data errors · 09 NOV 2026 21:38 UTC
up24 opened 61 incidents for Kraken in the last 90 days; 38 line up with something Kraken published within six hours, and the rest have no published report near them. Pairing is by time alone — nothing checks that a notice is about the fault up24 measured, so none of it should be read as a scoop . Every entry links to the venue's own notice so the pairing can be judged.
KRAKEN — OTHER INCIDENTS
Measured by up24's own probe against Kraken's public API, XBTUSD against USD, every 5s. This page is generated from the incident's own rows — 5 recorded transitions — and nothing on it is reported by Kraken.