United States-based trading platform, Coinbase has fully resumed operations after 2 hours of disrupted transactions on the exchange's mobile app and website.
The latest development was revealed on X via Coinbase's support handle, informing customers of the significant progress and thanking them for their patience. “Coinbase is now fully recovered. We appreciate your patience and apologize for the inconvenience,” Coinbase's support wrote on X.
Coinbase is now fully recovered. We appreciate your patience and apologize for the inconvenience. https://t.co/AAzEMPaJGL
— Coinbase Support (@CoinbaseSupport) May 14, 2024
Notice Of A System-Wide Outage
During the early hours of today, Coinbase, through its support handle on X, revealed that the exchange is experiencing a potential glitch that has interrupted operations on the trading platform.
The support team assured customers that their funds were safe, adding that investigations to remedy the situation were ongoing.
A few hours after notifying users of the mishap interrupting the exchange's services, the support handle notified customers that some services were recovering, pleading for patience from users who might still be experiencing interruptions on the exchange.
The support team announced, "We are seeing some services recover. We know customers may still be encountering connectivity problems, and we appreciate your patience while we work to correct this. We're still monitoring this closely."
Possible Reasons For Coinbase Service Interruption
Having closely followed the updates from Coinbase's support group, it is relatively fair to say that the trading platform never stated any reason behind the mishap despite claims of ongoing investigations.
However, based on a previous similar occurrence, which happened following a substantial Bitcoin price rally in March, it is safe to say that Coinbase's recent mishap was not because of an increment in transaction volumes, as no significant increase in transaction count was recorded within the interruption window. Hence, chances are high that the glitch could emanate from internal sources rather than external origins.
