Is Uber down right now?

Yes. HostTracker lets you add any URL - including third-party services you depend on, not just your own website - as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.

No - as of the most recent check, www.uber.com is responding normally to HostTracker's monitoring network, and has been up for 15h 2m. Over the last 24 hours it recorded 98.29% uptime across 1 incident. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

No - as of the most recent check, www.uber.com is responding normally to HostTracker's monitoring network, and has been up for 15h 2m. Over the last 24 hours it recorded 98.29% uptime across 1 incident. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

No - as of the most recent check, www.uber.com is responding normally to HostTracker's monitoring network, and has been up for 15h 2m. Over the last 24 hours it recorded 98.29% uptime across 1 incident. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

No - as of the most recent check, www.uber.com is responding normally to HostTracker's monitoring network, and has been up for 15h 2m. Over the last 24 hours it recorded 98.29% uptime across 1 incident. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

Usually not. No available cars nearby is most often a driver supply problem specific to your area and time, such as a weekend night, a large event, or bad weather pulling demand above what drivers can cover, rather than a technical issue. A genuine outage looks different: the app fails to load at all, or a trip cannot be requested anywhere regardless of driver availability.

Not necessarily either way. Uber Eats and the rider app for trips are separate products that share the same account system but run their own ordering, dispatch and delivery logic. It is entirely possible for ride requests to be having trouble while food delivery works normally, or the reverse, so checking the specific app you are using is more useful than assuming a problem in one affects the other.

Almost certainly not a glitch. Uber's pricing rises with surge pricing when demand for rides outstrips the number of available drivers in an area, which is a normal and intentional part of how the system balances supply, not a technical error. It is most common during weekend nights, bad weather, and large events. The fare is shown before you confirm a trip specifically so this is not a surprise after booking.

It can be, but it is also worth ruling out simpler causes first: being outside an area with rider demand at that moment, a connectivity issue, or an app update being needed. A genuine driver-app outage typically affects many drivers in an area at once and is reported widely rather than being isolated to one phone. If the rider-facing app is working normally for trip requests elsewhere, the problem is more likely local to your app or connection than a platform-wide failure.