Kraken service status
Open the provider’s incident information and match its component, region and update time to your problem. A status-page headline does not test your individual account.
Live Domain Check
Run a live reachability check for kraken.com. Compare the regional responses with the problem you see in Kraken.
Find Kraken help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Kraken account access, trading and asset-specific transfers can fail separately.
The checker above requests kraken.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Kraken action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Open the provider’s incident information and match its component, region and update time to your problem. A status-page headline does not test your individual account.
Match the affected asset/network/product and use authenticated account support.
Compare the website entrypoint with your browser or app. This website link is separate from a provider incident dashboard.
Match the affected asset/network/product and use authenticated account support.
Open Kraken help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Product, asset/network, transaction/order reference privately, state/error and UTC time without recovery secrets.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Kraken.
These are troubleshooting comparisons, not claims that Kraken is currently experiencing a particular incident.
Read the transaction/order status before repeating an action and note the affected asset/network.
Compare that service on Kraken Status and use authenticated Kraken support for account-specific evidence.
A 403 or 429 means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Kraken seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open kraken.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Kraken issue.
Compare Wi-Fi and mobile data only where you are permitted to do so. Keep required VPN, proxy and security controls in place, and record which network fails.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Kraken support.
Run the kraken.com check and compare its original timestamps and responses with your actual error. Kraken account access, trading and asset-specific transfers can fail separately.
Use the official help/reporting resource linked above. Match the affected asset/network/product and use authenticated account support.
Read the transaction/order status before repeating an action and note the affected asset/network. Compare that service on Kraken Status and use authenticated Kraken support for account-specific evidence.
Product, asset/network, transaction/order reference privately, state/error and UTC time without recovery secrets.