Revolut reported a service disruption affecting payments and account access on Tuesday as Google Cloud investigated problems in its London region. The digital bank listed card payments, cash withdrawals, transfers, sign-in and cryptocurrency services among functions that were unavailable or partly unavailable. Revolut said customers’ money and data remained safe while engineers worked to restore full service.
Reuters reported that a person familiar with the matter linked Revolut’s disruption to the Google Cloud incident. Google’s service-status information showed multiple products experiencing problems in the europe-west2 region, which is based in London. The provider said its engineering team was investigating the disruption.
PAYMENTS AND ACCESS WERE INTERRUPTED
The Guardian reported that users encountered errors when attempting to open the Revolut app, leaving some unable to manage accounts or complete transactions. Revolut’s status information also identified disruption to registration and sign-in functions. The company said it had been working on the incident since it was identified in the morning.
Revolut uses Google Cloud infrastructure under a strategic technology partnership disclosed by the companies. Reuters separately reported login problems at ING Germany on Tuesday, although it said no connection to the Google incident had been established. The wider disruption therefore affected more than one financial-service channel, but its full banking impact was not yet quantified.
RESTORATION AND RESILIENCE ARE NEXT
The incident demonstrates how a regional cloud failure can interrupt several customer-facing functions at the same financial institution at once. It does not, on the evidence available, indicate that customer funds or data were compromised. The operational question is how quickly services recover and whether traffic can be shifted safely to unaffected infrastructure.
Revolut’s next milestone is confirmation that card payments, withdrawals, transfers and account access have returned to normal. Google Cloud also needs to publish a final incident status and, if appropriate, a technical explanation after recovery. The story’s tense and service-status details must be checked immediately before publication because restoration could change the factual position.