Kraken WS · connection degradation, 30s on 04 NOV 2026
Kraken WS — 6.7% of windows failing over the last five minutes (conn) — from Singapore, SG and Lauterbourg, FR. up24 opened this incident from its own measurements of Kraken's public API on 04 NOV 2026 17:58 UTC. It lasted 30s and ended 04 NOV 2026 17:59 UTC, when the component started answering again.
WHAT HAPPENED
- Kraken published its own notice.
- up24 opened the incident at degraded, conn.
- The component started answering again. up24 dates the incident from this moment, not from when its clearing rule finished.
- 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.
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 within six hours of this incident, on 04 NOV 2026 17:33 UTC: “Plaid US Withdrawal 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.
Plaid US Withdrawal Delays · 04 NOV 2026 17:33 UTC
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 — 4 recorded transitions — and nothing on it is reported by Kraken.