Amazon help and reporting
Amazon retail and digital-content support are separate from AWS Health.
Live Domain Check
Run a live reachability check for amazon.com. Compare the regional responses with the problem you see in Amazon.
Find Amazon help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Amazon shopping, checkout, order access and account sign-in are separate from AWS infrastructure services.
The checker above requests amazon.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Amazon action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Separate shopping, seller management, payment and advertising entrypoints when reporting an Amazon problem: Amazon Seller Central status check, Amazon Pay status check, Amazon Advertising status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse shopping and payment checks.
Amazon retail and digital-content support are separate from AWS Health.
Open the website in your browser and compare it with the result above. This link opens the service, not its status page.
We have not linked a separate status page for this service. Check the official help page for current notices.
Open Amazon help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Marketplace, order state/reference privately, action, payment error and time.
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 Amazon.
These are troubleshooting comparisons, not claims that Amazon is currently experiencing a particular incident.
Check Your Orders and confirmation messages before repeating an uncertain purchase.
Use Amazon retail customer service for the affected order or account; AWS Health alone is not evidence of an Amazon shopping outage.
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.
Use these local troubleshooting steps after the down-check workflow when Amazon seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open 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.
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 Amazon issue.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Amazon support.
Run the amazon.com check and compare its original timestamps and responses with your actual error. Amazon shopping, checkout, order access and account sign-in are separate from AWS infrastructure services.
Use the official help/reporting resource linked above. Amazon retail and digital-content support are separate from AWS Health.
Check Your Orders and confirmation messages before repeating an uncertain purchase. Use Amazon retail customer service for the affected order or account; AWS Health alone is not evidence of an Amazon shopping outage.
Marketplace, order state/reference privately, action, payment error and time.