Kraken REST · depth degradation, 54 min on 14 SEP 2026
Kraken REST · depth — p95 1062ms over the last five minutes, 9.2× the 7-day baseline of 115ms — from Singapore, SG and Carlstadt, US. up24 opened this incident from its own measurements of Kraken's public API on 14 SEP 2026 14:27 UTC. It lasted 54 min and ended 14 SEP 2026 15:21 UTC, when the component started answering again.
WHAT HAPPENED
- Kraken published its own notice.
- up24 opened the incident at degraded.
- 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, 49 of 5,829 checks failed: timeout ×49.
REST latency for the failing endpoint, per minute, from 14 SEP 2026 13:33 UTC to 14 SEP 2026 16:15 UTC. The gap in the line is where nothing answered.
DID KRAKEN SAY SO?
Kraken acknowledged the same event 1h 58m before up24 opened this incident, on 14 SEP 2026 12:29 UTC: “Arweave (AR) Funding Delays”. Matching is by time window, and their notice is linked so the pairing can be judged rather than taken on faith.
Arweave (AR) Funding Delays · 14 SEP 2026 12:29 UTC
up24 opened 77 incidents for Kraken in the last 90 days; 39 fall within six hours of something Kraken published, and the rest were never mentioned. At the median, Kraken's own notice came 1h 58m 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.