Skip to content

Outage tracker / Uber

Is Uber down?

I'm having a problem

Operationalchecked moments ago

We reached Uber from all 10 regions we check.

As of Sep 23, 2026, 9:08 AM UTC, Uber answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured Uber (since Aug 8, 2026).

our independent probeslive · checked Sep 23, 2026, 9:08 AM UTC
US-East216 msOperational
US-West325 msOperational
Europe198 msOperational
Asia-Pacific430 msOperational
US-Central292 msOperational
Canada123 msOperational
UK213 msOperational
Southeast Asia825 msOperational
Australia367 msOperational
South America165 msOperational
their status pagetheir claim, not our reading

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

from Uber's own status page, checked Sep 23, 2026, 8:51 AM UTC
Our probes and Uber's own status page agree: both show Uber as reachable 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
650msp95 · 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-08-25 UTC: p95 851ms2026-08-26 UTC: p95 888ms2026-08-27 UTC: p95 814ms2026-08-28 UTC: p95 572ms2026-08-29 UTC: p95 314ms2026-08-30 UTC: p95 336ms2026-08-31 UTC: p95 363ms2026-09-01 UTC: p95 455ms2026-09-02 UTC: p95 363ms2026-09-03 UTC: p95 388ms2026-09-04 UTC: p95 367ms2026-09-05 UTC: p95 392ms2026-09-06 UTC: p95 319ms2026-09-07 UTC: p95 309ms2026-09-08 UTC: p95 303ms2026-09-09 UTC: p95 295ms2026-09-10 UTC: p95 277ms2026-09-11 UTC: p95 295ms2026-09-12 UTC: p95 300ms2026-09-13 UTC: p95 297ms2026-09-14 UTC: p95 331ms2026-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 650ms
Aug 25Sep 8Sep 23
US-West
600msp95 · 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-08-25 UTC: p95 230ms2026-08-26 UTC: p95 414ms2026-08-27 UTC: p95 617ms2026-08-28 UTC: p95 456ms2026-08-29 UTC: p95 711ms2026-08-30 UTC: p95 508ms2026-08-31 UTC: p95 501ms2026-09-01 UTC: p95 349ms2026-09-02 UTC: p95 450ms2026-09-03 UTC: p95 411ms2026-09-04 UTC: p95 398ms2026-09-05 UTC: p95 414ms2026-09-06 UTC: p95 501ms2026-09-07 UTC: p95 513ms2026-09-08 UTC: p95 373ms2026-09-09 UTC: p95 265ms2026-09-10 UTC: p95 238ms2026-09-11 UTC: p95 318ms2026-09-12 UTC: p95 276ms2026-09-13 UTC: p95 259ms2026-09-14 UTC: p95 248ms2026-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 600ms
Aug 25Sep 8Sep 23
Europe
553msp95 · 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-08-25 UTC: p95 465ms2026-08-26 UTC: p95 371ms2026-08-27 UTC: p95 526ms2026-08-28 UTC: p95 419ms2026-08-29 UTC: p95 369ms2026-08-30 UTC: p95 399ms2026-08-31 UTC: p95 449ms2026-09-01 UTC: p95 491ms2026-09-02 UTC: p95 497ms2026-09-03 UTC: p95 409ms2026-09-04 UTC: p95 648ms2026-09-05 UTC: p95 340ms2026-09-06 UTC: p95 370ms2026-09-07 UTC: p95 306ms2026-09-08 UTC: p95 316ms2026-09-09 UTC: p95 283ms2026-09-10 UTC: p95 439ms2026-09-11 UTC: p95 322ms2026-09-12 UTC: p95 340ms2026-09-13 UTC: p95 287ms2026-09-14 UTC: p95 316ms2026-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 553ms
Aug 25Sep 8Sep 23
Asia-Pacific
650msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-25 UTC: p95 975ms2026-08-26 UTC: p95 879ms2026-08-27 UTC: p95 996ms2026-08-28 UTC: p95 894ms2026-08-29 UTC: p95 880ms2026-08-30 UTC: p95 907ms2026-08-31 UTC: p95 735ms2026-09-01 UTC: p95 864ms2026-09-02 UTC: p95 1.2s2026-09-03 UTC: p95 1.2s2026-09-04 UTC: p95 836ms2026-09-05 UTC: p95 830ms2026-09-06 UTC: p95 593ms2026-09-07 UTC: p95 633ms2026-09-08 UTC: p95 692ms2026-09-09 UTC: p95 902ms2026-09-10 UTC: p95 694ms2026-09-11 UTC: p95 563ms2026-09-12 UTC: p95 581ms2026-09-13 UTC: p95 547ms2026-09-14 UTC: p95 643ms2026-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 650ms
Aug 25Sep 8Sep 23
US-Central
462msp95 · 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-03 UTC: p95 457ms2026-09-04 UTC: p95 553ms2026-09-05 UTC: p95 311ms2026-09-06 UTC: p95 304ms2026-09-07 UTC: p95 396ms2026-09-08 UTC: p95 363ms2026-09-09 UTC: p95 450ms2026-09-10 UTC: p95 390ms2026-09-11 UTC: p95 425ms2026-09-12 UTC: p95 342ms2026-09-13 UTC: p95 407ms2026-09-14 UTC: p95 377ms2026-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 462ms
Aug 25Sep 8Sep 23
Canada
144msp95 · 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-03 UTC: p95 474ms2026-09-04 UTC: p95 815ms2026-09-05 UTC: p95 823ms2026-09-06 UTC: p95 614ms2026-09-07 UTC: p95 402ms2026-09-08 UTC: p95 353ms2026-09-09 UTC: p95 520ms2026-09-10 UTC: p95 612ms2026-09-11 UTC: p95 603ms2026-09-12 UTC: p95 433ms2026-09-13 UTC: p95 460ms2026-09-14 UTC: p95 527ms2026-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 144ms
Aug 25Sep 8Sep 23
UK
283msp95 · 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-03 UTC: p95 327ms2026-09-04 UTC: p95 385ms2026-09-05 UTC: p95 350ms2026-09-06 UTC: p95 349ms2026-09-07 UTC: p95 256ms2026-09-08 UTC: p95 220ms2026-09-09 UTC: p95 273ms2026-09-10 UTC: p95 309ms2026-09-11 UTC: p95 222ms2026-09-12 UTC: p95 223ms2026-09-13 UTC: p95 261ms2026-09-14 UTC: p95 244ms2026-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 283ms
Aug 25Sep 8Sep 23
Southeast Asia
1.2sp95 · 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-03 UTC: p95 1.3s2026-09-04 UTC: p95 984ms2026-09-05 UTC: p95 992ms2026-09-06 UTC: p95 964ms2026-09-07 UTC: p95 902ms2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 895ms2026-09-11 UTC: p95 973ms2026-09-12 UTC: p95 927ms2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.4s2026-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.2s
Aug 25Sep 8Sep 23
Australia
886msp95 · 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-03 UTC: p95 1.3s2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 1.1s2026-09-06 UTC: p95 962ms2026-09-07 UTC: p95 940ms2026-09-08 UTC: p95 802ms2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 972ms2026-09-12 UTC: p95 885ms2026-09-13 UTC: p95 1.0s2026-09-14 UTC: p95 1.1s2026-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 886ms
Aug 25Sep 8Sep 23
South America
866msp95 · 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-03 UTC: p95 966ms2026-09-04 UTC: p95 913ms2026-09-05 UTC: p95 996ms2026-09-06 UTC: p95 1.1s2026-09-07 UTC: p95 868ms2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 875ms2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 780ms2026-09-12 UTC: p95 752ms2026-09-13 UTC: p95 799ms2026-09-14 UTC: p95 633ms2026-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 866ms
Aug 25Sep 8Sep 23

Is it Uber, or is it you?

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 we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 216msstatus code: 401checked: Sep 23, 2026, 9:01 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
      Operationallatency: 325msstatus code: 401checked: Sep 23, 2026, 9:05 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
      Operationallatency: 292msstatus code: 401checked: Sep 23, 2026, 8:50 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
      Operationallatency: 123msstatus code: 401checked: Sep 23, 2026, 8:50 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
    Operationallatency: 165msstatus code: 401checked: Sep 23, 2026, 9:07 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 198msstatus code: 401checked: Sep 23, 2026, 9:08 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
      Operationallatency: 213msstatus code: 401checked: Sep 23, 2026, 9:06 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 430msstatus code: 401checked: Sep 23, 2026, 9:08 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
      Operationallatency: 825msstatus code: 401checked: Sep 23, 2026, 9:05 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
      Operationallatency: 367msstatus code: 401checked: Sep 23, 2026, 9:00 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 outages

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

measured 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 measurements and Uber's own claim at the time, side by side.

Full availability history for Uber: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Uber, and again when they can reach it again. That is our own measurement from ten regions, not Uber's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Uber uptime measured by RealUptimeLive, from this page's own readings.
[![Uber uptime measured by RealUptime](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 measured by RealUptime"></a>

The badge shows the share of our probes that succeeded 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: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Uber's SLA implies, from our measurement

At or above your target

We measured none of downtime for Uber over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Uber's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://api.uber.com/v1.2/products
secondary
https://uber.statuspage.io/
RealUptime is not affiliated with Uber; the name identifies what we measured, 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 clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.