
Santander Online Banking Down: Another Day, Another Major Bank Outage
In March 2025, Santander online banking went down — adding to the pattern of recurring major bank outages in the first months of DORA applicability.
Key Metrics
EU Bank Outages (Jan-Mar 2025)
Barclays + TARGET2 + Santander
was: DORA applicable Jan 17
3 major outages in first 2 months of DORAAverage Annual Frequency
3-5 per year
was: 3-5 per year
No improvement trendRoot Cause Pattern
Structural
was: Varied
Individual fixes insufficientCustomer Priority
Reliability #1
was: Features
Trust eroding with each outageThe Situation
The Recurring Problem
Major European banks experience 3-5 significant digital disruptions per year on average. The causes are diverse but the outcome is consistent: millions of customers lose access to essential banking. This frequency points to systemic issues — aging infrastructure, insufficient resilience investment, inadequate testing, and organizational culture issues.
Each outage individually is tolerable, but cumulatively they erode customer trust. Surveys rank reliability as customers' top priority — above features, rates, and app design. Banks investing in features while experiencing recurring outages are misallocating resources.
Regulatory patience with recurring outages is decreasing. DORA establishes legal obligations where previously there were only best practices.
The Challenge
The Pattern of Recurring Outages
On March 6, 2025, Santander experienced an outage affecting online banking services. In the two months following DORA's January 17 applicability date, the sector experienced outages at Barclays (January 31), TARGET2 (February), and Santander (March 6). This pattern demonstrates that DORA's requirements address demonstrated, recurring deficiencies — not aspirational targets for a resilient sector.
The frequency of major outages suggests structural rather than incidental causes: aging infrastructure patched rather than replaced, insufficient resilience engineering investment, inadequate testing, and organizational cultures prioritizing uptime metrics over resilience engineering.
For Santander, the outage tested DORA Art. 5-6 (ICT risk management), Art. 9 (protection), Art. 11 (business continuity), and Art. 17-19 (incident management). As an ECB-supervised bank, Santander's DORA compliance is subject to intensive scrutiny.
The Approach
DORA as Structural Fix
Art. 5-6 — Systematic vs. Reactive
DORA requires systematic risk management addressing structural causes of recurring outages — not reactive post-mortems fixing individual bugs without addressing architectural fragility.
Art. 24 — Testing That Finds Problems First
If testing passes but outages continue, the testing programme is insufficient — testing the wrong things at insufficient depth.
Art. 11 — Resilience Engineering
DORA should drive institutions beyond traditional BCP toward resilience engineering that prevents failures, not just recovers from them.
Art. 5(4) — Investment Rebalance
Management body resource allocation should rebalance technology investment toward resilience engineering rather than exclusively toward feature development.
The Results
From Chronic to Controlled
The Santander outage illustrates both the problem DORA was designed to solve and the challenge of solving it. The root causes are structural — aging infrastructure, complexity, insufficient testing, underinvestment in resilience. Structural improvement takes time but DORA establishes the destination.
Success is not eliminating outages but measurably reducing their frequency, duration, and impact while systematically learning from each incident to prevent recurrence.
Lessons Learned
- 1DORA Art. 5-6 requires systematic risk management addressing structural causes of recurring outages.
- 2DORA Art. 24 testing must find vulnerabilities before they cause production outages.
- 3DORA Art. 5(4) should drive investment rebalancing toward resilience engineering over feature development.
- 4Recurring outages demonstrate DORA requirements are minimum standards addressing demonstrated deficiencies.
- 5DORA Art. 11 should evolve from recovery planning toward resilience engineering that reduces outage frequency.
Disclaimer:This case study is based on anonymized data from real-world DORA compliance programmes. Names, specific figures, and identifying details have been changed to protect confidentiality. The outcomes described are specific to the institution's context and may not be directly replicable.
Facing similar challenges?
See how Valendir can help your institution achieve and maintain DORA compliance with deterministic workflows, immutable evidence, and continuous assurance.