Is AWS down right now?
Real-time AWS status from health.aws.amazon.com. AWS publishes a public RSS feed of service events across all 200+ services and regions. We aggregate that feed into a single status indicator. For granular per-service, per-region detail, click the official link to drill into the AWS Health Dashboard.
Major outage: AWS
AWS
Major outageEC2, S3, Lambda, RDS, and 200+ services.
Status from health.aws.amazon.com · last fetched 1s ago
Developer Platforms
Upstream returned 404
Upstream returned 404
Atlassian source hosting and Pipelines.
Source hosting, Actions, Pages, Packages, Copilot.
macOS / Linux package manager (uses GitHub).
JavaScript registry, install API, web app.
Python Package Index — pip install backend.
AI / ML APIs
Elevated errors across many models on Anthropic — started 1 hr ago
FedRAMP workspaces and API orgs have degraded performance — started 21 hr ago
Upstream returned invalid JSON
Elevated errors across many models — started 1 hr ago
AI pair programmer — completions, chat, agents.
Gemini API, Vertex AI, AI Studio.
Run open-source ML models via API.
Cloud / Hosting
Service disruption: Increased Error Rates — started 47 days ago
Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas is experiencing intermittent periods of elevated latency and possible packet loss. — started 7 days ago
Cloudflare is aware of and investigating Workers AI experiencing degraded availability in some models. — started 5 hr ago
Upstream returned 404
Upstream returned invalid JSON
Droplets, App Platform, managed databases.
Global app servers, Postgres, volumes.
Azure VMs, App Service, AKS, Azure SQL.
Static + Jamstack hosting, Functions, Forms.
Web services, cron, Postgres, Redis.
Next.js hosting, Edge, Serverless functions.
Databases / Data
Upstream returned 404
Upstream returned invalid JSON
Upstream returned invalid JSON
Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain) — started 106 days ago
Serverless MySQL, Vitess-backed.
Postgres, auth, storage, realtime, edge fns.
Payments / Infra
Whatsapp Media Message Delivery Errors — started 2 hr ago
Upstream returned invalid JSON
Upstream returned 404
Upstream returned 404
Developer-first transactional email API.
Transactional + marketing email at scale.
Auth / Identity
Communication
Trouble submitting workflow forms with file attachments on Android. — started 3 hr ago
No public machine-readable feed; consult the official status page.
Voice, video, text servers and DMs.
Service Degradation Affecting Zoom Meeting Recordings — started 1 day ago
Monitoring / Dev Tools
Upstream returned invalid JSON
Upstream returned invalid JSON
APM, infra, logs, RUM, synthetics.
Figma Make and Agent Service Disruption — started 1 hr ago
Feature flags, experiments, releases.
Error monitoring, performance, replays.
DevZone aggregates publicly available status data and refreshes every 30 seconds. Status indicators reflect each provider’s own machine-readable feed; for incident details and authoritative information, always consult the official status page linked on each card.
AWS 90-day incident history
Last 90 days
98.89% incident-free
Quick facts about AWS
- AWS publishes an RSS feed at status.aws.amazon.com/rss/all.rss.
- Outages are almost always region-scoped (e.g., us-east-1 can be down while eu-west-1 is healthy).
- us-east-1 historically experiences more incidents than any other region — it hosts global control planes for IAM, S3, Route 53, and more.
- AWS Health Dashboard (signed-in) shows account-specific events not in the public feed.
How do I know if it's AWS or my own setup?
- Try the same operation from a different AWS region — if it works, the issue is region-scoped.
- Check the AWS Service Health Dashboard at health.aws.amazon.com/health/status for detailed per-service status.
- For account-specific events (Lambda concurrency limits, EC2 instance retirements), use the Personal Health Dashboard (signed-in).
- Down detector aggregators often flag AWS outages 5–30 minutes before the official feed.
Frequently asked questions
Is us-east-1 always down?
Not always — but us-east-1 hosts AWS’s global control plane for IAM, Route 53, CloudFront, and S3 multi-region buckets, so an issue there often cascades to other regions. The 90-day heatmap above shows the actual outage rate.
Why is my Lambda failing in one region but not another?
This is the canonical sign of a regional AWS outage. Check the AWS card above and the official AWS Health Dashboard (https://health.aws.amazon.com/health/status). Multi-region failover is the long-term mitigation.
How do I report an AWS outage?
AWS doesn’t take public outage reports. Open a Support case if you have a paid Support plan; otherwise, AWS internal monitoring will detect the issue (usually before the public feed updates).
Does AWS have a status API?
The public feed is RSS at status.aws.amazon.com/rss/all.rss. The signed-in AWS Health API (https://health.aws.amazon.com) requires authentication and a Business or Enterprise Support plan.