Challenger Bank Cites “Problem with Servers”

Bank joins GitHub, SumUp in suffering IT concerns currently

Updated 20:26 BST: Monzo states it has settled the challenge following circa ninety minutes. 

Digital-only lender Monzo is suffering what appears to be a sweeping outage that has left prospects unable to make payments or lender transfers.

Transactions, payments and chat providers are all impacted.

The lender acknowledged the challenge on its standing webpage at 19:10 BST, stating “we’re finding all the data we need to have to correct this.”

Monzo down: Challenger joins GitHub, SumUp in owning a big Monday wobble

Monzo has about 4 million prospects.

The outage arrives amid eager awareness from regulators on banking availability, pursuing many prolonged outages in the latest several years amongst the legacy Higher Avenue banks, many of which are reliant on getting old infrastructure.

See also: Give Economic Companies “Sharper Teeth” Over IT Outages: Treasury Committee

Monzo by distinction designed its individual stack. It uses Apache Cassandra as its transactional databases, with its software code penned in Go, and uses a Kubernetes-based microservices architecture, with Apache Kafka underpinning its asynchronous concept queue and AWS hosting most of its infrastructure.

After payment concerns on May well thirty, 2019, Monzo moved a component which connects Monzo to the Uk lender transfer network in-house, blaming a third-occasion for the challenge. “We recognise that functioning our individual infrastructure and systems is the important to dependability, and we necessary to create more specialised expertise into Monzo”, the lender claimed at the time. It is not still crystal clear if this evening’s outage relates to an interior challenge or 1 with an exterior cloud service provider, for instance.

Monzo joins GitHub and SumUp in dealing with outages currently.

We’ll update with write-up-incident assessment when we get it.

See also: GitHub Outage Hints at Ongoing Canary/Creation Challenges