Amazon Web Services (AWS) experienced a temporary malfunction on 15 April that disturbed several large crypto platforms and revived the concern about the dependence on the industry of centralized infrastructure.
On social media platform X, Binance, the world’s leading crypto exchange per volume, unveiled That it has temporarily suspended the recordings as a precautionary measure after confronted with connectivity problems.
The stock market confirmed that some transaction orders failed due to the AWS disturbance.
Less than an hour later, however, Binance announced that services recovered and that the recordings had resumed, although delays could continue to exist during the entire system recovery.
Another important crypto -trading platform, Kucin, reported Disruptions caused by the AWS incident. The Exchange users insured that their funds and data remained safe while the technical team was working on a solution.
Other platforms, including Crypto Wallet Rabby and Analytics Provider Debank, Also posted Service interruption messages.
The malfunction led to renewed conversations about the need for decentralized backend systems.
Santeri Aramo, co-founder of Auki Network, called the disruption certificate of centralized vulnerability. He said:
“This is precisely why we build decentralized infrastructure. No failure point. No gatekeeper. No lock on your funds. Own your keys. Own your future.”
Why AWS suffer a malfunction
The AWS disturbance took place between 12:40 pm and 1:43 am PDT, with 15 different services.
Amazon explained That the incident was caused by circuit breaks on both the primary and the back -up systems were responsible. Although most services were recovered quickly, the relational database service continued to be influenced at the time of the update.
During the malfunction, users experienced delayed answers and failed connections linked to EC2 authorities in the affected zone.
In the meantime, AWS users insured that the problem had been solved and no recurring problems were expected.
AWS currently has a dominant share in the worldwide market for cloud infrastructure.
This incident emphasized the risk of centralizing critical operations under one service provider, a riskypto platforms often want to eliminate in their core mission.