Amazon Kindle help and reporting
Amazon retail and digital-content support are separate from AWS Health.
Live Domain Check
Run a live reachability check for kindle.amazon.com. Compare the regional responses with the problem you see in Amazon Kindle.
Find Amazon Kindle help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Kindle library access, book downloads and reading on a device differ from Amazon shopping availability.
The checker above requests kindle.amazon.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Amazon Kindle action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse streaming and media 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.
Open Amazon Kindle 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.
Book, Kindle/app/device version, download or sync action, marketplace and error 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 Kindle.
These are troubleshooting comparisons, not claims that Amazon Kindle is currently experiencing a particular incident.
Compare an already downloaded book with a new download and verify the purchasing account/marketplace.
Use Kindle digital-content support and inspect library/purchase state before buying the title again.
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 Kindle seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open kindle.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 Kindle 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 Kindle support.
Run the kindle.amazon.com check and compare its original timestamps and responses with your actual error. Kindle library access, book downloads and reading on a device differ from Amazon shopping availability.
Use the community buttons on this page to share whether the service works for you. For help from Amazon Kindle, use the official help/reporting resource linked above. Amazon retail and digital-content support are separate from AWS Health.
Compare an already downloaded book with a new download and verify the purchasing account/marketplace. Use Kindle digital-content support and inspect library/purchase state before buying the title again.
Book, Kindle/app/device version, download or sync action, marketplace and error time.