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
AWS's Official Status Page

This affects you if you use...

Downstream impact when AWS is down
  • EC2 and Lambda workloads
  • S3 file storage and CDN
  • RDS databases and SQS queues
  • Any app hosted on AWS infrastructure

Component Breakdown

Specific service features status
ComponentStatus
Amazon EC2 (us-east-1) Operational
Amazon RDS Operational
Amazon Route 53 Operational
Amazon S3 (us-east-1) Operational
AWS Lambda Operational
DynamoDB Operational

⚠️ Active Outage Incidents

Active Event
Multiple services Incident

Increased failure rates.

Based on historical MTTR (53m avg), resolution is overdue — engineers are still working.
Impact Level: major Elapsed: 223693m of ~53m avg
Multiple services Incident

Increased failure rates.

Based on historical MTTR (53m avg), resolution is overdue — engineers are still working.
Impact Level: major Elapsed: 222668m of ~53m avg

90-Day Uptime Performance

History & recovery averages
SLA Grade: F Based on 90-day verified uptime
90.000%
Uptime
53m
Mean Resolution Time (MTTR)
7
Avg Incidents / Month
Active now
Last Incident
90 Days AgoToday

Past Incidents & Outage Archives

View Full 2026 Archive

AWS Service Restoration

Resolved. Services returned to baseline response profiles.

Duration: 30m Affected: Core Service

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

Community Outage Pulse

Are you having problems with AWS?

Submit your report to help alert other developers.

Downtime Reports: Last 2 Hours
2 Hours AgoNow

Get Alerted When AWS Goes Down

Free instant email alerts

Troubleshooting Guide

  1. 1
    Hard Refresh
    Bypass cache (Ctrl+F5 or Cmd+Shift+R).
  2. 2
    Flush DNS
    Run ipconfig /flushdns.
  3. 3
    Check with alternative network
    Try loading the site on a mobile cellular network or over a VPN. If it loads, the issue lies in your local ISP provider network routing.

Uptime Alternatives

GitHub

Leading developer platform.

View Status

Slack

Real-time team communication.

View Status

Frequently Asked Questions

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 53 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.

Related services you might be checking

GitHub Status GitLab Status Bitbucket Status npm Registry Status Vercel Status