AWS statusManual checkVerified May 24, 2026Source: health.aws.amazon.com
Is AWS down?
Live status check · No widespread incident reported.
Most recent manual verification mirrored from health.aws.amazon.com. Below: the components that can break, what to do during an incident, and how to keep your scheduled jobs running independently.
About AWS status
AWS is the largest public cloud. Incidents are almost always regional and component-scoped (us-east-1 EC2, ap-southeast-2 RDS, eu-west-1 S3, etc.) and rarely take down the whole platform — but a us-east-1 IAM or DynamoDB blip can ripple through everyone else's services because so much else depends on it.
Components and surfaces that can break
- Surface 01
Per-region: EC2, ECS, EKS, Lambda, API Gateway, RDS, DynamoDB, S3.
- Surface 02
Cross-region: IAM, Route 53, CloudFront, CloudFormation control plane.
- Surface 03
Developer-facing: AWS Console, the CLI, SSO, EventBridge, Cognito.
What to do if AWS is actually down
Open the AWS Health Dashboard for your specific region
health.aws.amazon.com lists status per service per region. A green us-east-2 while us-east-1 is red is common — confirm the AZ matches yours before you escalate.
Don't fail over us-east-1 only workloads on impulse
IAM, CloudFront, and Route 53 control planes all sit in us-east-1. A regional incident there can break things in other regions briefly. Wait 10-15 minutes before triggering a cross-region failover unless the runbook is well-tested.
Re-fire missed EventBridge schedules manually
EventBridge scheduled rules can be skipped during platform incidents and don't catch up. If a cron-driven Lambda missed a run, invoke it once manually so state moves forward.
Keep firing through the incident
Schedule your own AWS health check with Crontap
EventBridge schedules are the default cron primitive on AWS but they don't retry missed fires and they require IAM glue per target. Crontap calls the Lambda Function URL directly, retries on 5xx, and stores the response — no event bus to configure, no role to attach.
External HTTP cron hits your endpoint on the cadence you pick, stores every response, and emails you the moment a run fails. Pro schedules down to 1 minute; $3.25/mo annual flat for unlimited jobs.
Go deeper
AWS status: FAQ
- How do I check AWS status by region?
- The AWS Health Dashboard at health.aws.amazon.com splits status by service and by region. The legacy status.aws.amazon.com page still works and publishes an RSS feed if you want a programmatic mirror.
- Why didn't my EventBridge cron rule run during the outage?
- EventBridge schedules are best-effort. During platform incidents, individual fires can be skipped and there is no built-in catch-up. The CloudWatch metric InvocationsSentToDlq stays at 0 because nothing was attempted.
- Can Crontap trigger AWS Lambda without EventBridge?
- Yes. Enable a Lambda Function URL on your function (or front it with API Gateway) and point Crontap at the URL. You skip the EventBridge target + IAM role + permission boundary dance, and you get retries and a run log for free. See the cron jobs for AWS Lambda spoke.