Kraken REST · ping degradation, 5 min on 16 AUG 2026
Kraken REST · ping — p95 329ms over five minutes, 6.6× the 7-day baseline of 50ms. up24 opened this incident from its own measurements of Kraken's public API on 16 AUG 2026 12:41 UTC. It lasted 5 min and ended 16 AUG 2026 12:46 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 780 checks failed: no error class was recorded against them.
REST latency for the failing endpoint, per minute, from 16 AUG 2026 12:11 UTC to 16 AUG 2026 13:16 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 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 — 2 recorded transitions — and nothing on it is reported by Kraken.