← Kraken status page

Kraken WS · connection degradation, 5 min on 13 OCT 2026

Kraken WS — 33% of windows failing over the last minute (conn) — from Singapore, SG and Lauterbourg, FR — not graded an outage until it has failed for 2 minutes. up24 opened this incident from its own measurements of Kraken's public API on 13 OCT 2026 13:01 UTC. It lasted 5 min and ended 13 OCT 2026 13:06 UTC, when the component started answering again.

DEGRADEDWS · connection · the shared socket
DURATION
5 min
STARTED
13 OCT 2026 13:01 UTC
ENDED
13 OCT 2026 13:06 UTC
VS THEIR NOTICE
2h 36m later

WHAT HAPPENED

  1. 13 OCT 2026 10:25 UTC
    Kraken published its own notice.
  2. 13 OCT 2026 13:01 UTC
    up24 opened the incident at degraded, conn.
  3. 13 OCT 2026 13:06 UTC
    The component started answering again. up24 dates the incident from this moment, not from when its clearing rule finished.
  4. 13 OCT 2026 13:41 UTC
    Kraken marked its notice resolved.

HOW IT FAILED

Over the window, 30 of 2,343 ten-second windows failed: conn ×18, stalled ×6, timeout ×6.

— p50‑ ‑ p95
axis 0 – 2000ms
12:32 · 13 OCT13:04 · 13 OCT13:36 · 13 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. 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 36m before up24 opened this incident, on 13 OCT 2026 10:25 UTC: “MultiversX (EGLD) Funding paused”. Matching is by time window, and their notice is linked so the pairing can be judged rather than taken on faith.

MultiversX (EGLD) Funding paused · 13 OCT 2026 10:25 UTC

up24 opened 82 incidents for Kraken in the last 90 days; 44 fall within six hours of something Kraken published, and the rest were never mentioned. At the median, Kraken's own notice came 2h 36m 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.