Points of Focus

• Revolut falsely pushed Bitcoin crash-to-$0.02 notifications to users before the price snapped back to normal within seconds.
• The bug hit BTC, ETH, SOL, and XRP simultaneously, pointing to a corrupted data feed, while no other exchange showed any movement.
• Revolut has not acknowledged the incident despite serving 70 million users.

On the morning of May 8, Revolut users across the UK and Europe woke up to push notifications telling them Bitcoin (BTC) had collapsed to $0.02. It had not.

What they experienced was a pricing data glitch inside the Revolut app.

thx for the heart attack @Revolut pic.twitter.com/vmXImIaFTO

— lito (@litocoen) May 8, 2026

The incident trended on X and quickly spread across Reddit, where r/Revolut threads lit up as users compared the alerts they received and tried to work out what had just happened to their holdings.

What users actually experienced

The sequence of events was disorienting by design. 

Users first received a Revolut push notification stating that Bitcoin had fallen to $0.02, a figure implying a 99.99% crash from real levels. Moments later, some received a follow-up alert stating BTC had recovered to around $60,000.

Just received this one.

We are either dead as blockchain ecosystem or another non-technical guys pushing code on prod using AI @Revolut pic.twitter.com/Pv6BbbprTZ

— BulgarianDegen 🇧🇬 (@BulgarianDegen) May 8, 2026

Inside the app, the crypto tab briefly reflected the erroneous price. Several users report attempting to act on the signal in real time. 

One user on r/Revolut notes they “tried to buy in at €33k” but Revolut would not execute the trade at that rate, suggesting the order execution layer did not honor the glitched display price. Another user on r/Revolut asked openly whether Revolut would honor the displayed price retroactively if they bought it now.

The confusion extended beyond Revolut’s own user base. 

On r/CryptoCurrency, a user who had received the notification posted asking whether a “50 percent crash in 10 minutes” was real, what the support levels were, and whether it was a buying opportunity. 

Charts for BTC, ETH, SOL, and XRP in the Revolut app all showed similar anomalies, suggesting a data feed issue rather than a single-asset issue.

The glitch, not the price, is the story

Bitcoin did not crash. Every major exchange, aggregator, and chart outside the Revolut ecosystem showed BTC trading normally throughout the period. 

The issue was entirely contained within Revolut’s price display and notification pipeline, almost certainly caused by a corrupted or dropped data feed that fed a zero or near-zero value into the app’s price engine before the correct data restored itself.

Revolut has not, at the time of writing, published any official statement about the incident, acknowledged it on X or its status page, or confirmed how many users received the erroneous notification. 

Why this matters more than a simple bug

A bad price feed in itself is a minor technical failure. What makes this incident more serious is the notification layer. Revolut did not just display a wrong number inside the app. It actively pushed a false alert to users’ lock screens, telling them their Bitcoin had dropped to near zero. 

For someone without access to a second data source at that moment, especially a newer retail investor, that notification is indistinguishable from a real market event. This creates two risks. 

• The first is panic selling by users who do not wait to verify the price elsewhere. 
• The second is the reverse: users attempting to buy at what they think is a once-in-a-lifetime price, only to find Revolut does not honor the glitched rate, and they are left having wasted time or triggered partial account actions.

Revolut now has 70 million users globally and has been aggressively expanding its crypto offering. With that scale comes a responsibility to prevent its notification infrastructure from becoming a source of market misinformation, even by accident.