Not only was the experience painful for the engineers working to ensure the services are back up, but also painful to the customers who couldn’t access their accounts, according to CEO Nikolay Storonsky.
“You will get no excuses from me,” Storonsky wrote in a blog post. “We have let you down and I take full responsibility for what happened. It is never acceptable for our customers to ever be without access to their funds — period.”
So, what happened then? On Friday morning (Sept. 29) Revolut’s transaction database began to malfunction. Aware of this, it proceeded to switch to the backup server. That’s when disaster struck as the backup server struggled to process live transactions.
The issue then worsened, with a sudden 50 percent increase of user activity leading to around 25 percent of transactions timing out, frequently spiking to 75 percent.
By the end of the evening, Revolut engineers discovered that the issue was not the application or database, but instead a server failure. After performing a server migration, all services had been fully restored.
Revolut made it clear that all personal data and customer funds were completely secure at all times.
While this was an unforeseen issue that was hastily resolved, there had been times where the issues arose that were beyond its control.
In July, Revolut, Monzo, Starling Bank, Curve and payments startup Fire all suffered from outrages due to issues with their processor Global Processing Services (GPS). A similar thing happened in March. This incident was not related to GPS.