Rakuten help and reporting
Choose the correct Rakuten product and marketplace.
Live Domain Check
Run a live reachability check for rakuten.com. Compare the regional responses with the problem you see in Rakuten.
Find Rakuten 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
Rakuten cashback, a merchant purchase and regional Rakuten services are distinct workflows.
The checker above requests rakuten.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Rakuten action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse shopping and payment checks.
Choose the correct Rakuten product and marketplace.
Open the website in your browser and compare it with the result above.
Open Rakuten 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.
Service/marketplace, merchant, cashback/order reference privately, failed step 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 Rakuten.
These are troubleshooting comparisons, not claims that Rakuten is currently experiencing a particular incident.
Identify the Rakuten service and compare account access with the merchant checkout or cashback record.
Use the correct regional Rakuten Help route; contact the merchant for an order fulfilment issue.
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 Rakuten seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open rakuten.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 Rakuten 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 Rakuten support.
Run the rakuten.com check and compare its original timestamps and responses with your actual error. Rakuten cashback, a merchant purchase and regional Rakuten services are distinct workflows.
Use the community buttons on this page to share whether the service works for you. For help from Rakuten, use the official help/reporting resource linked above. Choose the correct Rakuten product and marketplace.
Identify the Rakuten service and compare account access with the merchant checkout or cashback record. Use the correct regional Rakuten Help route; contact the merchant for an order fulfilment issue.
Service/marketplace, merchant, cashback/order reference privately, failed step and time.