Kraken REST · depth degradation, 40s on 13 OCT 2026
Kraken REST · depth — 25% of checks failing over the last minute (timeout) — from Lauterbourg, FR and Carlstadt, US — not graded an outage until it has failed for 2 minutes. up24 opened this incident from its own measurements of Kraken's public API on 13 OCT 2026 13:01 UTC. It lasted 40s and ended 13 OCT 2026 13:02 UTC, when the component started answering again.
WHAT HAPPENED
- Kraken published its own notice.
- up24 opened the incident at degraded, timeout.
- 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, 5 of 2,184 checks failed: timeout ×5.
REST latency for the failing endpoint, per minute, from 13 OCT 2026 12:31 UTC to 13 OCT 2026 13:32 UTC. The gap in the line is where nothing answered.
DID KRAKEN SAY SO?
Kraken acknowledged the same event 2h 36m before up24 opened this incident, on 13 OCT 2026 10:25 UTC: “MultiversX (EGLD) Funding paused”. Matching is by time window, and their notice is linked so the pairing can be judged rather than taken on faith.
MultiversX (EGLD) Funding paused · 13 OCT 2026 10:25 UTC
up24 opened 82 incidents for Kraken in the last 90 days; 44 fall within six hours of something Kraken published, and the rest were never mentioned. At the median, Kraken's own notice came 2h 36m before up24 opened its incident. Pairing is by time alone — nothing checks that a notice is about the fault up24 measured, so the 14 that up24 timestamped first are not scoops. 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 — 4 recorded transitions — and nothing on it is reported by Kraken.