Is Amazon down?
Having trouble opening Amazon, finding products, signing in, or placing an order? Use the checks below to distinguish a broader Amazon availability problem from a browser, device, network, account, or checkout issue.
Site Administrator
Last reviewed: September 25, 2026
LATEST RECORDED STATUS
Up Amazon’s website appeared to be up and responding normally at the last check.
| Endpoint | Status | Observed |
|---|---|---|
| amazon.com | Operational | 2026-11-09 12:33 UTC |
Is it working for you?
0 recent reports — more reports are needed for a useful trend.
What this check can tell you
- Test the homepage, a product page, search, account access, and checkout separately; Amazon features can fail independently.
- Compare a normal browser session with a private window, another browser, or the Amazon app before changing account settings.
- Switch between Wi-Fi and mobile data to distinguish a local network or DNS problem from a broader availability issue.
- If only checkout, payment, sign-in, orders, or order history fails, treat it as a workflow or account problem rather than assuming the entire site is down.
- Do not repeatedly submit an order or payment while checkout is unstable; first confirm whether the order was created.
- Amazon retail and Amazon Web Services are separate services and should be investigated in separate contexts.
About Amazon reliability
What an Amazon outage can affect
Amazon availability is not limited to the homepage. A problem may affect product pages, search, account access, order history, checkout, payments, or parts of the Amazon app while other functions continue working.
Use the scope of the failure to narrow the likely cause:
- Wider Amazon outage: Several unrelated Amazon functions fail across more than one device or network.
- Regional or feature-specific issue: The homepage works, but search, checkout, orders, account access, or another function fails.
- Local device or network issue: Amazon works elsewhere, but not on your device, browser, Wi-Fi connection, or DNS path.
- Account or transaction issue: Browsing works, but sign-in, payment, order submission, or order history does not.
- Separate AWS issue: Amazon Web Services is distinct from the consumer Amazon shopping service. An AWS incident should not automatically be treated as an Amazon retail outage.
This page is an independent availability and troubleshooting guide, not an official Amazon incident notice.
How to troubleshoot Amazon
Troubleshooting Amazon problems
Check for a wider outage first
- Reload once and record the exact error, blank page, timeout, or failed action.
- Try more than one function, such as the homepage, a product page, search, and checkout.
- Test Amazon on another device or network. The same failure across both makes a wider or regional issue more plausible.
- If checkout or payment fails, do not keep submitting the order. Check your orders and email notifications before trying again.
When Amazon works in another browser or device
The cause is probably local to the original browser or device. Open Amazon in a private window, disable extensions that modify pages or block scripts, clear Amazon site data, and update the browser. If the app is affected, force-close it and compare the website with the app.
If private browsing fixes the problem, stale cookies, cached site data, or an extension conflict are more likely than a complete Amazon outage.
When Amazon fails on Wi-Fi but works on mobile data
This pattern points to the Wi-Fi network, router, DNS resolution, or an upstream network path. Restart the device and router, compare another connection, and contact the affected network or DNS provider if the problem persists. Avoid repeatedly changing Amazon account settings when changing networks clearly changes the result.
When pages time out or do not load
A timeout can result from a local connection problem, DNS failure, regional routing issue, or a temporary Amazon-side problem. Compare another Amazon page, device, and network. Record whether the failure is a browser error, a blank response, or an HTTP status code.
When sign-in or account pages fail
First check whether public Amazon pages load. If browsing works but sign-in or account pages do not, try a private window and remove stale Amazon cookies. Confirm that you are using the intended account, and never share passwords, verification codes, or payment details while troubleshooting.
When search, checkout, payment, or orders fail
A working product page does not prove that checkout or order services are working. Test browsing separately from the affected workflow. Before placing another order, verify the order list, confirmation messages, and email notifications to reduce the risk of duplicate submissions.
When an Amazon app or third-party integration fails
Compare the Amazon website with the app. If only the app fails, update it, force-close it, and test the same task in a browser. If a third-party integration or API-dependent tool is affected while Amazon works normally, check that tool's status, credentials, permissions, and documentation rather than assuming the retail site is down.
When Amazon returns a server or gateway error
HTTP 500, 502, 503, and 504 responses can indicate a temporary server, gateway, or upstream routing problem, but may also be limited to one request path or feature. Record the code, retry later, and compare another device or network. Use the relevant error guide for the response you received.
If the problem involves AWS
Do not use the consumer Amazon page to diagnose an AWS console, API, or cloud-resource problem. Identify the affected AWS service and region, then investigate it in the Amazon Web Services context instead.
Related troubleshooting guides
TROUBLESHOOTING GUIDE
500 Internal Server Error
A 500 Internal Server Error means the server encountered an unexpected problem while processing the request. The browser usually cannot identify the cause, so start by matching the failure time with PHP, application, and web-server logs. Recent code, plugin or theme changes, `.htaccess` rules, permissions, resource limits, and deployment settings are common causes.
TROUBLESHOOTING GUIDE
502 Bad Gateway
A 502 Bad Gateway means a reverse proxy, load balancer, or CDN could not obtain a valid response from the backend server. Check the backend process, proxy error log, upstream host or port, socket permissions, resource limits, and CDN-to-origin access. The fault is usually between servers rather than in the browser.
TROUBLESHOOTING GUIDE
503 Service Unavailable
A 503 Service Unavailable response means the service cannot handle the request at that time. Common causes include exhausted CPU, memory, worker, or connection capacity; incomplete maintenance mode; an unavailable database or other dependency; or a proxy, WAF, rate limiter, or load balancer returning 503. Identify which layer generated the response, then review logs and resource usage before changing settings.
TROUBLESHOOTING GUIDE
504 Gateway Timeout
A 504 Gateway Timeout means a proxy, CDN, load balancer, or gateway waited for a backend response but its timeout expired first. The backend may still be running; common causes include slow database queries, overloaded workers, long-running tasks, delayed third-party services, and restrictive intermediary timeouts. Compare direct backend timing with the full gateway path before changing timeout settings.
TROUBLESHOOTING GUIDE
DNS_PROBE_FINISHED_BAD_CONFIG
DNS_PROBE_FINISHED_BAD_CONFIG usually means your device or local network cannot use its configured DNS server correctly. First determine whether multiple websites fail, then restore automatic DNS settings, flush the DNS cache, and test without a VPN or proxy. If only one domain fails across unrelated networks, its nameserver delegation may be misconfigured.
TROUBLESHOOTING GUIDE
DNS_PROBE_FINISHED_NXDOMAIN
DNS_PROBE_FINISHED_NXDOMAIN means DNS could not find the exact hostname requested. Check the spelling, subdomain, authoritative nameservers, required A, AAAA, or CNAME record, and domain registration status. If the DNS change was recent, cached negative responses may persist; it is usually a DNS or domain configuration issue rather than a web-server outage.
TROUBLESHOOTING GUIDE
ERR_CONNECTION_TIMED_OUT
`ERR_CONNECTION_TIMED_OUT` means the browser waited for the destination server or an intermediary to respond, but no usable response arrived before the connection timeout. Common causes include an unreachable or overloaded server, a firewall silently dropping traffic, incorrect DNS, a broken network route, or a CDN or proxy that cannot reach the origin. Test from another network first, then check DNS, infrastructure health, firewall rules, and resource usage.
TROUBLESHOOTING GUIDE
ERR_CONNECTION_REFUSED
ERR_CONNECTION_REFUSED means the browser reached a destination address, but the connection was rejected before the website returned a response. Common causes include a stopped web server, no process listening on port 80 or 443, a service bound only to localhost, an incorrect DNS destination, or a firewall rule blocking access. Check the destination and listener first, then test from an external network.
Sources & references
Sources and scope
For current account, order, payment, and service information, consult Amazon's own website, app, Help resources, and any service communication shown there. When contacting Amazon support, provide the affected function, exact error message, device or app involved, network used, and approximate time of failure.
For AWS console, API, or cloud-resource problems, consult Amazon Web Services documentation and service-status resources separately from Amazon retail support. This page is not an official Amazon incident notice.
How this check works
Every time this page loads, our server makes its own request to amazon.com (and its API domain, when applicable) and reports what it got back — a real HTTP response, a timeout, or a connection failure. That result is cached for up to 2 minutes.
This confirms external reachability; it does not test every feature, region, account, or network path. Cross-check the official status page when one is available.
Embed this live status badge
Add this badge to a dashboard, documentation page, or blog. The badge reads the cached Erriscope observation and links back to this status page.
<a href="https://erriscope.com/status/amazon/"><img src="https://erriscope.com/status/badge/amazon.svg" alt="Amazon status on Erriscope" width="210" height="34"></a>Frequently asked questions
Is this the same as Amazon's official status page?
No. This is a live, one-off connectivity check run from our own server, not Amazon's own incident reporting. Their official status page can show partial, regional, or component-level issues our single external check cannot detect.
Why does this show "Up" when Amazon feels slow or broken for me?
A basic reachability check confirms that the server responded to our request. It does not test every feature, region, ISP, browser, or account-specific issue.
How often is this checked?
A check is refreshed after the two-minute cache expires. The displayed check time shows when the observation was made.
Does an API outage mean the whole product is down?
Not necessarily. Many services split their website and API onto separate infrastructure, so one can fail while the other keeps working.
Is Amazon down right now?
A failure on one device, browser, or page does not establish a general outage. Test several unrelated Amazon functions on another device or network. If the same functions fail across different connections, a wider or regional availability problem becomes more likely.
Why can I open Amazon but not complete checkout?
Amazon browsing and checkout can fail independently. If product pages load but checkout, payment, or order submission does not, the problem may be limited to that workflow or account transaction. Avoid submitting the order repeatedly until you can confirm its status.
Why does Amazon work on mobile data but not Wi-Fi?
That result usually points to the Wi-Fi network, router, DNS resolution, or network path rather than a complete Amazon outage. Restart the router, compare another connection, and contact the network provider if the issue continues.
Why does Amazon work in a private browser window?
Private browsing uses different stored site data and may bypass some browser extensions. This makes stale cookies, cached data, or an extension conflict more likely. Clear Amazon site data or disable extensions one at a time in the regular browser.
Is an AWS outage the same as an Amazon outage?
No. Amazon Web Services and the consumer Amazon shopping service are separate services. Investigate AWS console, API, and cloud-resource problems separately from Amazon retail shopping problems.
What should I do if Amazon shows a 503 or 504 error?
Record the error, wait briefly, and retry without repeatedly submitting forms or payments. Test another Amazon page and, if possible, another network. A 503 or 504 may be temporary or limited to a particular request path.
This is a live connectivity check from our server, not an official statement from Amazon. A down result may also reflect a regional or partial outage.
LIVE CHECKS
