← Kraken status page

Kraken WS · connection degradation, 1 min on 26 OCT 2026

Kraken WS — 6.9% 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 26 OCT 2026 19:07 UTC. It lasted 1 min and ended 26 OCT 2026 19:09 UTC, when the component started answering again.

DEGRADEDWS · connection · the shared socket
DURATION
1 min
STARTED
26 OCT 2026 19:07 UTC
ENDED
26 OCT 2026 19:09 UTC
NEAREST NOTICE · ±6H
4h 00m before up24

WHAT HAPPENED

  1. 26 OCT 2026 15:06 UTC
    Kraken published its own notice.
  2. 26 OCT 2026 15:45 UTC
    Kraken marked its notice resolved.
  3. 26 OCT 2026 19:07 UTC
    up24 opened the incident at degraded, conn.
  4. 26 OCT 2026 19:09 UTC
    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, 20 of 2,220 ten-second windows failed: conn ×20.

— p50‑ ‑ p95
axis 0 – 2000ms
18:38 · 26 OCT19:08 · 26 OCT19:39 · 26 OCT

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, measured from Lauterbourg, FR. 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 published a notice 4h 00m before up24 opened this incident, on 26 OCT 2026 15:06 UTC: “Bitcoin (BTC) funding delays”. It is paired by time alone, within six hours — nothing checks that it is about this fault, so it is linked to be judged rather than taken on faith.

Bitcoin (BTC) funding delays · 26 OCT 2026 15:06 UTC

up24 opened 105 incidents for Kraken in the last 90 days; 62 line up with something Kraken published within six hours, and the rest have no published report near them. At the median, Kraken's own notice came 1h 23m before up24 opened its incident. Pairing is by time alone — nothing checks that a notice is about the fault up24 measured, so the 23 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.