Kraken REST · ticker degradation, 50s on 15 OCT 2026
Kraken REST · ticker — 25% of checks failing over the last minute (timeout) — from Singapore, SG 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 15 OCT 2026 17:29 UTC. It lasted 50s and ended 15 OCT 2026 17:30 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.
HOW IT FAILED
Over the window, 14 of 2,196 checks failed: timeout ×14.
REST latency for the failing endpoint, per minute, from 15 OCT 2026 16:59 UTC to 15 OCT 2026 18:00 UTC. The gap in the line is where nothing answered.
DID KRAKEN SAY SO?
Kraken acknowledged the same event 3h 57m before up24 opened this incident, on 15 OCT 2026 13:32 UTC: “Blank favorites page for Pro App and Pro Web users who used Prop trading”. Matching is by time window, and their notice is linked so the pairing can be judged rather than taken on faith.
Blank favorites page for Pro App and Pro Web users who used Prop trading · 15 OCT 2026 13:32 UTC
up24 opened 91 incidents for Kraken in the last 90 days; 51 fall within six hours of something Kraken published, and the rest were never mentioned. At the median, Kraken's own notice came 2h 54m 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 — 3 recorded transitions — and nothing on it is reported by Kraken.