Loading prices…
🩸BEARISH

Kraken Resolves Trading Outage After One Hour

The disruption reached spot and derivatives users across web, mobile and trading interfaces, exposing how broadly an exchange outage can affect access.

Kraken began investigating connectivity and order placement issues at 02:42 UTC on October 30. Spot and derivatives users were affected across the web, mobile app, REST, WebSocket and FIX interfaces. The exchange marked the issue resolved at 03:42 UTC.

Why it matters

The incident affected both major trading products and multiple ways of connecting to Kraken. For traders, connectivity and order placement problems can interrupt access to spot and derivatives markets while an issue is active.

Market impact

Kraken reported the disruption resolved after one hour. The incident highlights the operational importance of reliable access across exchange interfaces, but the seed gives no indication of broader market effects.

Source: [Spot Exchange Connectivity Issues - Web, Mobile & API (Rest & Websockets)](https://status.kraken.com/incidents/zkqc9db292h5)

Frequently asked questions

  1. When did Kraken's connectivity and order issues begin and end?

    Kraken began investigating at 02:42 UTC on October 30 and marked the issue resolved at 03:42 UTC.

  2. Which Kraken trading products were affected?

    The disruption affected spot and derivatives users.

  3. Which Kraken access methods were affected?

    Users were affected across the web, mobile app, REST, WebSocket and FIX interfaces.

  4. What kinds of problems did Kraken report?

    Kraken reported connectivity and order placement issues.

  5. How long did the reported disruption last?

    The issue was marked resolved one hour after Kraken began investigating it.

Source attribution
Aggregated from WuBlockchain · Verified · Last refreshed 1h ago
Open original →