Uber status

How we check Uber

We watch uber.com/robots.txt from all five of our probe regions, every 2 minutes. A region that sees a failure does not make this page say "down" on its own: a second region has to agree first, the same confirmation rule every YoPingMe monitor uses.

Uber's rider and driver experience runs through native mobile apps rather than a single public web endpoint, and the mobile API is authenticated and not something an anonymous monitor can probe honestly. We watch Uber's own web host instead and pin the response an anonymous request receives, a reachability signal for uber.com's infrastructure rather than a claim about the app experience specifically.

What is Uber?

Uber operates as a marketplace connecting riders and drivers, and diners and couriers, primarily through native mobile apps rather than a single website most people interact with directly. That mobile-first, marketplace structure shapes what "Uber is down" actually tends to mean in practice, and it is worth separating from a platform-wide reading before drawing conclusions from one bad ride request.

Driver and delivery availability is the most common source of trouble mistaken for an outage. The number of nearby drivers or couriers varies constantly with location, time of day, weather, and local events, and a period with genuinely no supply nearby produces the same experience as an outage from a rider's perspective: no ride found, no estimate shown. This is the market working as designed rather than a platform failing, and it resolves as supply returns rather than as any incident clearing.

The apps poll for updates rather than maintaining a permanently open connection to the server, which means a stale-looking screen, a ride status that has not updated in a while, is often a local connectivity hiccup rather than a platform problem. The next successful poll usually resolves it, and force-closing and reopening the app is a faster fix than waiting on any external reading of Uber's health, including this one.

Payment failures at checkout are a frequent source of confusion between account-specific and platform-wide problems. A card that was declined, a payment method that expired, or a temporary hold placed by a bank will block a request with an error that reads like something is broken, while Uber's payment processing infrastructure is working exactly as intended for every other rider and diner. Updating the payment method on file is the fix, and it has nothing to do with platform availability.

Because Uber's rides and delivery products share underlying infrastructure but ship as separate mobile apps, a problem isolated to one app's client-side code can affect that experience specifically without touching the shared backend this page watches, and the reverse is also possible. Treating "the app is broken" and "the platform is down" as separate questions is the more accurate way to reason about what is actually happening during a reported problem.

Frequently asked questions

Is Uber down right now?

Check the board above; it reflects our own probes against Uber's web infrastructure from all five of our regions, refreshed every couple of minutes. The rider and driver apps are separate mobile experiences, so this is a reachability signal for Uber's infrastructure rather than a direct reading of the app.

The app shows no drivers available but this page says Uber is up. What does that mean?

That is a supply and demand condition, not a platform outage. Driver availability varies constantly by location, time of day, and local events, and a city having genuinely no nearby drivers at a given moment is a real market condition Uber's systems are reporting accurately, not a failure of the app to reach the platform.

My ride or order is stuck showing a stale status. Is Uber down?

Usually not. The app polls for updates rather than holding a permanently open connection, so a brief network interruption on your device can leave the screen showing an older status until the next successful refresh. Force-closing and reopening the app is often faster than waiting, and it says nothing about Uber's platform health.

Does a payment failure at checkout mean Uber's systems are down?

Rarely. A declined card, an expired payment method on file, or a temporary hold from your bank will block a ride or order request with an error that looks like a platform problem and is a payment-processing detail specific to your account. Updating the payment method on file resolves most of these without anything on Uber's side being unavailable.

Is Uber Eats covered by this page too?

This page watches Uber's shared web infrastructure, which underlies both the rides and Eats products, but does not separately verify each app's mobile-specific experience. A problem isolated to one app's client rather than the shared backend would not necessarily show up here.