Kraken REST · ping degradation, ongoing since 26 OCT 2026
Kraken REST · ping — p95 1123ms over the last five minutes, 4.2× the 7-day baseline of 265ms — from Carlstadt, US only; 2 regions had too little evidence. up24 opened this incident from its own measurements of Kraken's public API on 26 OCT 2026 23:04 UTC. It is still open, 2h 27m in.
WHAT HAPPENED
- up24 opened the incident at degraded.
HOW IT FAILED
Over the window, 0 of 2,165 checks failed.
REST latency for the failing endpoint, per minute, measured from Lauterbourg, FR, from 26 OCT 2026 20:36 UTC to 27 OCT 2026 01:31 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 108 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 — 1 recorded transitions — and nothing on it is reported by Kraken.