← Kraken status page

Kraken WS · connection outage, 16 min on 20 AUG 2026

Kraken WS — 33% of windows failing over the last minute (conn). up24 opened this incident from its own measurements of Kraken's public API on 20 AUG 2026 07:02 UTC. It lasted 16 min and ended 20 AUG 2026 07:19 UTC, when the component started answering again.

OUTAGEWS · connection · the shared socket
DURATION
16 min
STARTED
20 AUG 2026 07:02 UTC
ENDED
20 AUG 2026 07:19 UTC
VS THEIR NOTICE
2h 18m earlier

WHAT HAPPENED

  1. 20 AUG 2026 07:02 UTC
    up24 opened the incident at outage, conn.
  2. 20 AUG 2026 07:19 UTC
    The component started answering again. up24 dates the incident from this moment, not from when its clearing rule finished.
  3. 20 AUG 2026 09:21 UTC
    Kraken published its own notice.
  4. 20 AUG 2026 09:31 UTC
    Kraken marked its notice resolved.

HOW IT FAILED

Stream measurements are kept for seven days, and this incident is older than that. The incident itself is permanent; the ten-second windows behind it are not.

— p50‑ ‑ p95
axis 0 – 200ms
06:33 · 20 AUG07:11 · 20 AUG07:49 · 20 AUG

A stream has no latency of its own — a feed either delivers or it does not — so this is Kraken's REST endpoints over the same window, per minute, as the median across them. It answers the question the timeline cannot: whether the rest of the exchange was fine while this feed was down.

DID KRAKEN SAY SO?

Kraken acknowledged the same event 2h 18m 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.