1. Home
  2. Companies
  3. Lloyds Bank
  4. Harrogate
Lloyds Bank

Lloyds Bank status: access issues and outage reports

No problems detected

If you are having issues, please submit a report below.

Full Outage Map
  • Lloyds Bank generated 0 outage signals in the last 24 hours around Harrogate, including 0 direct reports.

Lloyds Bank plc is a British retail and commercial bank with branches across England and Wales. Lloyds Bank offers current accounts, savings, investments, loans, credit cards and other financial products.

Problems in the last 24 hours in Harrogate, England

The chart below shows the number of Lloyds Bank reports we have received in the last 24 hours from users in Harrogate, England and surrounding areas. An outage is declared when the number of reports exceeds the baseline, represented by the red line.

At the moment, we haven't detected any problems at Lloyds Bank. Are you experiencing issues or an outage? Leave a message in the comments section!

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

Lloyds Bank Issues Reports

Latest outage, problems and issue reports in social media:

  • WilliamOak37452
    William Oakley-Grant (@WilliamOak37452) reported

    @AllianzAssistUK you are the absolute worst travel insurance company I have ever dealt with. Timelines change constantly. I have no idea why @LloydsBank use you as partner! Customer service is NONEXISTENT!

  • ls39767284
    LisaS (@ls39767284) reported

    If you want a business bank which actually works, don't go with @LloydsBank . Their securities team won't pick up the phone and nor do they reply to emails. Customer service staff are completely impotent in managing to unblock the stonewalling.

  • DarthFuzz
    🇾🇪 (@DarthFuzz) reported

    @DavidWebbTweet @LloydsBank Keep scrolling down on that page you were on. It’s the App, and it’s nothing new, Biometrics have been used in it for years - it was Touch ID and now Face ID

  • kiborocket
    Kiborocket (@kiborocket) reported

    @LloydsBank Finally someone from your complaint department has responded and admitted you have a widespread issue with your app and the it teams are looking at this. Why do you put customers through this. Very poor service

  • kiborocket
    Kiborocket (@kiborocket) reported

    @LloydsBank No I cannot get through can you advise if you have a widespread issue or just me as I've tried on two devices getting the same technical difficulties message

  • tcumminsap
    The Cummins Accountability Project 🌎 (@tcumminsap) reported

    @LloydsBank Original post “before banning me from Chat” Dm “we can’t sort this here use our online chat service”. Point enforced. Cut and paste banking from a shot and waste of a bank.

  • ls39767284
    LisaS (@ls39767284) reported

    @LloydsBank No-one is available in the securities team though. Not all last week and not this week either. You are still holding security for loans repaid years ago because our business relationship manager overlooked this. Shocking service!

  • lauriefletcher
    Laurence Fletcher 💙 (@lauriefletcher) reported

    @Moneybox 2of2 and the accounts were closed, the funds are now missing. Our local branch seems entirely incapable of solving the problem. We’ve also heard of another charitable organisation local to us that has the same problem @LloydsBank

  • MrRatbags
    RatBags (@MrRatbags) reported

    @LloydsBank How on earth are you not yet supporting Samsung pay!!! I'm actually thinking of moving my Bank to @Barclays OR @HSBC as they got the memo and support Samsung pay. Disappointed

  • UchechiOsuji3
    Uchechi Osuji (@UchechiOsuji3) reported

    @LloydsBank Lloyds bank, you have locked me out of my account for 2 months and refused to send OTP to my address to unlock my account. All the efforts I made to get help from your unprofessional call handlers proved abortive because none of them seems to know what to do. I guess no training.