Is AWS Down?
AWS is experiencing a partial outage.
Active incidents
What is AWS?
Amazon Web Services (AWS) is the largest cloud computing platform, providing compute (EC2, Lambda), storage (S3), databases (RDS, DynamoDB), networking, and hundreds of other services across dozens of global regions. A vast share of the internet runs on AWS, so a disruption in a major region can ripple across countless websites, apps, and APIs at once.
Signs AWS is having problems
- EC2 instances, Lambda functions, or ECS/EKS workloads in a specific region return errors, fail to launch, or time out.
- S3 requests return 500 or 503 errors or elevated latency, breaking asset delivery and uploads for apps that depend on it.
- The AWS Management Console is slow or unreachable, or SDK/CLI API calls fail with throttling or internal errors in one region.
- Errors are confined to a single AWS region (for example us-east-1) while other regions stay healthy — AWS incidents are usually regional, not global.
Find out when your own services go down
You can check AWS here — but a heartbeat monitor tells you the moment your API, website, or cron job stops responding, so you hear about your own downtime before your users do.
Frequently asked questions
How can I tell if AWS is down?
Check the official AWS Health Dashboard at health.aws.amazon.com/health/status, which lists current events by service and region; this page mirrors that feed. Because AWS is divided into independent regions, an outage usually affects only specific services in specific regions rather than all of AWS at once, so check which region your workload runs in.
Where is the official AWS status page?
AWS publishes status at the AWS Health Dashboard, health.aws.amazon.com/health/status, which replaced the older status.aws.amazon.com page. It shows current and recent events per service and region. Issues isolated to your own account appear separately in the Personal Health Dashboard inside the AWS Console, which requires signing in.
Why does AWS show operational when I am having problems?
The public AWS Health Dashboard reflects only issues AWS has confirmed and made public, which can lag behind what you experience, and it does not surface problems isolated to your own account or resources. For account-specific impact, check the Personal Health Dashboard in the AWS Console. A single service degraded in one region can also leave the overall page reading mostly operational.
Can I get alerted when my own AWS-hosted services go down?
Yes. The AWS status page tells you when AWS itself has a confirmed problem, but not when your own application, API, or scheduled job stops working. A heartbeat monitor like CronJobPro pings your services on a schedule and alerts you the moment one stops responding, so you catch your own outages regardless of whether AWS is the cause.
Not affiliated with or endorsed by AWS. Status data is sourced from AWS's official status page (health.aws.amazon.com/health/status); for critical incidents, always verify at the official source. All trademarks are property of their respective owners.