Bitcoin Drops To 2 Cents! Revolut Users Report Massive BTC Price Glitch

A third-party data feed failure caused Revolut to display Bitcoin at 2 cents on May 8, exposing the risks of relying on external pricing providers for custody and trading platforms. The glitch, which also affected XRP, Solana, and stablecoins, remained isolated to Revolut’s app while major price aggregators showed no corresponding movement, raising questions about data validation controls at retail crypto platforms.

• Bitcoin displayed at $0.02 on Revolut’s app with a 52-week low notification, while CoinMarketCap and CoinGecko showed no price movement
• The pricing error affected multiple assets simultaneously including XRP, Solana, USDT, and USDC, not just Bitcoin
• Revolut blamed an unnamed external pricing provider for the disruption and is still evaluating root cause details

• $0.02 Bitcoin price shown on Revolut versus $39,900 recovery price within minutes
• May 8, 2026 Date glitch occurred, affecting multiple cryptocurrency assets simultaneously
• 50% Intraday chart plunge shown on Revolut before price snapped back to normal

Revolut users witnessed what appeared to be the most dramatic cryptocurrency crash in history on Friday when the fintech app’s pricing feed collapsed, displaying Bitcoin at 2 cents and flooding social media with screenshots of a market that existed nowhere else.

The company quickly confirmed the outage stemmed from a failure at an unnamed third-party pricing provider and said engineers had resolved the issue, but the incident exposed a critical vulnerability in how retail platforms validate external data feeds.

The pricing anomaly remained entirely contained within Revolut’s ecosystem; major aggregators including CoinMarketCap and CoinGecko reported no corresponding movement in Bitcoin or any other asset during the window.

Revolut Confirms External Provider Failure Behind Bitcoin Price Collapse

Within hours of users reporting the glitch on social media, Revolut acknowledged the problem and attributed it to a service failure at an external pricing data vendor. The company’s support account posted a public statement asking affected customers to monitor its status page while engineers worked on a resolution.

A company spokesperson later confirmed the disruption had been resolved but said Revolut was still evaluating the full technical details of what occurred and which specific provider had failed.

The scope of the outage extended well beyond Bitcoin. Screenshots posted across X and Reddit showed simultaneous price crashes affecting XRP, Solana, and stablecoin pairs including USDT and USDC, assets designed to maintain a one-dollar peg.

One user shared a notification alerting them that Bitcoin had hit a 52-week low of 2 cents, while others reported seeing Bitcoin’s 24-hour chart register a roughly 50% intraday plunge before snapping back to normal levels near $39,900. The synchronized nature of the price failures across unrelated assets strongly suggested a systemic feed error rather than individual market events.

The incident underscores a structural dependency that many retail crypto platforms have not fully addressed: the validation of pricing data from external providers.

No Price Movement on Major Aggregators or Derivatives Markets During Glitch

The isolation of the pricing error to Revolut’s app provides the clearest evidence that no actual market crash occurred. Real-time pricing data from CoinMarketCap and CoinGecko, which aggregate prices from exchanges and trading venues, showed Bitcoin trading at normal levels throughout the outage window.

Derivatives markets including futures and perpetuals contracts saw no corresponding spike in liquidations, unusual trading volume, or volatility that would have been triggered by a genuine 99% asset collapse.

Ranveer Arora, a former quantitative trading lead at PwC and co-founder of Altura.trade, outlined two technical mechanisms that could explain Revolut’s specific price distortion. The first is a corrupt data tick, where a single bad price point pushes through Revolut’s charting system and briefly anchors the display before being corrected by subsequent valid data.

Because Revolut does not operate as an exchange and instead pulls prices from external vendors, a single faulty input is sufficient to produce exactly this type of chart artifact. The second possibility is a transient liquidity gap within Revolut’s order book.

Revolut’s liquidity is shallower than what an institutional exchange offers, so a large sell order could theoretically exhaust available bids and print a sharp downward wick before prices recover, though the lack of matching prints on external platforms makes this scenario less likely.

Both mechanisms point to data validation as the critical vulnerability, not actual market conditions.

Institutional Risk: Custody Platforms Must Validate Third-Party Pricing in Real Time

For institutional investors and custody providers, the Revolut incident raises a material operational question. Platforms holding customer assets have a fiduciary obligation to display accurate pricing, and outages that show false prices, even if briefly, can trigger incorrect automated trading decisions, margin liquidations, or customer panic.

The fact that Revolut’s app displayed the Bitcoin price as 2 cents and sent push notifications about a 52-week low demonstrates that the platform’s alerting system accepted the corrupt data without validation checks.

The outage also highlights the asymmetric risk of outsourcing critical data feeds to single providers. Revolut did not immediately disclose which external vendor had failed, a common pattern when platforms want to avoid reputational damage to their data providers.

However, this lack of transparency prevents customers from assessing whether their platform has redundant data feeds or fallback systems if a primary vendor goes down. Institutional platforms increasingly use multiple pricing feeds from competing providers specifically to catch and isolate failures of this type.

The incident comes at a time when retail crypto platforms have significantly expanded their service offerings to include custody, staking, and leveraged trading, functions that require real-time price accuracy. Revolut did not immediately clarify whether customers could have executed trades during the glitch window based on the false prices displayed, a critical gap in post-incident disclosures.

If trades were executed at displayed prices during the outage, questions about trade reversal and customer compensation could follow, similar to past incidents at mainstream brokerages.

Resolving Root Cause and Preventing Recurrence Remains Open Question

Revolut has not yet published a detailed incident report explaining which pricing provider failed, why the corrupt data passed through validation systems, or what preventive measures it will implement. The company’s statement that it is “still evaluating the full details” suggests the investigation remains ongoing.

Without transparency on these details, it is unclear whether Revolut will add redundant pricing feeds, implement validation logic to flag price moves beyond certain thresholds, or both.

Institutional investors and crypto custody platforms should monitor Revolut’s public incident report when released, and clarify with their own service providers whether similar single-vendor pricing dependencies exist in their platforms. The specific unresolved question is whether Revolut will disclose the name of the failed pricing vendor and implement named technical controls to prevent recurrence, or whether the company will issue only a generic assurance that the issue has been fixed.