Is Uber down?
Checks passingchecked moments ago
Our checks of Uber pass from all 10 regions we check.
As of Nov 5, 2026, 3:23 PM UTC, RealUptime's checks of Uber passed in all 10 regions that returned a reading.
Uber's last published incident: "No me pagó el efectivo correcto", Oct 28, 2020, 1h 30m. their claim, not our reading
Our checks of Uber did not fail from two or more distant regions in the 89 days we have checked it (since Aug 8, 2026). This does not show Uber works for users.
Email me when our checks of Uber fail from two or more distant regions
Uber reports: All systems operational (“All Systems Operational”)
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
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 our checks show, and what people reported
- North AmericaChecks passingUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 1392msstatus code: 401checked: Nov 5, 2026, 3:20 PM UTC0 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-WestChecks passinglatency: 1314msstatus code: 401checked: Nov 5, 2026, 3:22 PM UTC0 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-CentralChecks passinglatency: 617msstatus code: 401checked: Nov 5, 2026, 3:03 PM UTC0 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.
- CanadaChecks passinglatency: 871msstatus code: 401checked: Nov 5, 2026, 3:14 PM UTC0 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 AmericaChecks passinglatency: 1976msstatus code: 401checked: Nov 5, 2026, 3:18 PM UTC0 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.
- EuropeChecks passingEurope, UK
- EuropeChecks passinglatency: 1011msstatus code: 401checked: Nov 5, 2026, 3:23 PM UTC0 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.
- UKChecks passinglatency: 789msstatus code: 401checked: Nov 5, 2026, 3:18 PM UTC0 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 PacificChecks passingAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 1600msstatus code: 401checked: Nov 5, 2026, 3:23 PM UTC0 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 AsiaChecks passinglatency: 1771msstatus code: 401checked: Nov 5, 2026, 3:03 PM UTC0 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.
- AustraliaChecks passinglatency: 1665msstatus code: 401checked: Nov 5, 2026, 3:08 PM UTC0 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
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
Live, from this page's own readings.[](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" height="20"></a>Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.
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.
How our checks compare with Uber's stated SLA
At or above your target
Our checks of Uber failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.
Our checks show no gap in this period. That does not rule out one you saw.
These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, 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
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