Kraken WS · connection degradation, 3 min on 06 OCT 2026
Kraken WS — 6.7% of windows failing over the last five minutes (conn) — from Carlstadt, US and Singapore, SG. up24 opened this incident from its own measurements of Kraken's public API on 06 OCT 2026 18:30 UTC. It lasted 3 min and ended 06 OCT 2026 18:33 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
Over the window, 14 of 2,268 ten-second windows failed: conn ×14.
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 5h 21m before up24 opened this incident, on 06 OCT 2026 13:09 UTC: “Sonic (S) Funding Delays”. Matching is by time window, and their notice is linked so the pairing can be judged rather than taken on faith.
Sonic (S) Funding Delays · 06 OCT 2026 13:09 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.