Scan to download
BTC $71,227.89 -3.27%
ETH $2,002.14 -0.24%
BNB $691.79 -2.51%
XRP $1.29 -2.90%
SOL $81.02 -1.78%
TRX $0.3430 -2.25%
DOGE $0.1009 +0.59%
ADA $0.2307 -2.14%
BCH $293.06 -3.40%
LINK $9.05 -0.90%
HYPE $73.59 +2.25%
AAVE $80.14 -2.47%
SUI $0.8777 -2.12%
XLM $0.2417 -6.30%
ZEC $542.21 -5.00%
BTC $71,227.89 -3.27%
ETH $2,002.14 -0.24%
BNB $691.79 -2.51%
XRP $1.29 -2.90%
SOL $81.02 -1.78%
TRX $0.3430 -2.25%
DOGE $0.1009 +0.59%
ADA $0.2307 -2.14%
BCH $293.06 -3.40%
LINK $9.05 -0.90%
HYPE $73.59 +2.25%
AAVE $80.14 -2.47%
SUI $0.8777 -2.12%
XLM $0.2417 -6.30%
ZEC $542.21 -5.00%

dent

Coinbase reviews the May outage incident: AWS cascading failure exposes architectural risks

Coinbase released a retrospective report on the large-scale service interruption event on May 7, 2026.The outage lasted approximately 8 hours, with full recovery taking about 12 hours. During this time, trading, deposits, withdrawals, and most core services were unavailable or severely degraded. Coinbase stated that the outage was caused by multiple cooling units failing simultaneously in the cooling system of a data center in one availability zone (use1-az4) in the AWS us-east-1 region, triggering cabinet thermal protection shutdowns, which led to EC2 instances and EBS volumes going offline, affecting multiple internet services.During the recovery process, the Coinbase trading matching engine lost quorum due to the cluster architecture deployed in a single AWS data center losing most nodes. It required urgent code adjustments and the reconstruction of a new node group to restore operation, gradually restarting market trading during the recovery.Additionally, the AWS-managed Kafka (MSK) service experienced control plane failures, preventing the automatic re-election of partition leaders, further blocking quotes, fees, and some settlement and data flow systems, which expanded the overall impact.After manual partition migration in collaboration with the AWS engineering team, the system gradually returned to normal. Coinbase stated that this incident exposed its shortcomings in cross-availability zone automatic switching capabilities and disaster recovery for managed middleware. The company will upgrade its cross-region hot backup architecture, strengthen regular failure drills, and migrate the Kafka system from dual availability zones to a three availability zone deployment, while also working with AWS to advance root cause fixes and improvements.

THORChain has released a recovery plan for the attack incident, and voting for node operators has begun

THORChain has released its fourth update regarding the attack incident on May 15, and the proposal ADR028 has been announced, with voting for node operators now open.According to the recovery plan, the protocol will first absorb losses through its own liquidity, with the remaining portion to be shared by synthetic asset holders; the specific distribution ratio of the two is still under evaluation. The protocol's own liquidity will be reduced to zero, and will be gradually replenished through system revenue. This plan will not issue or sell RUNE, nor will it dilute any holders.On the technical side, GG20 will be temporarily retained and has completed patch upgrades. Trading will resume after the vulnerabilities are fixed and node rotation is successfully conducted, with a future release pace that is slower and more security-conscious. Innocent nodes located in the same vault as the attacker will be protected, while the attacker nodes will be fully confiscated. The recovered RUNE will be paired with the recovered assets, and any excess will be destroyed.The protocol also offers a white hat bounty to the attacker to recover funds; if some are returned, the recovery plan will be adjusted proportionally. THORChain remains neutral and permissionless, and there will be no review of the attacker's Swap transactions after trading resumes. Node operators are currently voting on the proposal direction, and the numbers in the ADR are only indicative, with adjustments to be made through Mimir later.
app_icon
ChainCatcher Building the Web3 world with innovations.