Amazon Customer Service
Official customer support entry point.
Live Domain Check
Check if Amazon is down right now (amazon.com). Run a live multi-region check to see whether Amazon is offline for everyone or just you.
Get official Amazon outage status updates, support links, and targeted troubleshooting steps in one page.
Checking reachability from multiple regions.
Amazon outages are often partial: product pages can load while checkout, sign-in, or order history fails. Third-party blockers, corporate DNS, and region-specific edge routing can also create 'down for me' behavior. During high-traffic events, cart, payments, and account APIs may degrade first, so checking multiple Amazon sub-services helps confirm real scope faster.
For Amazon, incident signals are often feature-specific: Homepage loads but product detail pages timeout. Checkout and payment flows fail while browsing works. If this matches what you see on amazon.com, it usually points to partial degradation instead of a full outage, so confirm with official status updates and a second-network retest.
Amazon retail does not publish a single detailed public outage dashboard for all consumer traffic. Use official support channels and direct checks. AWS Health is only relevant for AWS services.
Official customer support entry point.
Official status for AWS services (not a direct amazon.com retail status page).
Official help topics for common account and ordering issues.
Monitor real-time social updates and official posts related to Amazon outages.
Official teams often post outage status updates and recovery progress through these social channels.
Use these service-specific patterns to identify likely root cause quickly and choose the right next step.
Practical steps to follow when amazon.com seems down. Use this checklist to confirm whether Amazon is down for everyone or only for you.
Run amazon.com in WebsiteDown.org first, then open amazon.com in your own browser. If results disagree, the issue is often local rather than global.
Check the official Amazon service status page and compare timestamps with your failed checks.
Test related hosts such as www.amazon.com, smile.amazon.com. If they work while amazon.com fails, this points to a partial endpoint issue.
Capture final URL, status code, and response time for amazon.com, then share those details with Amazon support for faster triage and recovery.
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, the issue is usually local cache, cookie, or extension state.
Sign out and sign back in one time, then retry the failing action on amazon.com. Avoid repeated password or security resets until you confirm this is not a broader Amazon issue.
Temporarily disable VPN, proxy, private DNS, and filtering extensions. Then switch between Wi-Fi and mobile data to isolate route-level differences.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Amazon support.
Run the automatic multi-region check on this page for amazon.com. If most regions fail at the same time, Amazon is likely experiencing a broader outage or partial incident.
If only one or two regions fail, the issue is usually local to your network path (DNS resolver, ISP route, VPN/proxy, or firewall). Re-check after 2 to 5 minutes and compare Wi-Fi with mobile data.
Use the Official Status, Support, and Social Channels section above in this order:
Official dashboards are authoritative but can lag during the first minutes of an incident. Combine those sources with this checker to confirm whether Amazon is down globally, regionally degraded, or only affecting specific users.
That pattern usually points to path-specific issues rather than a full Amazon outage. Common causes include:
Test in a private window, temporarily disable VPN/extensions, and retry from a second network. If one feature fails while the homepage still loads, treat it as a partial incident.
Use this quick triage sequence for amazon.com:
This order helps you avoid unnecessary account resets when the Amazon issue is provider-side.