Kraken REST · ping degradation, 4 min on 13 OCT 2026
Kraken REST · ping — p95 748ms over the last five minutes, 4.4× the 7-day baseline of 170ms — from Lauterbourg, FR and Carlstadt, US. up24 opened this incident from its own measurements of Kraken's public API on 13 OCT 2026 18:00 UTC. It lasted 4 min and ended 13 OCT 2026 18:05 UTC, when the component started answering again.
WHAT HAPPENED
- Kraken published its own notice.
- Kraken marked its notice resolved.
- 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,339 checks failed: no error class was recorded against them.
REST latency for the failing endpoint, per minute, from 13 OCT 2026 17:30 UTC to 13 OCT 2026 18:35 UTC. The gap in the line is where nothing answered.
DID KRAKEN SAY SO?
Kraken acknowledged the same event 4h 52m before up24 opened this incident, on 13 OCT 2026 13:08 UTC: “Futures Trading Engine degraded performance”. Matching is by time window, and their notice is linked so the pairing can be judged rather than taken on faith.
Futures Trading Engine degraded performance · 13 OCT 2026 13:08 UTC
up24 opened 83 incidents for Kraken in the last 90 days; 45 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.