← Kraken status page

Kraken WS · trade degradation, 4 min on 17 NOV 2026

Kraken WS · trade — 83% of windows stalled over the last minute (stalled) — from Singapore, SG and Lauterbourg, FR. up24 opened this incident from its own measurements of Kraken's public API on 17 NOV 2026 08:10 UTC. It lasted 4 min and ended 17 NOV 2026 08:15 UTC, when the component started answering again.

DEGRADEDWS · trade · trade
DURATION
4 min
STARTED
17 NOV 2026 08:10 UTC
ENDED
17 NOV 2026 08:15 UTC
NEAREST NOTICE · ±6H
NONE

WHAT HAPPENED

  1. 17 NOV 2026 08:10 UTC
    up24 opened the incident at degraded, stalled.
  2. 17 NOV 2026 08:15 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, 34 of 1,167 ten-second windows failed: stalled ×34.

— p50‑ ‑ p95
axis 0 – 200ms
07:41 · 17 NOV08:13 · 17 NOV08:45 · 17 NOV

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 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 61 incidents for Kraken in the last 90 days; 38 line up with something Kraken published within six hours, and the rest have no published report near them. Pairing is by time alone — nothing checks that a notice is about the fault up24 measured, so none of it should be read as a scoop . 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.