Skip to content

Outage tracker / Cabify

Is Cabify down?

I'm having a problem

Checks passingchecked 4 minutes ago

Our checks of Cabify pass from all 4 regions we check.

As of Nov 5, 2026, 5:06 PM UTC, RealUptime's checks of Cabify passed in all 4 regions that returned a reading.

Front-door checks

Our checks of Cabify did not fail from two or more distant regions in the 3 days we have checked it (since Nov 2, 2026). This does not show Cabify works for users.

Email me when our checks of Cabify fail from two or more distant regions

One email when our checks of Cabify fail from two or more distant regions, and one when they pass, after you confirm the address. No account, no card.

This is our own reading from outside. It is not Cabify's official status.

our check readinglive · checked Nov 5, 2026, 5:06 PM UTC
US-East832 msChecks passing
US-West1494 msChecks passing
Europe1450 msChecks passing
Asia-Pacific2119 msChecks passing
their status pagetheir claim, not our reading

Cabify publishes no status feed we can read, so the only reading here is our check reading on the left.

Cabify response time, by region

US-East
1.3sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
US-West
2.0sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.9s2026-11-04 UTC: p95 2.6s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
Europe
1.7sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 1.7s
Oct 7Oct 21Nov 5
Asia-Pacific
2.4sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 2.6s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.7s2026-11-05 UTC: p95 2.4s
Oct 7Oct 21Nov 5

Check your own site while you wait on Cabify

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 Cabify. It cannot diagnose Cabify'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
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 832msstatus code: 200checked: Nov 5, 2026, 4:58 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Cabify normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1494msstatus code: 200checked: Nov 5, 2026, 5:06 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Cabify normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionCabify is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionCabify is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionCabify is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Checks passinglatency: 1450msstatus code: 200checked: Nov 5, 2026, 5:03 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Cabify normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Not monitored from this regionCabify is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2119msstatus code: 200checked: Nov 5, 2026, 5:05 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Cabify normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Not monitored from this regionCabify is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionCabify 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 Cabify, 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 Cabify yet, which is not evidence that nothing is wrong.

Recent probe events

No probe events on record yet for Cabify.

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

We have been measuring Cabify since November 2, 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 Cabify covering any window you pick, with our check readings and Cabify's own claim at the time, side by side.

Full check history for Cabify: 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

Cabify uptime by RealUptime's checksLive, from this page's own readings.
[![Cabify uptime by RealUptime's checks](https://realuptime.io/outages/cabify/badge.svg?days=30)](https://realuptime.io/outages/cabify)
<a href="https://realuptime.io/outages/cabify"><img src="https://realuptime.io/outages/cabify/badge.svg?days=30" alt="Cabify 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 Cabify down?", https://realuptime.io/outages/cabify. The readings change with every check, so give the date you read them.

How our checks compare with Cabify's stated SLA

At or above your target

Our checks of Cabify failed for none over the 74h 56m since we started checking it on 2026-11-02, which is 100% uptime by our checks. A 99.9% target allows 4 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 Cabify'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

primary
https://cabify.com/es

What our check can and cannot see

A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.

Host checked: cabify.com

RealUptime is not affiliated with Cabify; the name identifies what we checked, and nothing here speaks for Cabify's own team. We send a single web request to Cabify from 4 regions on our own schedule and time the response. We do not see inside Cabify's systems, do not use an account or real transaction, and are not the same signal Cabify's own team has access to. Treat this as one external data point, not a verdict. What we check for Cabify is its front door only: a passing check means the endpoints above answered, not that the underlying product or account features work. Cabify operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on November 2, 2026 (3 of 14 days so far, 1265 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.