AWS Outage Check
Is AWS Down Right Now?
🔴 AWS is down. A major outage was confirmed.
Increased failure rates.
Approximately 80% of users are affected.
Auto-refreshing live data in 60s
| Component | Status |
|---|---|
| Amazon EC2 (us-east-1) | Operational |
| Amazon RDS | Operational |
| Amazon Route 53 | Operational |
| Amazon S3 (us-east-1) | Operational |
| AWS Lambda | Operational |
| DynamoDB | Operational |
Multiple services Incident
Increased failure rates.
Impact: major
Multiple services Incident
Increased failure rates.
Impact: major
97.778%
Uptime
54m
MTTR
6.7
Avg Incidents / Mo
90 Days AgoToday
AWS API Gateway Timeout and Increased Error Rates
Engineers investigated a spike in 504 Gateway Timeout errors affecting public API endpoints.
Duration: 40m
Affected: API Requests, API Portal
AWS Database Failover and Connection Backlog
A hardware failure on the primary database cluster triggered an automatic failover to the replica.
Duration: 58m
Affected: Core Service, Website
AWS API Gateway Timeout and Increased Error Rates
Engineers investigated a spike in 504 Gateway Timeout errors affecting public API endpoints.
Duration: 37m
Affected: API Requests, API Portal
AWS API Gateway Timeout and Increased Error Rates
Engineers investigated a spike in 504 Gateway Timeout errors affecting public API endpoints.
Duration: 20m
Affected: API Requests, API Portal
AWS API Gateway Timeout and Increased Error Rates
Engineers investigated a spike in 504 Gateway Timeout errors affecting public API endpoints.
Duration: 1h 4m
Affected: API Requests, API Portal
Are you having problems with AWS?
Submit your report to help alert other developers.
Downtime Reports: Last 2 Hours
2 Hours AgoNow
Troubleshooting Guide
- 1Hard RefreshBypass cache (Ctrl+F5 or Cmd+Shift+R).
- 2Flush DNSRun
ipconfig /flushdns.
Uptime Alternatives
GitHub
Leading developer platform.
Slack
Real-time team communication.
Yes, AWS maintains an official status page. However, our real-time tracker aggregates reports faster.
Historical records indicate that the mean time to resolve (MTTR) is approximately 54 minutes.
Outages can happen due to configuration mistakes, database freezes, edge network issues, or infrastructure drops.
You can subscribe to live alerts on this page. We send emails on status updates.
Try bypass caching by executing hard refresh, flush local DNS, or use alternatives listed below.