AWS Health Dashboard
Official AWS health summary for service and regional events.
Live Domain Check
Is AWS Down? Check aws.amazon.com Status and Outages
Check if AWS is down right now (aws.amazon.com). Run a live multi-region check to see whether AWS is offline for everyone or just you.
Get official AWS outage status updates, support links, and targeted troubleshooting steps in one page.
Ready
Running automatic check…
Checking reachability from multiple regions.
Checked
-
Verdict
-
Response Time
-
Final URL
-
Regional checks
About AWS Outages and Server Issues
AWS incidents are often regional and product-specific, so some workloads remain healthy while others fail. This page helps quickly verify whether reachability issues align with a larger cloud incident.
For AWS, incident signals are often feature-specific: Management Console access works, but service API calls starts failing for many users. Instability appears around regional endpoint behavior during normal traffic. If this matches what you see on aws.amazon.com, it usually points to partial degradation instead of a full outage, so confirm with official status updates and a second-network retest.
Official AWS Status, Support, and Social Channels
Use official sources first, then social/community signals to estimate incident scope and speed of recovery.
AWS Support
Official incident support and escalation guidance for AWS customers.
AWS Service Health
Additional AWS status feed for service disruptions.
X Live Updates
Real-time posts and official updates related to AWS incidents.
Official AWS Social Profiles for Live Updates
Official teams often post outage status updates and recovery progress through these social channels.
Common AWS Problem Patterns
Recognizing these patterns helps you avoid false assumptions and escalate with better evidence.
How to Check if AWS Is Down
Practical steps to follow when aws.amazon.com seems down. Use this checklist to confirm whether AWS is down for everyone or only for you.
1. Check in two places
Run aws.amazon.com in WebsiteDown.org first, then open aws.amazon.com in your own browser. If results disagree, the issue is often local rather than global.
2. Verify service status
Check the official AWS service status page and compare timestamps with your failed checks.
3. Isolate network path
Test related hosts such as amazon.com, www.amazon.com. If they work while aws.amazon.com fails, this points to a partial endpoint issue.
4. Escalate with evidence
Capture final URL, status code, and response time for aws.amazon.com, then share those details with AWS support for faster triage and recovery.
If AWS Is Not Working Only For You, Start Here
Use these local troubleshooting steps after the down-check workflow when AWS seems broken only for you. This section focuses on app, browser, account, and network fixes.
1. Compare browser sessions
Open aws.amazon.com in your current browser, then test in a private window or second browser. If only one session fails, the issue is usually local cache, cookie, or extension state.
2. Reset account session once
Sign out and sign back in one time, then retry the failing action on aws.amazon.com. Avoid repeated password or security resets until you confirm this is not a broader AWS issue.
3. Remove network interference
Temporarily disable VPN, proxy, private DNS, and filtering extensions. Then switch between Wi-Fi and mobile data to isolate route-level differences.
4. Capture support-ready evidence
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting AWS support.
Frequently Asked Questions
Is AWS down for everyone or just me?
Run the automatic multi-region check on this page for aws.amazon.com. If most regions fail at the same time, AWS is likely experiencing a broader outage.
If only one or two regions fail, the issue is usually local to your route, resolver, device state, or account session. Recheck after 2 to 5 minutes and compare Wi-Fi with mobile data.
Where can I find official and real-time AWS outage updates?
Use this order so you get reliable signal quickly:
- Official status: AWS Health Dashboard
- Support guidance: AWS Support
- Product context: AWS Service Health
- Live chatter: X Live Updates and Reddit Community Reports
Official dashboards are the source of record, but social channels can surface impact faster in the first minutes of an incident.
Why is AWS down for me but up for others?
That usually means a route-specific or client-specific issue instead of full provider downtime. Common reasons:
- A regional control plane is degraded while global pages remain reachable
- Identity providers or token services fail before core endpoints fail
- One upstream transit path is unstable from your network
- DNS resolver or firewall policy creates local false-down signals
Try a private window, switch networks, and compare with this page's regional result before making major local changes.
What should I do first if AWS is not working?
Use this quick triage sequence:
- Run this live check for aws.amazon.com
- Check AWS Health Dashboard and AWS Support
- Test management console access and service api calls from a second network
- Capture failing endpoint, response code, and timestamp for regional endpoint behavior or identity and token validation
- Then apply local fixes (cache, DNS, app reset) only if results point to a local issue
This keeps your troubleshooting efficient and avoids unnecessary account resets during provider-side incidents.