Robinhood Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

Robinhood Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Squiddy🦑 (@Squiddyderpypy) reported 12 seconds ago

  @virtuals_io @RobinhoodApp @axol_io damn, fumbled hard on Raxol

• 
  John Christmas (@j_christmas7172) reported 20 seconds ago

  @RobinhoodApp Anyone using this app is stupid. They will take control of you account

• 
  Charlie (@Charlie85270R) reported 54 seconds ago

  We now support @RobinhoodApp chain on Octav 🤠

• 
  0xmyopic (@0xmyopic) reported 2 minutes ago

  There’s only one app that can take down @RobinhoodApp @baseapp Can you hear the storm approaching, Robinhood?😎🫡

• 
  SF Trades (@Sammoneytalks) reported 5 minutes ago

  I tried setting up a robinhood UK account and it always takes me to the US launchpad no matter what I do. Support have been no help. Any ideas? @RobinhoodApp @AskRobinhood

• 
  Texxas (@Texxas) reported 9 minutes ago

  @vincentvinod @RobinhoodApp scroll down, you will see the robinhood section. the pad supports 3 chains

• 
  Artyom (@artyom_mtr) reported 9 minutes ago

  If @RobinhoodApp is using @0xPolygon network a lot why they don't relist $POL ex $MATIC token for trading on their app then? Don't just ignore this, answer to community! $BTC $ETH $SOL $ADA $XRP $DOT $AVAX $OP $ARB #Bitcoin

• 
  okan (@okanruhi) reported 10 minutes ago

  @RobinhoodApp @AskRobinhood My account has been under “unusual activity” review for days. Called support — got nowhere, no real answers, no timeline beyond a vague date. I have a trade to execute Monday and no way to reach anyone who can actually help. This is unacceptable. #Robinhood #CustomerService

• 
  Lior (@liorsela) reported 14 minutes ago

  Dear @RobinhoodApp Small but annoying staking issue: every time I get rewards, I have to manually type a bunch of tiny decimal amounts instead of just staking everything. Super easy fix: ✅ Auto-stake rewards by default OR ✅ Add a simple “Stake All” button This has to be bugging tons of us. Can we get this sorted? @RobinhoodCrypto @AskRobinhood

• 
  Nugget (@Nugget_Trades) reported 14 minutes ago

  I’ve been a @RobinhoodApp Gold Card holder for a while now, and my first chargeback experience has been disappointing. The customer support has been well below what I expected. Unless things improve, I don’t see the @RobinhoodApp Gold Card remaining my primary card.

• 
  beau wilson (@ibeauw) reported 17 minutes ago

  @RobinhoodApp I’m ready to be off the waitlist, help me out Robinhood team 🤞🤞🤞

• 
  Alchemist Jones (@AgenticJonesy) reported 17 minutes ago

  @RobinhoodApp Only problem is i've been waiting forever

• 
  Wearysoles (@wearysoles1776) reported 26 minutes ago

  @RobinhoodApp I've blocked and muted this ad, but it still pops up This is a terrible company and their other ads had many posts hidden from angry users.

• 
  vik ⚡️ (@vscorrpio) reported 27 minutes ago

  found an interesting honeypot ($RIALTO) on @RobinhoodApp today. i aped it myself, got drained, felt pretty stupid, so i figured i’d reverse it. turns out it was a pretty clean allowance bypass, and you don’t see those every day. CA: 0xefd3db0271aa579b8f9f1e4ab91a9d17fea1faa9 attacker helper: 0x5e3c1C6F90d35499C40A5f5769822AF2a631d702 attacker: 0x281FF81dF0Eca1F3F7Ba2A48499c7A83D216a2A8 both contracts were unverified, so most of the reversing was done with a mix of decompilers, AI, and manual analysis. normally an ERC20 works like this: - alice owns tokens. - alice calls approve(bob, 100). - the contract stores that allowance. - bob can now call transferFrom(alice, someoneElse, 100). without that approval, transferFrom should revert. that’s basically the entire security model behind ERC20 allowances. on $RIALTO, transferFrom has another branch. before it checks the allowance, it loads a value from a hidden mapping in storage slot 0 using msg.sender as the key. if that value is non-zero, the allowance check is skipped completely. roughly: if (hidden[msg.sender] != 0) { // skip allowance check } else { require(allowance[from][msg.sender] >= amount); } the attacker helper contract had hidden[attacker] = 0x64. that single storage value effectively made it a privileged spender. it could call transferFrom(holder, attacker, amount) against any holder without ever receiving an approval from that holder. i also suspect this has a decent chance of slipping past a lot of automated bytecode scanners. most quick scanners look for obvious blacklist logic, owner mints, tax changes, or suspicious selectors. this one hides inside an otherwise normal-looking transferFrom implementation. they were also actively market making the token. volume looked organic, there were real-looking sells, larger buys getting sold into, then the chart recovered again. the price action looked surprisingly legitimate even though the whole thing was all fake. since @RobinhoodApp is only on day 2, stuff like this was bound to show up sooner or later. security tooling and risk scoring on new chains usually takes time to catch up, so don’t blindly trust green checkmarks on terminals like @BasedBot which btw great job for working so well on day0 when nobody else was around stay safe out there.

• 
  jejela (@texmaxie) reported 31 minutes ago

  @merts_eth @RobinhoodApp @vladtenev damn