Kraken REST · depth degradation, 1 min on 26 OCT 2026
Kraken REST · depth — p95 705ms over the last five minutes, 4× the 7-day baseline of 175ms — from Lauterbourg, FR only; 2 regions had too little evidence. up24 opened this incident from its own measurements of Kraken's public API on 26 OCT 2026 21:05 UTC. It lasted 1 min and ended 26 OCT 2026 21:07 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 870 checks failed.
REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 26 OCT 2026 20:35 UTC to 26 OCT 2026 21:37 UTC. The gap in the line is where nothing answered.
DID KRAKEN SAY SO?
Kraken published a notice 5h 58m before up24 opened this incident, on 26 OCT 2026 15:06 UTC: “Bitcoin (BTC) funding delays”. It is paired by time alone, within six hours — nothing checks that it is about this fault, so it is linked to be judged rather than taken on faith.
Bitcoin (BTC) funding delays · 26 OCT 2026 15:06 UTC
up24 opened 105 incidents for Kraken in the last 90 days; 62 line up with something Kraken published within six hours, and the rest have no published report near them. At the median, Kraken's own notice came 1h 23m before up24 opened its incident. Pairing is by time alone — nothing checks that a notice is about the fault up24 measured, so the 23 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.