← Kraken status page

Kraken WS · connection degradation, 1 min on 22 SEP 2026

Kraken WS — 6.7% of windows failing over the last five minutes (conn) — from Singapore, SG and Carlstadt, US. up24 opened this incident from its own measurements of Kraken's public API on 22 SEP 2026 20:29 UTC. It lasted 1 min and ended 22 SEP 2026 20:30 UTC, when the component started answering again.

DEGRADEDWS · connection · the shared socket
DURATION
1 min
STARTED
22 SEP 2026 20:29 UTC
ENDED
22 SEP 2026 20:30 UTC
VS THEIR NOTICE
4h 59m later

WHAT HAPPENED

  1. 22 SEP 2026 15:30 UTC
    Kraken published its own notice.
  2. 22 SEP 2026 20:29 UTC
    up24 opened the incident at degraded, conn.
  3. 22 SEP 2026 20:30 UTC
    The component started answering again. up24 dates the incident from this moment, not from when its clearing rule finished.
  4. 28 SEP 2026 11:58 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 – 500ms
20:00 · 22 SEP20:30 · 22 SEP21:00 · 22 SEP

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 4h 59m before up24 opened this incident, on 22 SEP 2026 15:30 UTC: “Krak Card degraded performance.”. Matching is by time window, and their notice is linked so the pairing can be judged rather than taken on faith.

Krak Card degraded performance. · 22 SEP 2026 15:30 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.