Kraken REST · ping degradation, 10s on 23 OCT 2026
Kraken REST · ping — 5.1% of checks failing over the last five minutes (dns) — none of the 11 checks over the last minute failed — from Lauterbourg, FR and Carlstadt, US. up24 opened this incident from its own measurements of Kraken's public API on 23 OCT 2026 21:05 UTC. It lasted 10s and ended 23 OCT 2026 21:05 UTC, when the component started answering again.
WHAT HAPPENED
- Kraken published its own notice.
- up24 opened the incident at degraded, dns.
- 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, 3 of 2,173 checks failed: dns ×3.
REST latency for the failing endpoint, per minute, from 23 OCT 2026 20:35 UTC to 23 OCT 2026 21:35 UTC. The gap in the line is where nothing answered.
DID KRAKEN SAY SO?
Kraken acknowledged the same event 4h 50m before up24 opened this incident, on 23 OCT 2026 16:15 UTC: “Initia (INIT) Deposits and Withdrawals Temporarily Paused”. Matching is by time window, and their notice is linked so the pairing can be judged rather than taken on faith.
Initia (INIT) Deposits and Withdrawals Temporarily Paused · 23 OCT 2026 16:15 UTC
up24 opened 101 incidents for Kraken in the last 90 days; 59 fall within six hours of something Kraken published, and the rest were never mentioned. At the median, Kraken's own notice came 3h 02m before up24 opened its incident. Pairing is by time alone — nothing checks that a notice is about the fault up24 measured, so the 15 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 — 3 recorded transitions — and nothing on it is reported by Kraken.