Is Gett down right now?

Checking…

Verifying live status…

Our latest checks found Gett responding normally. Live verification is running now.

Live latency
···
Reports · 5 min
···
Reports · 24 h
···
Verification tier
···
What's not working with Gett?

Your report feeds the live outage-velocity detector. One click per 30 s.

Live latency (probe round-trip, ms)

User reports, last 24 hours

Outage history

last 30 days

Recent outages and issues we recorded for Gett, based on our own checks. An episode opens on the second check that finds a problem, since a single adverse reading is not reported, and closes when a check finds the service normal again.

60 days agoToday

No problemsProblemsOutageNot monitored

···Observed uptime, 7 days
···Observed uptime, 30 days
···Episodes, last 30 days

    Comments

    Comments are hosted and moderated via Disqus. Spam is filtered automatically, readers can flag anything, and the thread loads only when you scroll to it so the rest of the page stays fast.

    Jump to comments

    How we check Gett

    No evidence of problems with Gett. Our last recorded check found it behaving normally. That does not rule out a fault affecting only some users or regions.

    Every check runs a four-tier cascade and stops at the first tier that gives a clear answer: Gett's official status feed, then a direct HTTP probe, then an ICMP network ping, and finally reports from visitors. The Verification tier box above tells you which one produced the verdict you are looking at. When enough separate people report a problem for it to be well outside what Gett normally sees, that counts as evidence too, which is how a partial fault can show here before an operator's own status page catches up.

    Gett (gett.com) is re-checked continuously, and this page picks up any change on its own, with no refresh needed.

    Common Gett problems users report

    • Gett app fails to load the ride booking screen or crashes during fare estimation
    • Login fails or session expires immediately after authentication
    • Live driver tracking map shows no available vehicles in your area
    • Booking confirmation gets stuck in 'searching for driver' state indefinitely

    What to do when Gett is not working

    First check the banner above. If it shows evidence of problems, the fault is most likely on Gett's side and waiting is usually the only option. If it shows nothing wrong, clear the app cache and reinstall it, check that location permissions are enabled, and try booking from a different network or device to rule out local connectivity issues.

    About Gett

    Gett is a ride-hailing platform that connects passengers with professional drivers for on-demand transportation. When Gett is down, users cannot book rides, see driver locations, or track their journeys in real time.

    Official Gett resources

    Cross-check an incident with the company's own channels:

    Frequently asked questions

    Is Gett down right now?

    No. Our checks are finding no problems with Gett right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Gett continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.

    What usually goes wrong with Gett?

    The problems visitors report most often on this page are can't connect, can't log in, website / app down, lag or disconnects, no response / timing out, orders or tracking and no notifications. Those are the options the report button offers for Gett, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.

    Why is Gett not connecting to drivers for me when this page says it is fine?

    Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With Gett specifically, Gett's real-time driver dispatch system, which relies on constant communication between the app and active driver networks, can experience outages separate from general website availability. When this dispatch layer fails, the app cannot retrieve nearby driver lists or send booking requests to Gett's assignment servers, even if other platform services remain operational. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.

    How do I tell whether it is Gett or my own connection?

    For Gett, try booking a ride on the web version at gett.com and on the mobile app simultaneously, checking if both fail or only one does. A problem that follows you across networks and devices is very unlikely to be yours.

    What should I do while Gett is down?

    If this page shows evidence of problems, the fault is most likely on Gett's side. Specifically: do not repeatedly cancel and rebook, as this can lock your account or queue duplicate requests that charge you multiple times when service returns. Reporting it here helps other people see they are not alone.

    How does status.buzz check Gett?

    Continuously, around the clock. Gett does not publish a machine-readable status feed, so we cannot read a verdict from them. We probe gett.com directly over HTTP, fall back to an ICMP ping if that is inconclusive, and weigh reports from visitors. That means we can tell you the service is unreachable, but not what Gett says about it. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.

    Is status.buzz affiliated with Gett?

    No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to Gett or gett.com. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need Gett's own support, not us.