Live / Digipost / Incident
Digipost: Problemer med BankID fører til problemer med signering og innlogging
Digipost · digipost.noMajor incidentResolved2026-10-13 02:49 UTC
Public — what happened
Summary
Digipost reported a major disruption in which problems with BankID, the third-party login and identification service, interfered with signing documents and logging in. The company began investigating the BankID issue at 10:36 UTC on 12 October 2026, noting it affected users trying to sign assignments. By 13:03 UTC Digipost said BankID had fixed its problems and users were able to sign again, though it kept watching its systems. The incident was marked resolved on 13 October 2026 at 02:49.
Affected
Posten Signering - Web
Timeline
- Started — 2026-10-12 10:36 UTC
- Identified — 2026-10-12 10:36 UTC
- Monitoring — 2026-10-12 13:03 UTC
- Resolved — 2026-10-13 02:49 UTC · 16h 13m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Digipost against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Digipost: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Digipost report →
More from Digipost
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.