Skip to content

Outage tracker

Robinhood: incident history

The last 24 hours in detail, Robinhood's declared incident record, and our regional check results beside it.

← Back to Robinhood's check readings

We started checking Robinhood on August 20, 2026, which is 65 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me when Robinhood reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Robinhood's own statement from its status page, with our regional reading beside it.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Robinhood's own status page declared. Below it, any public chatter we saw about Robinhood and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Robinhood's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Unverified user reportsNo reports about Robinhood in the last 24 hours, which is not evidence that nothing is wrong.
Robinhood's status pageNo incident declared in the last 24 hours.

Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Robinhood's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Robinhood next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Checks passing by region

Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionChecks passingProbes recorded
US-East99.97%9068
US-West99.96%9064

Their declared record

Robinhood's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.

Bank Transfers IssueMinor incident
Apr 25, 2022, 4:37 PM UTC to Apr 25, 2022, 4:52 PM UTC (15 min)resolved
their latest update (Apr 25, 2022, 4:52 PM UTC): This incident has been resolved.
Crypto Trading IssueMajor outage
Mar 29, 2022, 11:45 PM UTC to Mar 29, 2022, 11:59 PM UTC (13 min)resolved
their latest update (Mar 29, 2022, 11:59 PM UTC): This incident has been resolved.
Phone Support IssuePartial outage
Mar 17, 2022, 2:37 PM UTC to Mar 17, 2022, 3:46 PM UTC (1h 10m)resolved
their latest update (Mar 17, 2022, 3:46 PM UTC): This incident has been resolved.
Market DataMinor incident
Mar 4, 2022, 3:16 PM UTC to Mar 4, 2022, 4:55 PM UTC (1h 39m)resolved
their latest update (Mar 4, 2022, 4:55 PM UTC): This incident has been resolved.
Service DisruptionMajor outage
Dec 7, 2021, 4:50 PM UTC to Dec 7, 2021, 10:53 PM UTC (6h 3m)resolved
their latest update (Dec 7, 2021, 10:53 PM UTC): This incident has been resolved.
Trading DegradedMajor outage
Dec 1, 2021, 11:04 PM UTC to Dec 2, 2021, 2:53 AM UTC (3h 50m)resolved
their latest update (Dec 2, 2021, 2:53 AM UTC): This incident has been resolved.
Login IssuesMajor outage
Nov 11, 2021, 4:08 PM UTC to Nov 11, 2021, 5:47 PM UTC (1h 39m)resolved
their latest update (Nov 11, 2021, 5:47 PM UTC): We fixed the issue that was affecting some customers’ ability to log in to their accounts. Customers should now be able to log in without trouble.
Website IssueMinor incident
Nov 9, 2021, 4:25 PM UTC to Nov 9, 2021, 6:38 PM UTC (2h 13m)resolved
their latest update (Nov 9, 2021, 6:38 PM UTC): This incident has been resolved.
Bank Transfer IssuesMajor outage
Nov 9, 2021, 3:06 PM UTC to Nov 9, 2021, 3:45 PM UTC (38 min)resolved
their latest update (Nov 9, 2021, 3:45 PM UTC): This incident has been resolved.
Crypto Trading IssuePartial outage
Sep 27, 2021, 7:52 AM UTC to Sep 27, 2021, 9:09 AM UTC (1h 17m)resolved
their latest update (Sep 27, 2021, 9:09 AM UTC): This incident has been resolved.

Showing the 10 most recent of 50 incidents Robinhood has declared in the history we hold.

These entries are Robinhood's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

Robinhood's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.

Full detail on what a probe does and does not prove is in the methodology page.