Kraken REST · ticker degradation, 2 min on 24 OCT 2026
Kraken REST · ticker — p95 693ms over the last five minutes, 6.7× the 7-day baseline of 103ms — from Lauterbourg, FR and Carlstadt, US. up24 opened this incident from its own measurements of Kraken's public API on 24 OCT 2026 00:06 UTC. It lasted 2 min and ended 24 OCT 2026 00:08 UTC, when the component started answering again.
WHAT HAPPENED
- 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.
HOW IT FAILED
Over the window, 0 of 2,234 checks failed.
REST latency for the failing endpoint, per minute, from 23 OCT 2026 23:36 UTC to 24 OCT 2026 00:38 UTC. The gap in the line is where nothing answered.
DID KRAKEN SAY SO?
Kraken publishes a status feed and nothing in it lines up with this incident. That is not proof they stayed silent; it is what their feed says.
up24 opened 102 incidents for Kraken in the last 90 days; 59 fall within six hours of something Kraken published, and the rest were never mentioned. At the median, Kraken's own notice came 3h 02m before up24 opened its incident. Pairing is by time alone — nothing checks that a notice is about the fault up24 measured, so the 15 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 — 2 recorded transitions — and nothing on it is reported by Kraken.