Is Lyft down?
Checks passingchecked 15 minutes ago
Our checks of Lyft pass from all 2 regions we check.
As of Oct 23, 2026, 1:28 AM UTC, RealUptime's checks of Lyft passed in all 2 regions that returned a reading.
Our checks of Lyft did not fail from two or more distant regions in the 64 days we have checked it (since Aug 20, 2026). This does not show Lyft works for users.
This reading is from our two US regions.
Email me when our checks of Lyft fail from two or more distant regions
Lyft operates in the United States and Canada, so we check it from our US regions only.
Lyft publishes no status feed we can read, so the only reading here is our check reading on the left.
Lyft response time, by region
Check your own site while you wait on Lyft
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 Lyft. It cannot diagnose Lyft's own systems.
What we measured, function by function
Lyft answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.
- WebUS-East: Checks passingUS-West: Checks passingEurope: Not monitored from this regionAsia-Pacific: Not monitored from this regionUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
- APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Not monitored from this regionAsia-Pacific: Not monitored from this regionUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
What our checks show, and what people reported
- North AmericaNot monitored from this regionUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 675msstatus code: 422checked: Oct 23, 2026, 1:21 AM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Lyft normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestChecks passinglatency: 876msstatus code: 422checked: Oct 23, 2026, 1:28 AM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Lyft normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralNot monitored from this regionLyft is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- CanadaNot monitored from this regionLyft is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- South AmericaNot monitored from this regionLyft is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- EuropeNot monitored from this regionEurope, UK
- EuropeNot monitored from this regionLyft is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- UKNot monitored from this regionLyft is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- Asia PacificNot monitored from this regionAsia-Pacific, Southeast Asia, Australia
- Asia-PacificNot monitored from this regionLyft is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- Southeast AsiaNot monitored from this regionLyft is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
- AustraliaNot monitored from this regionLyft is not monitored from this region.0 people in the last 5 minutesNot enough reports to say
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using Lyft, 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 started counting reports for Lyft on September 11, 2026.
Recent probe events
No probe events on record yet for Lyft.
check entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring Lyft since August 20, 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 Lyft covering any window you pick, with our check readings and Lyft's own claim at the time, side by side.
Full check history for Lyft: 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/lyft)<a href="https://realuptime.io/outages/lyft"><img src="https://realuptime.io/outages/lyft/badge.svg?days=30" alt="Lyft uptime by RealUptime's checks" height="20"></a>The badge shows the share of our checks that passed over the last 30 days. 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 Lyft down?", https://realuptime.io/outages/lyft. 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.
How our checks compare with Lyft's stated SLA
At or above your target
Our checks of Lyft 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 Lyft'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 our request with the error they give a request that carries no account or valid input. It does not show that sign-in works or that any real request succeeds.
Host checked: api.lyft.com