Uber help and reporting
Select rider or driver and the affected trip rather than filing a generic public report.
Live Domain Check
Run a live reachability check for uber.com. Compare the regional responses with the problem you see in Uber.
Find Uber help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Uber ride requests, driver matching, payments and a current trip are different workflows.
The checker above requests uber.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Uber action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse shopping and payment checks.
Select rider or driver and the affected trip rather than filing a generic public report.
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 Uber 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.
Rider/driver role, trip reference privately, request/payment step, app 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 Uber.
These are troubleshooting comparisons, not claims that Uber is currently experiencing a particular incident.
Check whether a ride request already exists before requesting another and note its current state.
Use help attached to the trip for rider/driver issues and the appropriate role-specific support route.
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 Uber seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open uber.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 Uber 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 Uber support.
Run the uber.com check and compare its original timestamps and responses with your actual error. Uber ride requests, driver matching, payments and a current trip are different workflows.
Use the official help/reporting resource linked above. Select rider or driver and the affected trip rather than filing a generic public report.
Check whether a ride request already exists before requesting another and note its current state. Use help attached to the trip for rider/driver issues and the appropriate role-specific support route.
Rider/driver role, trip reference privately, request/payment step, app and time.