Key Takeaways
- • Revolut's app displayed Bitcoin at $0.02 on May 8, 2026, while major exchanges quoted BTC near $79,000, triggering widespread user panic and social media alerts.
- • The company attributed the pricing error to a third-party data feed provider failure, not a platform malfunction or security breach affecting user holdings.
- • Users received push notifications warning of 52-week lows and apparent sell orders at distorted prices, causing confusion about whether automated trades had executed.
- • Revolut confirmed that no actual transactions occurred at the erroneous prices and user assets remained secure; the glitch affected only price display and alerting systems.
- • The incident sparked broader concern about cryptocurrency pricing infrastructure vulnerabilities and the reliance on third-party data providers for real-time market data delivery.
Summary
On May 8, 2026, Revolut users experienced a significant pricing glitch that briefly displayed Bitcoin trading at $0.02—a level approximately 99.97% below actual market prices of $79,000 quoted on major exchanges. The malfunction triggered immediate panic among the fintech platform's user base, with affected customers receiving push notifications alerting them to catastrophic price declines and 52-week lows. Screenshots circulated rapidly across social media platform X, where users expressed alarm and confusion about the validity of the alerts and whether trades had executed at the distorted prices.
The company subsequently confirmed that a third-party data provider failure was responsible for the erroneous pricing information. According to Revolut's statement, the glitch affected price displays, charting data, and alert systems linked to Bitcoin and multiple other cryptocurrency assets. One analysis suggested the error stemmed from a "corrupt tick pushed through Revolut's pricing system," which briefly anchored price charts at significantly depressed levels before the system corrected to accurate market data. The issue appeared isolated to Revolut's application interface and data visualization layers.
Revolut reassured customers that no actual financial transactions occurred at the $0.02 price point and that user cryptocurrency holdings remained secure. The platform emphasized that the incident was a technical display error rather than a security breach or loss of asset custody. User concerns centered on whether margin calls or automated liquidation triggers could have been activated by the false pricing data, though Revolut's statement addressed these concerns by clarifying that trading systems did not execute orders based on the corrupted feed.
The incident underscores structural vulnerabilities in cryptocurrency trading infrastructure, particularly the dependence on third-party data aggregators and pricing feeds. For institutional and retail investors utilizing fintech platforms, the episode raises questions about failsafe mechanisms, alert validation protocols, and contingency procedures during data provider outages. While Revolut's response included full restoration of accurate pricing and customer communication, the incident highlights the operational risks associated with cryptocurrency markets' still-evolving technological maturity and the critical importance of redundant data sourcing across multiple independent providers.
The company subsequently confirmed that a third-party data provider failure was responsible for the erroneous pricing information. According to Revolut's statement, the glitch affected price displays, charting data, and alert systems linked to Bitcoin and multiple other cryptocurrency assets. One analysis suggested the error stemmed from a "corrupt tick pushed through Revolut's pricing system," which briefly anchored price charts at significantly depressed levels before the system corrected to accurate market data. The issue appeared isolated to Revolut's application interface and data visualization layers.
Revolut reassured customers that no actual financial transactions occurred at the $0.02 price point and that user cryptocurrency holdings remained secure. The platform emphasized that the incident was a technical display error rather than a security breach or loss of asset custody. User concerns centered on whether margin calls or automated liquidation triggers could have been activated by the false pricing data, though Revolut's statement addressed these concerns by clarifying that trading systems did not execute orders based on the corrupted feed.
The incident underscores structural vulnerabilities in cryptocurrency trading infrastructure, particularly the dependence on third-party data aggregators and pricing feeds. For institutional and retail investors utilizing fintech platforms, the episode raises questions about failsafe mechanisms, alert validation protocols, and contingency procedures during data provider outages. While Revolut's response included full restoration of accurate pricing and customer communication, the incident highlights the operational risks associated with cryptocurrency markets' still-evolving technological maturity and the critical importance of redundant data sourcing across multiple independent providers.
Go deeper than the headline
Research every firm in this story, track the ones that matter and get the daily briefing — free for 7 days.