Kraken REST · ping degradation, 10s on 20 AUG 2026
Kraken REST · ping — p95 265ms over five minutes, 4.3× the 7-day baseline of 61ms. up24 opened this incident from its own measurements of Kraken's public API on 20 AUG 2026 04:35 UTC. It lasted 10s and ended 20 AUG 2026 04:35 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.
- Kraken published its own notice.
- Kraken marked its notice resolved.
HOW IT FAILED
Over the window, 0 of 720 checks failed: no error class was recorded against them.
REST latency for the failing endpoint, per minute, from 20 AUG 2026 04:05 UTC to 20 AUG 2026 05:05 UTC. The gap in the line is where nothing answered.
DID KRAKEN SAY SO?
Kraken acknowledged the same event 4h 45m after up24 opened this incident, on 20 AUG 2026 09:21 UTC: “Delayed Delivery of Account-Related Email Notifications”. Matching is by time window, and their notice is linked so the pairing can be judged rather than taken on faith.
Delayed Delivery of Account-Related Email Notifications · 20 AUG 2026 09:21 UTC
up24 opened 77 incidents for Kraken in the last 90 days; 39 fall within six hours of something Kraken published, and the rest were never mentioned. At the median, Kraken's own notice came 1h 58m 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.