Kraken REST · ping degradation, 2h 31m on 18 AUG 2026
Kraken REST · ping — intermittently degraded: 11 episodes. up24 opened this incident from its own measurements of Kraken's public API on 18 AUG 2026 14:06 UTC. It lasted 2h 31m and ended 18 AUG 2026 16:37 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 5,459 checks failed: no error class was recorded against them.
REST latency for the failing endpoint, per minute, from 18 AUG 2026 11:34 UTC to 18 AUG 2026 19:09 UTC. The gap in the line is where nothing answered.
DID KRAKEN SAY SO?
Kraken acknowledged the same event 5h 14m before up24 opened this incident, on 18 AUG 2026 08:51 UTC: “Issues with asset search on Kraken Web and Kraken App”. Matching is by time window, and their notice is linked so the pairing can be judged rather than taken on faith.
Issues with asset search on Kraken Web and Kraken App · 18 AUG 2026 08:51 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.