Binance, KuCoin, MEXC report service issues due to AWS network interruption

Binance, KuCoin, MEXC and other exchanges and wallet providers have been experiencing service issues due to a significant network interruption by Amazon Web Services (AWS).

Centralized cryptocurrency exchanges (CEXs) were hit by an AWS data center outage, which reported “connectivity issues” that affected at least 12 of its services on April 15.

*AWS Service health. Source:* *Health.aws.amazon*

“We are seeing initial signs of recovery but continue to monitor and work toward full recovery. Other AWS services are also impacted by this issue, and are also observing recovery. We will provide another update within the next 30-60 minutes,” AWS said in an April 15 update.

Binance was among the first to report issues with its services.

“We are aware of an issue impacting some services on the #Binance platform due to a temporary network interruption in the AWS data center,” wrote Binance in an April 15 X post, adding that “some orders are still successful, but some are failing. If users failed, they may keep retrying.”

Binance has since restored services, including user withdrawals, thanks to the exchange’s quick collaboration with AWS, a Binance spokesperson confirmed to Cointelegraph.

Other large exchanges, including KuCoin and MEXC, also reported service interruptions.

“Due to a large-scale network outage with AWS services, our platform is currently experiencing temporary disruptions,” KuCoin said in an April 15 X post.

On MEXC, users of the mobile app and web platform were warned of “abnormal candlestick charts, failed order cancellations” and asset transfer delays. However, users’ assets “remain fully secure,” the exchange said in an April 15 X post.

AWS provides cloud infrastructure for centralized exchanges that can handle high transaction volumes with low latency in trading orders. AWS is used by some of the biggest crypto exchanges, including Coinbase, Crypto.com, Huobi, BitMEX and Kraken.

The effect of the AWS outage may be perceived as another signal of the vulnerability of centralized infrastructure providers, which may suffer cascading effects due to a single point of failure.

This is a developing story, and further information will be added as it becomes available.