Skip to content

Outage tracker / Uber

Is Uber down?

I'm having a problem

Vendor reports no incidentWhat Uber reports

Uber reports no incident on its status page.

As of the last successful poll, 2026-10-14 04:30 UTC.

Uber's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 1 minute ago

Our checks of Uber pass from all 10 regions we check.

As of Oct 14, 2026, 4:37 AM UTC, RealUptime's checks of Uber passed in all 10 regions that returned a reading.

Front-door and live API checks

Email me when Uber reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Uber's own statement from its status page, with our regional reading beside it.

our check readinglive · checked Oct 14, 2026, 4:37 AM UTC
US-East66 msChecks passing
US-West170 msChecks passing
Europe190 msChecks passing
Asia-Pacific1024 msChecks passing
US-Central225 msChecks passing
Canada206 msChecks passing
UK218 msChecks passing
Southeast Asia565 msChecks passing
Australia1104 msChecks passing
South America207 msChecks passing
their status pagetheir claim, not our reading

Uber reports: All systems operational (“All Systems Operational”)

from Uber's own status page, checked Oct 14, 2026, 4:19 AM UTC
Uber's own status page shows no incident, and our checks of Uber pass right now.

Uber's own component breakdown, as they publish it

  • API (example)Operational
  • Management Portal (example)Operational

These are Uber's components, named and scored by Uber. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Uber's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Uber response time, by region

US-East
254msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 360ms2026-09-16 UTC: p95 412ms2026-09-17 UTC: p95 311ms2026-09-18 UTC: p95 354ms2026-09-19 UTC: p95 432ms2026-09-20 UTC: p95 392ms2026-09-21 UTC: p95 363ms2026-09-22 UTC: p95 469ms2026-09-23 UTC: p95 661ms2026-09-24 UTC: p95 561ms2026-09-25 UTC: p95 328ms2026-09-26 UTC: p95 361ms2026-09-27 UTC: p95 318ms2026-09-28 UTC: p95 344ms2026-09-29 UTC: p95 472ms2026-09-30 UTC: p95 405ms2026-10-01 UTC: p95 396ms2026-10-02 UTC: p95 363ms2026-10-03 UTC: p95 333ms2026-10-04 UTC: p95 405ms2026-10-05 UTC: p95 436ms2026-10-06 UTC: p95 404ms2026-10-07 UTC: p95 371ms2026-10-08 UTC: p95 442ms2026-10-09 UTC: p95 425ms2026-10-10 UTC: p95 390ms2026-10-11 UTC: p95 375ms2026-10-12 UTC: p95 374ms2026-10-13 UTC: p95 402ms2026-10-14 UTC: p95 254ms
Sep 15Sep 29Oct 14
US-West
287msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 355ms2026-09-16 UTC: p95 307ms2026-09-17 UTC: p95 296ms2026-09-18 UTC: p95 420ms2026-09-19 UTC: p95 590ms2026-09-20 UTC: p95 554ms2026-09-21 UTC: p95 478ms2026-09-22 UTC: p95 580ms2026-09-23 UTC: p95 584ms2026-09-24 UTC: p95 590ms2026-09-25 UTC: p95 565ms2026-09-26 UTC: p95 632ms2026-09-27 UTC: p95 469ms2026-09-28 UTC: p95 416ms2026-09-29 UTC: p95 314ms2026-09-30 UTC: p95 295ms2026-10-01 UTC: p95 389ms2026-10-02 UTC: p95 486ms2026-10-03 UTC: p95 433ms2026-10-04 UTC: p95 314ms2026-10-05 UTC: p95 302ms2026-10-06 UTC: p95 351ms2026-10-07 UTC: p95 291ms2026-10-08 UTC: p95 324ms2026-10-09 UTC: p95 379ms2026-10-10 UTC: p95 322ms2026-10-11 UTC: p95 348ms2026-10-12 UTC: p95 379ms2026-10-13 UTC: p95 314ms2026-10-14 UTC: p95 287ms
Sep 15Sep 29Oct 14
Europe
286msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 358ms2026-09-16 UTC: p95 474ms2026-09-17 UTC: p95 514ms2026-09-18 UTC: p95 551ms2026-09-19 UTC: p95 727ms2026-09-20 UTC: p95 564ms2026-09-21 UTC: p95 696ms2026-09-22 UTC: p95 679ms2026-09-23 UTC: p95 608ms2026-09-24 UTC: p95 848ms2026-09-25 UTC: p95 695ms2026-09-26 UTC: p95 538ms2026-09-27 UTC: p95 509ms2026-09-28 UTC: p95 542ms2026-09-29 UTC: p95 478ms2026-09-30 UTC: p95 284ms2026-10-01 UTC: p95 404ms2026-10-02 UTC: p95 338ms2026-10-03 UTC: p95 316ms2026-10-04 UTC: p95 309ms2026-10-05 UTC: p95 318ms2026-10-06 UTC: p95 349ms2026-10-07 UTC: p95 280ms2026-10-08 UTC: p95 359ms2026-10-09 UTC: p95 283ms2026-10-10 UTC: p95 302ms2026-10-11 UTC: p95 358ms2026-10-12 UTC: p95 292ms2026-10-13 UTC: p95 258ms2026-10-14 UTC: p95 286ms
Sep 15Sep 29Oct 14
Asia-Pacific
828msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 614ms2026-09-16 UTC: p95 846ms2026-09-17 UTC: p95 663ms2026-09-18 UTC: p95 702ms2026-09-19 UTC: p95 667ms2026-09-20 UTC: p95 644ms2026-09-21 UTC: p95 700ms2026-09-22 UTC: p95 689ms2026-09-23 UTC: p95 702ms2026-09-24 UTC: p95 694ms2026-09-25 UTC: p95 644ms2026-09-26 UTC: p95 631ms2026-09-27 UTC: p95 694ms2026-09-28 UTC: p95 628ms2026-09-29 UTC: p95 653ms2026-09-30 UTC: p95 760ms2026-10-01 UTC: p95 849ms2026-10-02 UTC: p95 703ms2026-10-03 UTC: p95 677ms2026-10-04 UTC: p95 609ms2026-10-05 UTC: p95 541ms2026-10-06 UTC: p95 562ms2026-10-07 UTC: p95 577ms2026-10-08 UTC: p95 607ms2026-10-09 UTC: p95 597ms2026-10-10 UTC: p95 616ms2026-10-11 UTC: p95 717ms2026-10-12 UTC: p95 845ms2026-10-13 UTC: p95 896ms2026-10-14 UTC: p95 828ms
Sep 15Sep 29Oct 14
US-Central
534msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 415ms2026-09-16 UTC: p95 377ms2026-09-17 UTC: p95 286ms2026-09-18 UTC: p95 324ms2026-09-19 UTC: p95 454ms2026-09-20 UTC: p95 450ms2026-09-21 UTC: p95 492ms2026-09-22 UTC: p95 426ms2026-09-23 UTC: p95 452ms2026-09-24 UTC: p95 449ms2026-09-25 UTC: p95 424ms2026-09-26 UTC: p95 460ms2026-09-27 UTC: p95 289ms2026-09-28 UTC: p95 376ms2026-09-29 UTC: p95 395ms2026-09-30 UTC: p95 437ms2026-10-01 UTC: p95 466ms2026-10-02 UTC: p95 393ms2026-10-03 UTC: p95 243ms2026-10-04 UTC: p95 426ms2026-10-05 UTC: p95 417ms2026-10-06 UTC: p95 439ms2026-10-07 UTC: p95 402ms2026-10-08 UTC: p95 455ms2026-10-09 UTC: p95 468ms2026-10-10 UTC: p95 492ms2026-10-11 UTC: p95 488ms2026-10-12 UTC: p95 402ms2026-10-13 UTC: p95 592ms2026-10-14 UTC: p95 534ms
Sep 15Sep 29Oct 14
Canada
357msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 478ms2026-09-16 UTC: p95 402ms2026-09-17 UTC: p95 382ms2026-09-18 UTC: p95 380ms2026-09-19 UTC: p95 542ms2026-09-20 UTC: p95 457ms2026-09-21 UTC: p95 505ms2026-09-22 UTC: p95 518ms2026-09-23 UTC: p95 231ms2026-09-24 UTC: p95 511ms2026-09-25 UTC: p95 419ms2026-09-26 UTC: p95 502ms2026-09-27 UTC: p95 511ms2026-09-28 UTC: p95 559ms2026-09-29 UTC: p95 520ms2026-09-30 UTC: p95 584ms2026-10-01 UTC: p95 567ms2026-10-02 UTC: p95 402ms2026-10-03 UTC: p95 530ms2026-10-04 UTC: p95 498ms2026-10-05 UTC: p95 299ms2026-10-06 UTC: p95 338ms2026-10-07 UTC: p95 386ms2026-10-08 UTC: p95 271ms2026-10-09 UTC: p95 474ms2026-10-10 UTC: p95 370ms2026-10-11 UTC: p95 294ms2026-10-12 UTC: p95 418ms2026-10-13 UTC: p95 356ms2026-10-14 UTC: p95 357ms
Sep 15Sep 29Oct 14
UK
258msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 223ms2026-09-16 UTC: p95 260ms2026-09-17 UTC: p95 315ms2026-09-18 UTC: p95 311ms2026-09-19 UTC: p95 531ms2026-09-20 UTC: p95 330ms2026-09-21 UTC: p95 393ms2026-09-22 UTC: p95 411ms2026-09-23 UTC: p95 394ms2026-09-24 UTC: p95 315ms2026-09-25 UTC: p95 434ms2026-09-26 UTC: p95 432ms2026-09-27 UTC: p95 335ms2026-09-28 UTC: p95 367ms2026-09-29 UTC: p95 306ms2026-09-30 UTC: p95 463ms2026-10-01 UTC: p95 559ms2026-10-02 UTC: p95 429ms2026-10-03 UTC: p95 359ms2026-10-04 UTC: p95 264ms2026-10-05 UTC: p95 310ms2026-10-06 UTC: p95 376ms2026-10-07 UTC: p95 362ms2026-10-08 UTC: p95 304ms2026-10-09 UTC: p95 325ms2026-10-10 UTC: p95 318ms2026-10-11 UTC: p95 278ms2026-10-12 UTC: p95 277ms2026-10-13 UTC: p95 270ms2026-10-14 UTC: p95 258ms
Sep 15Sep 29Oct 14
Southeast Asia
826msp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 863ms2026-09-17 UTC: p95 824ms2026-09-18 UTC: p95 846ms2026-09-19 UTC: p95 949ms2026-09-20 UTC: p95 1.0s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 972ms2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 991ms2026-10-05 UTC: p95 913ms2026-10-06 UTC: p95 914ms2026-10-07 UTC: p95 921ms2026-10-08 UTC: p95 872ms2026-10-09 UTC: p95 919ms2026-10-10 UTC: p95 902ms2026-10-11 UTC: p95 829ms2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 807ms2026-10-14 UTC: p95 826ms
Sep 15Sep 29Oct 14
Australia
1.1sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 853ms2026-09-16 UTC: p95 824ms2026-09-17 UTC: p95 835ms2026-09-18 UTC: p95 661ms2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 894ms2026-09-21 UTC: p95 953ms2026-09-22 UTC: p95 927ms2026-09-23 UTC: p95 918ms2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.5s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.0s2026-09-28 UTC: p95 901ms2026-09-29 UTC: p95 831ms2026-09-30 UTC: p95 957ms2026-10-01 UTC: p95 888ms2026-10-02 UTC: p95 1.0s2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.0s2026-10-06 UTC: p95 1.0s2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 906ms2026-10-09 UTC: p95 982ms2026-10-10 UTC: p95 931ms2026-10-11 UTC: p95 748ms2026-10-12 UTC: p95 880ms2026-10-13 UTC: p95 999ms2026-10-14 UTC: p95 1.1s
Sep 15Sep 29Oct 14
South America
851msp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 816ms2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 2.4s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 954ms2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 930ms2026-09-24 UTC: p95 792ms2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 948ms2026-09-27 UTC: p95 878ms2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 928ms2026-09-30 UTC: p95 740ms2026-10-01 UTC: p95 760ms2026-10-02 UTC: p95 1.0s2026-10-03 UTC: p95 992ms2026-10-04 UTC: p95 889ms2026-10-05 UTC: p95 810ms2026-10-06 UTC: p95 924ms2026-10-07 UTC: p95 766ms2026-10-08 UTC: p95 903ms2026-10-09 UTC: p95 786ms2026-10-10 UTC: p95 829ms2026-10-11 UTC: p95 944ms2026-10-12 UTC: p95 841ms2026-10-13 UTC: p95 999ms2026-10-14 UTC: p95 851ms
Sep 15Sep 29Oct 14

Check your own site while you wait on Uber

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Uber. It cannot diagnose Uber's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 66msstatus code: 401checked: Oct 14, 2026, 4:34 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Uber normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 170msstatus code: 401checked: Oct 14, 2026, 4:37 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Uber normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 225msstatus code: 401checked: Oct 14, 2026, 4:19 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Uber normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 206msstatus code: 401checked: Oct 14, 2026, 4:33 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Uber normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 207msstatus code: 401checked: Oct 14, 2026, 4:32 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Uber normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 190msstatus code: 401checked: Oct 14, 2026, 4:28 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Uber normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 218msstatus code: 401checked: Oct 14, 2026, 4:33 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Uber normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1024msstatus code: 401checked: Oct 14, 2026, 4:32 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Uber normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 565msstatus code: 401checked: Oct 14, 2026, 4:31 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Uber normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1104msstatus code: 401checked: Oct 14, 2026, 4:35 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Uber normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Uber, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Uber yet, which is not evidence that nothing is wrong.

Recent probe events

No me pagó el efectivo correcto, 1h 30mdeclared on their status page2020-10-28
This is an example incident, 10mdeclared on their status page2020-10-27
Pago, 1mdeclared on their status page2020-10-25

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Uber since August 8, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Uber covering any window you pick, with our check readings and Uber's own claim at the time, side by side.

Full check history for Uber: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

Uber uptime by RealUptime's checksLive, from this page's own readings.
[![Uber uptime by RealUptime's checks](https://realuptime.io/outages/uber/badge.svg?days=30)](https://realuptime.io/outages/uber)
<a href="https://realuptime.io/outages/uber"><img src="https://realuptime.io/outages/uber/badge.svg?days=30" alt="Uber uptime by RealUptime's checks"></a>

The badge shows the share of our checks that passed over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Uber down?", https://realuptime.io/outages/uber. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional
https://api.uber.com/v1.2/products
secondary
https://uber.statuspage.io/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.uber.com

RealUptime is not affiliated with Uber; the name identifies what we checked, and nothing here speaks for Uber's own team. We send a single web request to Uber from 10 regions on our own schedule and time the response. We do not see inside Uber's systems, do not use an account or real transaction, and are not the same signal Uber's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Uber is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.