How do I manage my orders when the Kraken platform is down?

Understanding Platform Downtime on Kraken

When the Kraken platform is down, users may experience disruptions in accessing their accounts, viewing balances, or executing trades. This downtime can result from scheduled maintenance, unexpected server outages, or high traffic volume overwhelming the system. During these periods, real-time order management becomes inaccessible through the standard web or mobile interface. It’s important to recognize that while Kraken maintains a high uptime, temporary outages do occur, and traders must be prepared with contingency strategies. The inability to cancel, modify, or monitor active orders during downtime can expose users to market risk, especially in volatile conditions.

Checking the Status of Kraken’s Services

Before assuming full platform failure, verify whether the issue is localized or widespread. Visit Kraken’s official status page at status.kraken.com. This page provides real-time updates on the operational health of various services, including the trading engine, API, deposit/withdrawal systems, and website accessibility. Look for indicators such as:

• 'Operational' – All systems are functioning normally
• 'Degraded Performance' – Some features may be slow or partially unavailable
• 'Outage' – A service is completely down If the status page confirms an outage, no immediate action on your end will restore access. However, this confirmation helps rule out personal connectivity issues or account-specific problems.

  Leveraging Kraken’s API for Order Management

  If you have previously set up API access, you may still be able to manage orders during partial outages. The Kraken API sometimes remains functional even when the web interface is down. To use the API:
• Ensure your API keys are created with 'Query' and 'Cancel/Modify Orders' permissions
• Use a secure environment (e.g., a local script or API client) to avoid exposing keys
• Send a private request to the OpenOrders endpoint to retrieve your active orders

• To cancel an order, use the CancelOrder endpoint with the correct transaction ID Example curl command:

  curl -X POST https://api.kraken.com/0/private/CancelOrder \
  -H 'API-Key: YOUR_API_KEY' \
  -H 'API-Sign: SIGNED_PAYLOAD' \
  -d 'txid=ORDER_TRANSACTION_ID'

  Note: The API may also be affected during major outages. Test connectivity using the public API endpoints (e.g., Ticker data) to assess availability.

  Setting Up Stop-Loss and Take-Profit Orders in Advance

  One of the most effective ways to manage risk during platform downtime is to pre-place conditional orders before any outage occurs. Kraken supports Stop-Loss and Take-Profit orders through its advanced order types. These are stored on Kraken’s servers and executed automatically based on market conditions, even if you cannot access the platform. To set them:
• Navigate to the trading interface and select 'Advanced Orders'
• Choose 'Stop-Loss' to limit downside risk or 'Take-Profit' to secure gains
• Enter the trigger price and order size
• Confirm the order is 'Posted to the order book' or 'Triggered when price reaches' level These orders remain active across sessions and do not require your device to stay online. They function independently of interface availability, relying on Kraken’s backend matching engine.

  Using Third-Party Tools and Alerts

  External monitoring tools can help you react quickly when Kraken is unreachable. Set up price alerts via third-party services such as TradingView, CoinMarketCap, or custom scripts. While these won’t let you place orders directly during downtime, they notify you when market conditions reach critical levels. For example:
• Configure a TradingView alert when BTC/USD drops below a certain threshold
• Use IFTTT or Zapier to send SMS or email notifications
• Run a Python script that polls public Kraken API endpoints and alerts you via Telegram These tools don’t replace direct order control but provide situational awareness. If an alert triggers and Kraken is down, you can act immediately once service resumes.

  Preparing for Future Outages

  Proactive preparation minimizes the impact of unexpected downtime. Consider the following steps:
• Enable two-factor authentication (2FA) on your API keys to allow secure remote access
• Maintain a local record of active order IDs and transaction details for quick reference
• Use limit orders instead of market orders to reduce slippage risk during reconnection
• Distribute holdings across multiple exchanges to avoid single-point dependency
• Bookmark the Kraken status page and API documentation for rapid access during emergencies By treating platform reliability as part of your trading risk model, you reduce exposure to technical failures.

  Frequently Asked Questions

  Can I cancel a Kraken order via SMS or phone call during an outage?No, Kraken does not offer phone support for order cancellation or SMS-based trading. All order modifications must go through the website, app, or API. There is no customer service channel that can manually cancel orders on your behalf.

  Do limit orders stay active if Kraken goes down?Yes, limit orders placed on Kraken remain active on the exchange’s servers even during platform downtime. They are not dependent on your device or internet connection. Once the market reaches your specified price and the platform is back online, the order will execute if still valid.

  How can I check my order status if the Kraken website is down?If the website is down but the API is operational, use the QueryOrders API endpoint with your API key to retrieve order status. If both are down, you must wait until service is restored. Public block explorers cannot track exchange-based orders, as they are internal to Kraken’s system.

  Will Kraken compensate me for losses due to platform downtime?Kraken’s User Agreement does not guarantee compensation for losses resulting from service interruptions. Users are responsible for managing their own risk, including using stop-loss orders and monitoring platform status. Downtime-related losses are generally considered part of trading risk.