Cryptocurrency exchange KuCoin has disclosed a widespread service disruption linked to Amazon Web Services (AWS), affecting customer asset balances, internal transfers, trade settlement and several calculations used to manage leveraged positions.
The exchange published an official notice on October 13, 2026, at 21:49 according to its website timestamp, warning that some customers were experiencing abnormal account queries and difficulty accessing trading-related functions. The company attributed the problems to an AWS service issue and said customer assets remained secure.
More concerning than the inability to view balances was KuCoin’s acknowledgment that maximum tradable amounts, futures available balances, margin information and estimated liquidation prices could be inaccurate or outdated. Those figures help traders determine how much exposure they can take and whether existing positions have sufficient collateral.
The exchange has not disclosed the number of affected customers, the precise duration of the disruption or whether any traders experienced financial losses. No separate restoration notice had been independently verified at the time of reporting.
KuCoin Confirms Problems Across Asset Balances, Transfers and Trading Services
According to KuCoin’s official service disruption notice, the AWS-related failure affected several components of its trading and account-management infrastructure.
All users were temporarily unable to view their total asset overview through the exchange’s mobile application or website, while certain API balance queries returned abnormal results.
Some customers also encountered failures when transferring funds between Classic accounts and Unified Trading Accounts (UTA), including cases in which the transfer interface would not load.
Other affected services included KuCoin Convert, where settlement of certain orders was disrupted, and Classic spot trading, where orders using the Savings funding source could encounter errors.
Trading bots were not entirely unaffected. KuCoin acknowledged problems involving certain bot shutdown operations and bonus-fund queries, potentially complicating efforts to manage automated strategies during the disruption.
Customers were also temporarily unable to switch between Classic and UTA trading modes.
For users attempting to move money or complete conversions, KuCoin recommended checking transaction statuses carefully before repeating an operation. That precaution is important because an incomplete confirmation does not necessarily mean an instruction failed to reach the underlying processing system.
Futures Traders Faced Unreliable Liquidation Prices and Order-Size Calculations
The most consequential part of KuCoin’s disclosure concerns its Unified Trading Account, which combines spot, margin and futures trading within a shared account framework.
KuCoin reported abnormal queries affecting maximum tradable quantities for spot, margin and futures products, along with percentage-based order placement and quick quantity calculations.
In futures trading, available-balance queries were also affected. Depending on the circumstances, the interface could display placeholder information, remain stuck loading or continue showing previously received balance data.
The exchange additionally identified problems involving estimated order costs, cost-per-contract calculations and estimated liquidation prices on its order-placement interface and chart-based quick-order panel.
Cross-margin users faced abnormalities in queries for eligible margin tokens, index prices, risk limits and margin usage.
These are not merely decorative figures. Traders use them to determine how much collateral is available, calculate position sizes and assess their exposure to liquidation.
KuCoin explicitly warned customers that displayed balances, maximum tradable amounts and other trading-related information might be inaccurate or outdated. It advised caution when submitting orders or adjusting positions.
However, the notice does not establish that the exchange’s underlying liquidation engine or matching engine calculated positions incorrectly. The confirmed problem concerns affected queries, interfaces and related functions. Whether any incorrect execution or liquidation occurred remains unknown.
KuCoin Suggests WebSocket Updates as Temporary Alternative to REST API Queries
KuCoin recommended that UTA customers consider subscribing to WebSocket channels for real-time asset updates while the affected REST API queries remained unavailable.
Even that workaround came with an important qualification: the exchange warned that WebSocket data could be incomplete or delayed.
That creates uncertainty for automated trading systems relying on account balances, available margin and position information to determine whether orders should be placed or modified.
KuCoin also advised Classic spot traders to use assets held in their Spot Accounts rather than relying on the affected Savings funding source.
The exchange did not identify the specific AWS region, cloud service or technical component responsible for the failure. It also did not establish whether the disruption resulted from one infrastructure dependency or several interconnected services.
The incident emerged shortly after KuCoin announced its KuCoin 5.0 upgrade on October 12, emphasizing a more integrated trading experience and expanded Unified Trading Account capabilities. There is no verified evidence connecting that platform announcement or rollout to the AWS-related disruption.
Why Incorrect Risk Displays Can Be More Dangerous Than Missing Balances
The obvious inconvenience during an exchange outage is being unable to see an account balance. But the more serious trading risk appears when information is available yet potentially wrong.
A missing figure warns users that something has failed. A stale liquidation estimate or incorrect maximum order size can look entirely normal, encouraging traders to act on information that no longer represents their actual exposure.
Consider a leveraged futures position supported by $5,000 in collateral. If a trader incorrectly believes another $2,000 is available, they might attempt to increase exposure rather than preserve funds for an adverse price movement. The exchange could reject the order, but the unreliable display still undermines the trader’s decision-making process.
Similarly, an outdated estimated liquidation price can create a false impression of distance from a margin threshold. The actual consequence depends on the exchange’s backend calculations, not simply the number shown on the screen.
The distinction resembles concerns raised during SBI Securities’ recent collateral valuation and position-restoration incident, where the handling of margin and protective orders became central to understanding the risks faced by customers.
There is no evidence that KuCoin customers suffered equivalent liquidations. The comparison illustrates why reliable risk information matters even when the exchange says customer assets are secure.
Delayed Settlement Creates Another Risk: Duplicate Instructions
KuCoin’s warning about repeating transfers or Convert orders deserves attention because it concerns the difference between a transaction failing and its confirmation failing.
A trader who initiates a conversion and sees no completed status might assume nothing happened. If the original instruction subsequently settles, repeating the request could create an unintended second transaction.
The same problem can arise with internal transfers when the interface fails to refresh.
Similar uncertainty appeared in the Xendit payout disruptions in Indonesia, where repeated failures and unstable recovery complicated the distinction between service restoration and reliable transaction processing.
For KuCoin, the financial implications depend on whether transactions were actually duplicated, delayed or merely displayed incorrectly. None of those outcomes has been quantified publicly.
That uncertainty makes a detailed post-incident reconciliation important. Customers need to know which instructions were accepted, which were rejected and which completed after delayed confirmations.
Cloud Dependence Is Becoming a Trading-Risk Issue for Crypto Exchanges
The broader lesson is that cryptocurrency exchanges depend on infrastructure extending well beyond their own trading engines.
Cloud-hosted account services, balance databases, pricing feeds and API gateways can become operational dependencies for seemingly simple functions. A failure in one component may interfere with several connected customer workflows.
The distinction between platform access and actual trading infrastructure was also evident when Crypto.com experienced repeated Android login disruptions earlier in October. In that case, customers encountered access problems even though alternative browser services remained available.
KuCoin’s incident appears broader in functional scope because its disclosure includes settlement processes and calculations directly relevant to leveraged trading.
Still, it would be premature to conclude that its exchange infrastructure suffered a complete trading shutdown. KuCoin has not made that claim.
For investors, the important question is whether trading platforms have sufficiently independent fallback systems for critical account and risk information when an external infrastructure provider experiences problems.
KuCoin Needs to Clarify the Financial Impact, Not Just Restore Access
KuCoin’s assurance that customer assets remained secure addresses one important concern: a balance displaying zero does not necessarily indicate missing cryptocurrency.
But asset security and trading reliability are different issues. A customer can retain ownership of funds while experiencing difficulty transferring them, closing positions or evaluating margin requirements.
The next useful disclosure would establish when services were restored, which functions remained impaired longest and whether any orders, transfers or automated strategies were affected financially.
KuCoin should also clarify whether the disruption was limited to customer-facing calculations or extended to any backend systems responsible for order validation and risk enforcement.
Without those details, the scale of the operational failure remains difficult to assess.
The October 13 notice demonstrates that a cloud infrastructure problem can affect more than account visibility. When unreliable data reaches order-sizing, margin and liquidation interfaces, the incident becomes a question of whether traders had dependable information to manage their positions.
For a cryptocurrency exchange operating around the clock, restoring the application is only one measure of recovery. Establishing that account balances, trading calculations and transaction records are accurate is just as important.
Johan Shamshad is a financial markets writer at Dave Finances covering cryptocurrencies, trading platforms, brokers, fintech, financial regulation, and developments across global markets. He previously worked at Gulf News, adding newsroom experience to his coverage of fast-moving financial and digital-asset markets.
His work focuses on identifying market-moving events, company developments, regulatory changes, product launches, and shifts in trading and financial infrastructure.
Johan contributes news and analysis designed to help readers understand not only what happened, but why a development matters and how it may affect the wider financial landscape. You can reach out to him via his social media accounts:
Linkedin: https://www.linkedin.com/in/johan-shamshad-742851262/
X: https://x.com/Yasmine_FX
Investing: https://www.investing.com/members/contributors/279781574