
FREDRIK VARFJELL/NTB/AFP via Getty Images
Norway’s BankID — the dominant electronic identification and contract-signing platform for roughly 4.2 million Norwegians — suffered the most prolonged service disruption in its two-decade history this week, with core signing services failing across two consecutive days and the company’s own communications director confirming on Thursday that no previous outage had lasted as long. The crisis froze property transactions worth potentially hundreds of millions of dollars, blocked contract executions across nearly every regulated industry, and cut citizens off from government digital services — all from a single technical failure at one vendor, DXC Technology, which now bears the distinction of having been involved in two separate multi-day BankID outages in less than five years. TheLocal.no reported the December 2021 precedent with DXC named as the supplier.
BankID’s Two-Day Failure — What Happened and When
The incident began in the early morning hours of Wednesday, September 3, when BankID’s production status monitors first flagged a complete outage — described as “100% impact” — across three interdependent services: BankID CSC Signing, the WYSIWYS (What You See Is What You Sign) document-signing interface, and the Qualified Timestamp service. The initial alert was logged at 07:11 CEST on September 3.
Engineers worked through Wednesday. By mid-afternoon, BankID Signing B2B and the Qualified Timestamp service were partially restored at 15:40 CEST Wednesday — but CSC Signing and WYSIWYS remained down. A fix was implemented and the services entered monitoring mode at 20:52 CEST, only for new problems to emerge overnight. By 22:18 CEST Wednesday, engineering teams confirmed they were still working to restore the remaining services.
By Thursday afternoon, BankID’s status page indicated resolution of signing services around 12:15 CEST (6:15 ET), with the company cautioning it would continue close monitoring through the weekend.
Hege Steinsland, communications director at Stø AS — the company that operates BankID — described the situation to Norwegian newspaper VG: “We have been working through the night, and the services were stable for a period, but now there are new problems again.” She also confirmed to VG that this was the longest service disruption BankID had experienced.
A precursor incident had struck BankID’s pre-production environment on September 2, resolving the same morning — suggesting underlying instability in the DXC-operated infrastructure before the production failure began.
Why a Signing Failure Is Different From a Login Failure
The technical services that failed during this outage are not interchangeable. Understanding what each does explains why a signing outage carries legal and financial consequences that an ordinary login failure does not.
CSC Signing refers to the Cloud Signature Consortium API standard, an international specification for remote cloud-based qualified electronic signatures under the EU’s eIDAS regulation. BankID’s signing infrastructure is built on this standard. When the CSC Signing service fails, it is not possible to create legally valid eIDAS-qualified electronic signatures from Norway — regardless of whether authentication is working. The inability to sign is not a convenience failure; it is a legal inability to execute binding contracts.
WYSIWYS stands for “What You See Is What You Sign,” a security property mandated by eIDAS requiring that signatories see precisely the document they are signing in a tamper-evident display. When the WYSIWYS interface fails, the signing workflow cannot proceed at all, even if the underlying signature system is operational. It is a separate failure mode with its own failure path.
Qualified Timestamps are eIDAS-regulated trust services that cryptographically prove when a document was signed. They are legally required for many regulated documents. Their failure means newly signed documents — during the window when this service was unavailable — lacked legally valid timestamps.
BankID is a Public Key Infrastructure system in which private cryptographic keys are held at the bank level, not on user devices, with the central authentication and signing orchestration operated by Stø AS through DXC Technology. This architecture means a failure in the central DXC-operated infrastructure propagates simultaneously to all 4.2 million users. There is no device-level fallback, no cached credential that allows signing to continue locally, and no secondary infrastructure a business can route around. When the central layer fails, the entire system fails.
Real-World Damage: Frozen Transactions, Blocked Funds
The human cost of the outage was most visible in the Norwegian real estate sector, where BankID’s signing technology underpins virtually every property transaction.
Terje Tinholt, a partner at Tinholt Eiendomsmegling, told VG his firm alone had between 50 and 60 transactions that could not complete. “People are waiting on enormous sums of money, but cannot receive them. Everything we do goes through electronic systems. This is a complete crisis,” Tinholt said.
The ripple extended far beyond real estate. Corporate contract execution, mortgage disbursements, healthcare consent forms, and tax filings all flow through BankID’s signing infrastructure. The Norwegian Tax Administration reported disruptions. Access to Helsenorge, the national health portal, was affected. Vipps — Norway’s dominant mobile payment application, with more than four million users — depends on BankID authentication for its core payment workflows.
Unlike a standard login failure — where users can defer access until services restore — a signing outage introduces potential legal and financial liability when statutory deadlines are missed or property settlements delayed. Norwegian property law requires BankID-qualified electronic signatures for deed registration in the Grunnboken (land register); a delayed signature is not merely inconvenient but can invalidate a transaction’s legal completion date.
A Supplier Pattern Worth Scrutinizing
The September 2026 crisis is not DXC Technology’s first appearance in a BankID outage of this kind.
BankID switched its infrastructure operations from Nets (now Nexi) to DXC in October 2021 — the same migration that the company had pre-announced with assurances of smooth transition. Within weeks of that migration, in December 2021, BankID users faced a third consecutive day of disruption — once again with DXC as the named technical supplier. Øyvind Brekke, then speaking for BankID, said at the time: “We are having ongoing crisis meetings with the suppliers and hope it will help find out what the problem is.” He also acknowledged: “At present, we do not know exactly where the problem lies. It is a complex service with very high-security requirements and long value chains.” That December 2021 acknowledgment carried essentially identical language to what Stø AS communicated in September 2026.
Now, fewer than five years later, the same supplier is involved in Norway’s longest BankID disruption on record — and Stø AS has once again confirmed it does not know the underlying cause. The company’s September 4 update contained nearly identical language to 2021: engineering teams implementing fixes, monitoring results, and new problems emerging overnight.
This pattern raises a question that Norwegian financial regulators are now positioned — and legally obligated — to answer.
Does “Is It DORA Compliant?” Now Apply to BankID?
Norway’s national DORA Act (formally: Lov om digital operasjonell motstandsdyktighet i finanssektoren) took effect July 1, 2025, with Finanstilsynet — the Norwegian Financial Supervisory Authority — as the designated supervisory body.
DORA does not merely require financial entities to be resilient; it requires them to demonstrate operational resilience through documented ICT risk management, mandatory third-party supplier oversight, resilience testing, and — critically — incident reporting. A significant incident affecting critical financial infrastructure triggers a 24-hour early warning obligation to Finanstilsynet, a full notification within 72 hours, and a final report within one month.
A 30-plus-hour outage of a platform serving 4.2 million users, classified as critical national financial infrastructure and operated through a single third-party ICT supplier, almost certainly crosses the threshold for mandatory incident notification. What Finanstilsynet received, when they received it, and what supervisory action follows — if any — will determine whether Norway’s DORA implementation has real enforcement teeth or remains a document exercise.
Norway also implemented the Digital Security Act (Digitalsikkerhetsloven) on October 1, 2025, which carries obligations from the EU’s original NIS Directive, confirmed by the Norwegian government, applicable to providers of essential services including banking and financial market infrastructure. Both legal frameworks apply to Stø AS. The September 2026 outage is the first major test of whether regulators will enforce them.
How Does an Entire Nation End Up with One Digital Signing Rail?
BankID’s dominance in Norway is the result of deliberate design. The system was developed beginning in the early 2000s as a collaboration between the Norwegian Financial Services Association and the Norwegian Savings Banks Association — now merged as Finance Norway (Finans Norge) — with the explicit goal of creating a single, bank-backed electronic identification standard accepted across the economy. That goal was achieved: today BankID is issued through more than 90 banks, accepted by roughly 9,000 merchants and public services, and used by more than 75% of Norway’s adult population.
What the designers of that system did not build — or did not require — was a viable fallback. Risk professionals call the result “concentration risk” or “IdP concentration risk”: the exposure an organization faces when all authentication and signing decisions depend on a single platform. When that platform fails, the blast radius equals the total count of dependent services — because every dependent service shares the same failure domain.
“We do not accept single points of failure in our power grids, our databases, or our networks,” researchers at the RSA Conference concluded in a widely cited analysis of identity infrastructure resilience. “It is time we apply the same standard to our identity systems.”
Norway’s BankID crisis is a live demonstration of what happens when a country has not applied that standard.
Norway’s Broader Pattern of Digital Infrastructure Fragility
The BankID signing crisis did not occur in isolation. It arrived in the middle of a summer defined by Norwegian digital infrastructure failures.
In late June 2026, ID-porten — Norway’s mandatory government single sign-on gateway — was knocked offline by a DDoS attack targeting Vivicta, one of its infrastructure suppliers, leaving citizens unable to access tax records, health services, and dozens of other public platforms. That attack was followed by a second incident on August 3, and a third — described by Digdir press officer Are Kvistad as “two to three times larger than what we experienced last time” — beginning on August 24. Pro-Russian hacker group Server Killers took credit for the campaign, according to reporting by the Associated Press. The Bleeping Computer also confirmed the scale of the attacks against Digdir’s infrastructure.
The BankID September outage differs in character from those attacks — there is no indication it involved an external threat actor — but the underlying structural vulnerability is identical: a society that has consolidated its critical authentication and signing infrastructure into a small number of centralized platforms has created catastrophic single points of failure. The ID-porten campaign exploited that architecture through a DDoS; the BankID crisis exposed it through a supplier technical failure. The result for citizens and businesses was the same.
That pattern has a direct regulatory implication. DORA specifically requires financial entities to map which processes would fail if authentication infrastructure went down, and to have agreed manual fallback procedures in place before a failure occurs. The BankID outage revealed that no such fallback exists for the tens of thousands of property transactions, corporate contracts, and regulated documents that depend on BankID signing weekly.
What Business Operators Can Do Right Now
If you operate in Norway and depend on BankID signing for critical business processes:
Contact your legal or settlement counsel immediately about whether any missed deadlines during the September 3–4 window create liability or require an extension. Norwegian property law and contract law both have provisions for force majeure events, but these must be invoked proactively.Determine which of your regulated documents require a Qualified Electronic Signature (QES) versus an Advanced Electronic Signature (AdES). Alternative eID providers such as Buypass ID and Commfides are also registered with the Norwegian Communications Authority and can in some cases substitute for BankID.Review your own supplier agreements with BankID/Stø AS to determine what SLA protections exist, what remedy provisions apply to a 30-plus-hour outage, and whether those provisions have been triggered.For organizations subject to DORA, document your own third-party ICT risk exposure: map which of your services would fail if BankID is unavailable, and identify or plan the fallback that DORA requires you to have.Frequently Asked QuestionsWhat caused Norway’s BankID outage in September 2026?
Stø AS and its technical supplier DXC Technology had not publicly disclosed the root cause of the failure as of Thursday afternoon, September 4. The outage affected BankID’s CSC Signing and WYSIWYS services — the components used for legally valid electronic document signing — beginning at 07:11 CEST on September 3, with partial restoration achieved on September 4 around 12:15 CEST. The company described the underlying issue only as a “complex service with very high-security requirements and long value chains,” the same language it used in December 2021, the last time DXC was involved in a major BankID outage. The Idura status page tracked the full incident timeline.
Why did a BankID signing outage freeze property sales but not just logins?
BankID’s signing services are built on the Cloud Signature Consortium API standard for eIDAS-qualified electronic signatures. When CSC Signing fails, it is legally impossible to create a valid electronic signature under EU and Norwegian law — not just technically difficult. Norwegian property transfers require BankID-qualified signatures for deed registration, meaning a delay in signing is a delay in legal ownership transfer. The WYSIWYS (What You See Is What You Sign) interface is a separate eIDAS-mandated security layer; its failure independently blocks the signing workflow even when authentication is working.
Has DXC Technology been involved in BankID outages before?
Yes. BankID switched its infrastructure operations from Nets to DXC Technology in October 2021. Within weeks of that transition, in December 2021, BankID users experienced a three-day outage with DXC named as the technical supplier — and BankID acknowledged at the time it did not know the cause. The September 2026 outage, also involving DXC and also without a disclosed root cause, is the second multi-day incident since that migration. Norwegian DORA regulations require Finanstilsynet to oversee third-party ICT supplier risk; whether that oversight has evaluated this specific supplier dependency is now a live regulatory question.
Does the BankID outage violate Norway’s DORA or cybersecurity law?
Norway’s national DORA Act (in force since July 1, 2025) requires financial entities to maintain operational resilience and manage third-party ICT risk, and mandates incident reporting to Finanstilsynet within 24 hours for significant incidents affecting critical financial infrastructure. A 30-plus-hour outage of a platform used by 4.2 million people likely meets the threshold for mandatory notification. Norway’s Digital Security Act (Digitalsikkerhetsloven, in force since October 1, 2025) carries similar obligations under the original EU NIS Directive for providers of essential services including banking infrastructure. Whether Stø AS complied with these reporting obligations, and whether Finanstilsynet takes supervisory action, has not been publicly confirmed.