Lloyds, Halifax and Bank of Scotland Hit by App Outage Again

Lloyds, Halifax and Bank of Scotland app users spent Wednesday lunchtime locked out of their accounts after Lloyds Banking Group confirmed that thousands of customers could not log in or move money. Reports to the outage tracker Downdetector spiked from around 11:15 BST on 3 June 2026, with the apps throwing a 503 server error, the code a system returns when it cannot handle requests.

The group apologised and said it was working hard to fix it. This is the second time in three months that the same banking group has left customers stranded, and UK lenders as a whole have now logged weeks of cumulative downtime that the regulator’s new rulebook was meant to prevent.

Thousands Locked Out on a Wednesday Lunchtime

The complaints followed a familiar shape. People could not pay bills, transfers stalled, and balances would not load. Most of the early reports came from London, Belfast and Cardiff, with customers in Liverpool, Newcastle, Birmingham and Manchester also flagging problems. A message inside the Lloyds app told users that logging in again might help, and if it did not, to try later.

Lloyds Banking Group says it is the UK’s largest retail and commercial bank, serving 26 million customers across its three high-street brands. When its core systems stumble, the blast radius is enormous. Halifax confirmed the same trouble on its own channel, telling one customer to bear with it while engineers worked on the fix.

We’re aware some customers are having issues with our app and online banking. We’re really sorry about this. We’re working hard to fix it and will let you know as soon as we’re back to normal.

That apology came in Lloyds Banking Group’s outage update on X, the channel banks now lean on first when their own apps stop talking to customers. By early afternoon the bank had not given a fixed restoration time.

Three Brands, One Set of Servers

The reason Halifax and Bank of Scotland fall over at the exact moment Lloyds does is simple. They are not three separate banks under the hood. They run on shared digital plumbing inside one group, so a single fault propagates across all three brands and the 26 million customers who bank with them. The branding on the login screen changes; the servers behind it do not.

That design is efficient until it is not. The same architecture was at the centre of the group’s last big embarrassment. On 12 March 2026, a botched overnight software update introduced a defect in the way the apps handled transaction data. For a few hours that morning, as many as 447,936 customers could briefly see fragments of other people’s account activity, and up to 114,182 could see more detailed payment information. Exposed data could include transaction details, payment references and even National Insurance numbers.

The group later said it found no evidence anyone lost money because of that breach. The point holds anyway: one weak link in shared infrastructure does not break one app, it breaks the lot.

Thirty-Three Days of Downtime in Two Years

Wednesday’s wobble is one data point in a much longer record, and the record is grim. MPs have already put hard numbers on how often Britain’s banks go dark.

What the MPs Found

According to data the Treasury Committee published on bank IT failures, nine of the biggest banks and building societies operating in the UK clocked enough unplanned outages over two years to add up to more than a month of lost service. The committee gathered the figures by writing to chief executives at Barclays, HSBC, Lloyds, Nationwide, Santander, NatWest, Danske Bank, Bank of Ireland and Allied Irish Bank.

• 803 hours of unplanned outages across the nine firms between January 2023 and February 2025
• 158 separate IT failure incidents over the same window
• 194 hours at NatWest, the worst single tally, with HSBC next on 176
• 33 days of combined downtime, the equivalent of over a month with no banking

The causes repeat too: problems with third-party suppliers, disruption from system changes, and internal software defects. None of that is exotic. It is the slow cost of running modern apps on ageing core systems that were never built for always-on mobile banking.

The Latest Run of Failures

The past 18 months have been especially rough, and the bill for getting it wrong is no longer theoretical.

The Barclays failure was almost a textbook worst case. A software problem in a critical module of its UK mainframe knocked out roughly 56% of payments for those who could log in, and it landed on the self-assessment tax deadline, when people scramble to pay HMRC before midnight.

The Rules That Were Meant to Stop This

All of this was supposed to be on the mend by now. The Financial Conduct Authority’s operational resilience rules (FCA, the City regulator) took full effect on 31 March 2025, after a long transition period. They are not a vague aspiration. They force firms to name their important business services, the ones that cause real harm to customers if they break, and to set hard impact tolerances for how long disruption can last.

Under the FCA’s operational resilience framework, a bank might decide payment processing cannot be down for more than a set number of hours, then has to map, test and invest enough to stay inside that limit during severe disruption. Lloyds Banking Group’s 12 March data incident came less than a year after that deadline. Wednesday’s outage came roughly 14 months after it.

The rules give the regulator the standing to ask hard questions about why a service keeps breaching its own tolerances. Whether that translates into a penalty with teeth is the test still ahead for the FCA.

What Affected Customers Can Claim

An outage is not automatically a payday. The FCA does not force banks to hand everyone a refund when an app goes down, and most short blips end with an apology and nothing more. Where money is involved, though, you have real footing.

If a missed or late payment triggered a charge because the app was down, you are entitled to be put back in the position you would have been in had the system worked. Under the Payment Services Regulations 2017, a provider is liable for charges and interest a customer has to pay because a payment was not made, or was made late, through no fault of their own.

• Keep evidence: screenshots of failed transactions, error messages, statements and any late-fee notices
• Add up direct losses such as late-payment fees, overdraft charges or interest caused by the outage
• Complain to the bank first and ask for both your costs back and an award for distress and inconvenience
• If the bank does not resolve it, escalate to the Financial Ombudsman Service, which handles disputes the bank cannot settle

For scale, the group’s March data glitch ended with £139,000 paid to 3,625 customers, an average of about £38 each, mostly for distress rather than financial loss. Barclays, by contrast, expects its January 2025 outage to cost it millions because so many real payments failed.

Lloyds said it expected its services back to normal the same day. The compensation maths, as usual, arrives later.

Frequently Asked Questions

Are the Lloyds, Halifax and Bank of Scotland apps back up now?

The group said it was working to fix the fault and would update customers once services returned to normal. Outages of this type are usually resolved within hours rather than days, and the bank pointed users to its official social channels and online banking status for live updates.

Why are Halifax and Bank of Scotland down when the problem is with Lloyds?

All three brands belong to Lloyds Banking Group and run on the same shared technology behind the scenes. A single fault in that core infrastructure affects every brand at once, which is why customers across all three report the same login and payment failures simultaneously.

Can I get compensation for a bank app outage?

There is no automatic refund, but you can claim if the outage caused you a measurable loss, such as a late fee or overdraft charge. The Financial Ombudsman Service can award compensation where a bank refuses to put things right, and for complaints referred after April 2024 its awards can reach £430,000.

What should I do if a missed payment caused a late charge?

Gather proof of the failed payment and the resulting charge, then complain to your bank and ask it to refund the cost and cover any knock-on fees. If you are not happy with the response, you can take the case to the Financial Ombudsman Service, typically after the bank has had a chance to reply.

How often do UK banks suffer outages like this?

Far more often than most customers realise. Treasury Committee figures recorded 158 separate IT failure incidents across nine large banks between January 2023 and February 2025, adding up to the equivalent of more than a month of total downtime.

Disclaimer: This article is for general information only and does not constitute financial or legal advice. Compensation outcomes depend on individual circumstances, and readers with a claim should consult their bank, the Financial Ombudsman Service, or a qualified adviser. Figures are accurate as of publication.