Incident Overview
On April 15, 2025, a critical power failure occurred at Amazon Web Services' (AWS) AP-NORTHEAST-1 data center in Japan, specifically impacting Availability Zone APNE1-AZ4. The simultaneous failure of both primary and backup power systems caused widespread service disruptions across multiple cryptocurrency exchanges and DeFi platforms.
👉 How crypto exchanges mitigate cloud outages
Technical Details of the Outage
Root Cause Analysis
- Dual power system failure: Unprecedented simultaneous outage of primary and backup power infrastructure
Impacted services:
- EC2 instances
- AWS Relational Database Service (RDS)
- Increased API error rates and latency
Geographic Specifics
- Region: AP-NORTHEAST-1 (Tokyo)
- Availability Zone: APNE1-AZ4 (isolated incident)
Timeline of Events
| Time (UTC+0) | Event |
|---|---|
| 07:40 | Initial power failure detected |
| 07:45 | AWS engineering team begins investigation |
| 08:20 | Partial restoration begins |
| 08:43 | Full service restoration |
Affected Platforms and Responses
Major cryptocurrency services impacted included:
- Binance (temporarily suspended withdrawals)
- KuCoin
- DeBank
- Various DeFi applications
Exchange response protocols:
- Immediate system status notifications
- Temporary suspension of critical operations
- Gradual restoration as AWS services stabilized
AWS Recommendations for Users
AWS advised customers to:
- Replace affected EC2 instances
- Migrate impacted EBS volumes
- Monitor AWS Console for updates
- Implement cross-AZ redundancy strategies
👉 Best practices for exchange disaster recovery
FAQs About the AWS Outage
Q: How long did the AWS outage last?
A: The disruption lasted approximately 63 minutes, from 07:40 to 08:43 UTC.
Q: Was cryptocurrency trading completely stopped?
A: No, but several exchanges temporarily suspended withdrawals as a precautionary measure.
Q: Could this outage have been prevented?
A: While redundant systems typically prevent such events, the simultaneous failure of both power systems represents an extremely rare scenario.
Q: Should users be concerned about fund safety?
A: No funds were at risk as exchanges implemented standard security protocols during the outage.
Q: How can exchanges prevent similar disruptions?
A: Implementing multi-cloud strategies or distributing infrastructure across multiple availability zones enhances resilience.
Key Takeaways for Cloud Users
- Always design for failure: Implement multi-AZ architectures
- Monitor dependencies: Understand critical third-party services
- Have fallback plans: Prepare manual override procedures
- Communicate proactively: Keep users informed during incidents