Is Lyft down right now?

Operational. We reached Lyft from all 2 regions we check.

How does RealUptime check if Lyft is down?

RealUptime checks Lyft with scheduled HTTP probes against its public, unauthenticated functional endpoints, run from named regions on a fixed cadence, plus an extra confirmation probe whenever a signal suggests a problem. This verifies that the functional endpoints we probe actually answer, not that every feature of Lyft works end to end.

What does "degraded" mean for Lyft?

Degraded means Lyft answered our probe but at several times its own seven-day median response time. Degraded only ever applies to a reading that answered: a surface that is down, or one that refused our probe, is reported as down or awaiting data instead, never softened into "degraded".

What is Lyft's current response time?

RealUptime's most recent measured response time for Lyft, by region: US-East: 337 ms, US-West: 466 ms. This is the latest single probe reading per region, not an average.

When did RealUptime last check Lyft?

RealUptime's probes last checked Lyft at 2026-09-03T00:49:09.011Z.

Is Lyft down?

Short linkrlup.io/down/lyft

I'm having a problem

Operationalchecked 40 minutes ago

We reached Lyft from all 2 regions we check.

Functional endpoints verified

No outage recorded in the 14 days we have measured Lyft (since Aug 20, 2026).

our independent probeslive · checked Sep 3, 2026, 12:49 AM UTC

US-East337 msOperational

US-West466 msOperational

Lyft operates in the United States and Canada, so we check it from our US regions only.

their status pagetheir claim, not our reading

Lyft publishes no status feed we can read, so the only independent reading here is ours on the left.

Lyft response time, by region

US-East

389msp95 · latest

1s500ms0ms

Aug 5Aug 19Sep 3

US-West

461msp95 · latest

1s500ms0ms

Aug 5Aug 19Sep 3

Is it Lyft, 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 Lyft -- it cannot diagnose Lyft's own systems.

What we measured, and what people reported

US-East
Operationallatency: 337msstatus code: 422checked: Sep 3, 2026, 12:42 AM UTC
0 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-West
Operationallatency: 466msstatus code: 422checked: Sep 3, 2026, 12:49 AM UTC
0 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.
Europe
Not monitored from this regionLyft is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
Asia-Pacific
Not monitored from this regionLyft is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
US-Central
Not monitored from this regionLyft is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
Canada
Not monitored from this regionLyft is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
UK
Not monitored from this regionLyft is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
Southeast Asia
Not monitored from this regionLyft is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
Australia
Not monitored from this regionLyft is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
South America
Not 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 have not received any reports for Lyft yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for Lyft.

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

Full availability history for Lyft: 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

Put this badge in your README

Live, from this page's own readings.

[![Lyft uptime measured by RealUptime](https://realuptime.io/outages/lyft/badge.svg?days=30)](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 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 Lyft's SLA implies, from our measurement

Window

What you pay per month

Uptime target in your contract

Include outages only one region saw (none)

At or above your target

We measured none of downtime for Lyft over the 337h 29m since we started watching it on 2026-08-20, which is 100% uptime by our reading. A 99.9% target allows 20 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 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

primaryfunctional: live API

https://api.lyft.com/v1/cost

secondary

https://www.lyft.com/

RealUptime is not affiliated with Lyft; the name identifies what we measured, and nothing here speaks for Lyft's own team. We send a single web request to Lyft from 2 regions on our own schedule and time the response. We do not see inside Lyft's systems, do not use an account or real transaction, and are not the same signal Lyft's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Lyft 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. Lyft operates in the United States and Canada, so we check it from our US regions only. Read the full methodology.

Related services

Airbnb Amazon Apple iCloud Best Buy Booking.com