Is AWS down?
Loading the latest status…
Is AWS down right now? Live status from AWS’s status page, our own checks and user reports, updated every minute.
- Official status
- Reachable
- Reports in the last hour
Detailed data for this service is briefly unavailable. The status above comes from our latest check.
AWS’s status page
Not working for me
Pick what’s broken. Your report shows up on the chart below within a few minutes.
Last 24 hours
- Operational
- Degraded
- Partial outage
- Major outage
- No data
- Reachability check (dynamodb.us-east-1.amazonaws.com)
By region
| Region | DynamoDB us-east-1 dynamodb.us-east-1.amazonaws.com | Lambda API us-east-1 lambda.us-east-1.amazonaws.com |
|---|---|---|
| N. Virginia | ||
| Oregon | ||
| Frankfurt | ||
| Singapore | ||
| Tokyo | ||
| São Paulo |
Each row shows the latest result from that region. How we check
Last 90 days
We have checked AWS ourselves since Oct 28, 2026. Earlier days come from its status page.
42 days with problems in the last 90 days.
Recent incidents
Incidents: 3 in the last 30 days and 8 in the last 90, lasting a median of 3 h 6 min.
- Elevated API issues and Launch Failures (ap-northeast-1)Degraded1 day
- Elevated Launch Failures (us-west-2)Degraded1 day
- Increased invoke error rates (us-west-2)Degraded1 day
- Elevated packet loss (eu-south-2)Degraded2 h 41 min
- Increased Error Rates (us-east-1)Degraded57 min
- Increased API Error Rates (us-west-2)Degraded2 h 17 min
- Increased Error Rates (ap-northeast-1)Degraded37 min
- Increased Error Rates (eu-west-2)Degraded3 h 32 min
- Increased Packet loss (eu-central-1)Degraded3 days
- Increased Error Rates (me-south-1)Partial outage197 days
If AWS isn’t working for you
Amazon Web Services (AWS) is Amazon's cloud platform, running compute, storage, databases and hundreds of other services for a large share of the internet.
Common AWS errors
| Error | What it means | Usually | What to do |
|---|---|---|---|
InsufficientInstanceCapacity | AWS does not have enough capacity of the requested instance type in that Availability Zone right now. | Heavy load | Try another instance type or Availability Zone, or retry later. Source |
ServiceUnavailable | The request failed because of a temporary failure of the server. | An outage | Retry with backoff and check the AWS Health Dashboard for your region. Source |
InternalError | An internal error happened on AWS's side. | An outage | Retry; if it persists, check the AWS Health Dashboard or contact AWS. Source |
RequestLimitExceeded | Your account exceeded the maximum request rate for the EC2 API. | Your side | Use an increasing or variable sleep between requests (exponential backoff). Source |
ThrottlingException | The service rejected the request because of rate limits on your account. | Your side | Let the SDK retry with backoff and reduce your request rate. Source |
UnauthorizedOperation | You are not authorized to perform this operation with the credentials you used. | Your side | Check your IAM policies and that you are using the right credentials. Source |
Is it just you?
- Check the AWS Health Dashboard for your specific region; most AWS incidents affect one region or service, not all of AWS.
- Try the same action in another region or Availability Zone to see whether the problem is local to one.
- Read the error code: throttling and authorization errors come from your account, while InternalError and ServiceUnavailable are AWS-side.
- Your account's Health Dashboard (signed in) shows events that affect your own resources, which the public page may not list.
- If only your website is down, check your own instances, load balancers and DNS before assuming an AWS outage.
Alternatives to AWS
Questions
AWS incidents are usually limited to one region or one service. Check the AWS Health Dashboard for the region and service you use rather than AWS as a whole.
Many companies host their apps, APIs and files on AWS, often in a single region. When a core service in that region fails, every app depending on it can fail at once, even apps that do not mention AWS.
AWS does not currently have enough capacity of that instance type in the Availability Zone. It is not an account problem; try another instance type or zone, or retry later.
Sources: docs.aws.amazon.com, docs.aws.amazon.com, health.aws.amazon.com
Get alerted when AWS breaks your app.
If your product depends on AWS, your users feel its outages too. Point a Site Qwality monitor at the AWS endpoint you use and at your own site, and we alert you on Slack, email, SMS or a webhook as soon as either one stops answering.