Kraken REST · ticker degradation, 4 min on 02 NOV 2026
Kraken REST · ticker — p95 953ms over the last five minutes, 5.4× the 7-day baseline of 176ms — from Lauterbourg, FR and Carlstadt, US. up24 opened this incident from its own measurements of Kraken's public API on 02 NOV 2026 17:01 UTC. It lasted 4 min and ended 02 NOV 2026 17:05 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,304 checks failed.
REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 02 NOV 2026 16:31 UTC to 02 NOV 2026 17:35 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 61 incidents for Kraken in the last 90 days; 38 line up with something Kraken published within six hours, and the rest have no published report near them. Pairing is by time alone — nothing checks that a notice is about the fault up24 measured, so none of it should be read as a scoop . 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.