Live Domain Check

Is AWS Down? Check aws.amazon.com Status and Outages

Run a live reachability check for aws.amazon.com. Compare the regional responses with the problem you see in AWS.

Find AWS help and reporting links, specific checks, and step-by-step guidance below the live result.

Ready

Running automatic check…

Checking reachability from multiple regions.

Checked -

Verdict -

Response Time -

Final URL -

Regional checks 8 regions

Rate:

No ratings yet.

Is AWS working for you?

Share a quick update and see what other visitors are experiencing.

Loading community reports…

Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy

Understanding AWS connection and service problems

The AWS public site does not test your workload. A service incident can be specific to a region, account or resource.

The checker above requests aws.amazon.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual AWS action that failed. A homepage response alone cannot verify an account, app workflow or transaction.

Looking for another service? Browse infrastructure checks.

AWS status information and official help

AWS service status

Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.

AWS help and reporting

Public AWS Health and account-specific Health can have different scopes.

Open aws.amazon.com

Open the website in your browser and compare it with the result above.

Where to report problems with AWS

Open AWS help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.

Details to include in your report

Service, region, affected resource, request ID, UTC window and recent deployment/configuration change.

Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to AWS.

What to check when AWS is not working

These are troubleshooting comparisons, not claims that AWS is currently experiencing a particular incident.

Start with the action that failed

Identify the AWS service and region, then compare public Health information with account-specific AWS Health if accessible.

Narrow down the affected service

Check the affected resource's own metrics and request errors before applying changes across unrelated regions.

Read the actual checker response

A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.

How to check if AWS is down

Save the error. Note what you were doing and when it failed. Save unfinished work before refreshing.
Run the aws.amazon.com check. Look at the regional results and when they were checked. Checking again may return a cached result.
Check for a service notice. Open AWS status and check whether the named service and incident time fit your error.
Try another browser or network. Use the specific checks above to narrow down the problem. If it continues, send the error and time through the official help link.

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, compare its account, cookie and extension context before assuming the entire service is unavailable.

2. Preserve a working account session

Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader AWS issue.

3. Try another network

If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.

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 about AWS problems

Is AWS down, or is the problem limited to one feature?

Run the aws.amazon.com check and compare its original timestamps and responses with your actual error. The AWS public site does not test your workload. A service incident can be specific to a region, account or resource.

Where can I report a problem with AWS?

Use the community buttons on this page to share whether the service works for you. For help from AWS, use the official help/reporting resource linked above. Public AWS Health and account-specific Health can have different scopes.

What should I check first when AWS is not working?

Identify the AWS service and region, then compare public Health information with account-specific AWS Health if accessible. Check the affected resource's own metrics and request errors before applying changes across unrelated regions.

What information helps AWS support investigate?