Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021
In a world where we are so reliant on technology for everything, from doing our weekly grocery shopping to online banking, it’s no surprise that when something goes wrong, it has a huge domino effect impact. The pressures on apps and online platforms in 2022 is so high that we almost solely depend on them for all of our day to day activities. It’s no surprise, therefore, that when the banking apps suffered partial downtime in March, it felt like Armageddon.
Let’s set the scene a bit here.
When was the last time you popped into a Lloyds bank and transferred money to someone? Or, when was the last time you deposited cash to a cashier in a NatWest branch? I can almost hear your brain whirring from here, trying to figure out when this nostalgic moment last took place. But if I was now to ask you when was the last time you logged into your online banking app, I’m sure the answer would be almost automatic. So what happened when you couldn’t?
It’s estimated that over 18 million people in the UK use online banking. So when the Lloyds, Halifax, and the Bank of Scotland online banking platforms all suffered partial downtime, millions of people were unable to access their accounts properly. The biggest downside? All 3 of these banks are managed by the Lloyds Banking Group. And the most worrying part for customers was seeing “N/A” against their “available funds”. Scary.
It took Lloyds a while to release a statement about the issue, which seemingly came after the influx of comments on social media directed at them. A spokesperson then released the following:
‘We know some of our customers had issues accessing mobile and online banking for a short time this morning.
‘We’re sorry about this and both our website and app are now back to normal.’
What caused the downtime?
Lloyds Banking Group hasn’t released any information about why their online banking platforms went down or what caused it but with such a tremendous amount of reliance now on them, it bodes the question, should they be doing more to make sure this doesn’t happen?
According to the banking group, online banking use has gone up over 25% in the past two years so with this added usage, you’d need excellent website monitoring in place to ensure that any downtime is picked up as quickly as possible.
The solution? Enter StatusCake (bet you didn’t see that coming!). We will monitor your website for uptime, page speed, server, domain, and any SSL issues so you can always have the best performing website possible. The cherry on the cake is you can take a free trial of our paid plans or enjoy a free for life account. Almost sounds too good to be true. Why not try it?
StatusCake Team
Share this
More from StatusCake
Engineering
Beyond Uptime: Building a Self-Healing OpenClaw Observability Stack
3 min read The allure of OpenClaw is undeniable. You deploy a highly autonomous, self-hosted AI agent, give it access to your repositories and inboxes, and watch it reason through complex workflows while you sleep. It is the dream of the ultimate 10x developer tool realized. But as any veteran DevOps engineer will tell you: running an LLM-backed
Daniel
April 23, 2026
When AWS us-east-1 Fails, Much of the Internet Fails With It
7 min read There are cloud outages, and then there are us-east-1 outages. That distinction matters because failures in AWS’s Northern Virginia region rarely feel like ordinary regional incidents. They tend instead to expose something larger and more uncomfortable: too much of the modern internet still behaves as though one place is an acceptable concentration point for infrastructure,
James Barnes
April 15, 2026
In the Age of AI, Operational Memory Matters Most During Incidents
7 min read Artificial intelligence is making software easier to produce. That much is already obvious. Code that once took hours to scaffold can now be drafted in minutes. Boilerplate, integration logic, tests, refactors and small internal tools can be generated with startling speed. In some cases, even substantial pieces of implementation can be assembled quickly enough to
James Barnes
April 10, 2026
AI Didn’t Kill the SDLC. It Made It Harder to See
10 min read Whilst AI has compressed the visible stages of software delivery; requirements, validation, review and release discipline have not disappeared. They have been pushed into automation, runtime and governance. The real risk is not that the lifecycle is dead, but that organisations start acting as if accountability died with it. There is a now-familiar story about
James Barnes
April 2, 2026
When Code Becomes Cheap: The New Reliability Constraint in Software Engineering
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
James Barnes
March 25, 2026
Buy vs Build in the Age of AI (Part 3)
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
James Barnes
March 18, 2026