Is Santander down in Wrexham, Wales?
No problems detected
If you are having issues, please submit a report below.
The latest reports from users having issues in Wrexham come from postal codes LL14.
Santander UK plc is a British bank, wholly owned by the Spanish Santander Group. Santander offers current accounts, savings, investments, loans, credit cards and other financial products.
Full Outage Map
TransactionsProblems in the last 24 hours in Wrexham, Wales
The chart below shows the number of Santander reports we have received in the last 24 hours from users in Wrexham 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 Santander. Are you experiencing issues or an outage? Leave a message in the comments section!
Most Reported Problems
The following are the most recent problems reported by Santander users through our website.
-
Mobile App (41%)
-
Website (25%)
-
Transactions (17%)
-
Login (10%)
-
Transfer (5%)
-
Withdrawals (2%)
Live Outage Map Near Wrexham, Wales
The most recent Santander outage reports came from the following cities: Wrexham.
| City | Problem Type | Report Time |
|---|---|---|
 Wrexham |
Transactions | |
| Buckley |
Mobile App | |
| Wrexham |
Withdrawals | |
| Chester |
Login | |
| Chester |
Login | |
| Wrexham |
Mobile App |
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.
Santander Issues Reports Near Wrexham, Wales
Latest outage, problems and issue reports in Wrexham and nearby locations:
-
Virtutis Gloria Merces - Slava Ukraini
(@Thoma5Reid) reported
from
Huntington, England
@santanderuk I'm trying to access my banking via your banking app, but I get a message saying server not responding try again?
Santander Issues Reports
Latest outage, problems and issue reports in social media:
-
Gemma Dee
(@dee_gemma) reported
@santanderuk my debit card is not working since yesterday. I have tried to call your phone lines but the line drops every time during the recorded message and your chat facility is sending me in circles thinking my card is blocked or stolen. Please help.
-
Maggie Agnew
(@maggieagnew87) reported
@RonnieH88083611 @santanderuk No that would be your problem, all I did to make sure I didn't go overdrawn was keep track of what I spent knowing how much should be in the bank!
-
𝕲.𝕸. 𝕲𝖗𝖎𝖋𝖋𝖎𝖓
(@GMWritesHorror) reported
@santanderuk No it's not. It is down again.
-
RL Capture
(@RlCapture) reported
@santanderuk can you please first unlock my account which has taken almost 3 days !! 2nd I was promised my direct debits would go out as normal , which I’d not the case! Please fix ! I will be considering moving to another bank after this lack of customer care 😐
-
Sinclair
(@SimmySinclair) reported
@santanderuk trying to use the online chat service to make a complaint about my experiences yesterday as your phones lines are all busy. But there is no way to complain online 🙄
-
Paul Williamson
(@paulwill70) reported
@petenew100 @santanderuk Compensation, really? The bank was doing its job and making sure funds were safe. Hardly worth compensating is it ffs. If u need compensation for that then you have issues
-
It's only my opinion #Peace #Love & #Equality
(@gssnutrition) reported
@santanderuk I still can't access my bank account via the Santander mobile app. When will it be back online?
-
steven turner
(@iamhere1981) reported
@santanderuk hi .I used my top up card a few times yesterday to get my electric on and I don't think they went through bit if they did and I end up overdrawn what help can I get
-
Jana Hrickova
(@cleistro) reported
@santanderuk The app is not working.. Message ooops something went wrong is still there.
-
Jana Hrickova
(@cleistro) reported
@santanderuk The app is still not working, don't like the message.. Oops something got wrong.