Is Ro down right now?

Checking…

Verifying live status…

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

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

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 Ro, 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 Ro

    No evidence of problems with Ro. 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: Ro'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 Ro 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.

    Ro (ro.co) is re-checked continuously, and this page picks up any change on its own, with no refresh needed.

    Common Ro problems users report

    • Cannot log into the app or web portal
    • Scheduled appointments not appearing or unable to book new ones
    • Messages with doctors not sending or receiving
    • Prescription orders stuck or not processing

    What to do when Ro is not working

    First check the banner above. If it shows evidence of problems, the fault is most likely on Ro's side and waiting is usually the only option. If it shows nothing wrong, clear your app cache and reinstall, verify your account email is confirmed in settings, and check that your pharmacy location is still in-network.

    About Ro

    Ro is a telehealth platform connecting patients with licensed doctors for virtual consultations and prescription delivery. When Ro is down, patients cannot schedule appointments, access their medical records, or receive prescriptions, disrupting ongoing treatment.

    Official Ro resources

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

    Frequently asked questions

    Is Ro down right now?

    No. Our checks are finding no problems with Ro right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Ro 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 Ro?

    The problems visitors report most often on this page are can't log in, can't connect, website / app down, messages not sending, orders or tracking, API errors and no response / timing out. Those are the options the report button offers for Ro, 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 Ro not loading 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 Ro specifically, Ro's appointment scheduling, messaging, and prescription fulfillment systems can fail independently, and regional pharmacy network issues may prevent prescription delivery even when the app works. 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 Ro or my own connection?

    For Ro, try logging in on both the web and mobile app from a different network, then check your appointment calendar and message history. A problem that follows you across networks and devices is very unlikely to be yours.

    What should I do while Ro is down?

    If this page shows evidence of problems, the fault is most likely on Ro's side. Specifically: do not repeatedly request new prescriptions or rebook appointments, as this creates duplicate orders that are hard to cancel and may delay your actual treatment when service returns. Reporting it here helps other people see they are not alone.

    How does status.buzz check Ro?

    Continuously, around the clock. Ro publishes a machine-readable status feed, so our first check reads it directly and reports what Ro itself says. If that feed is unreachable we fall back to a direct HTTP probe, then an ICMP ping, then reports from visitors. 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.

    Does Ro have an official status page?

    Yes, at status.ro.co, and it is linked further up this page. That is Ro's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.

    Is status.buzz affiliated with Ro?

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