Scrive incident

NO BankID QES - partial outage

Major Resolved View vendor source →

Scrive experienced a major incident on September 3, 2026 affecting Norwegian BankID, lasting 2d 7h. The incident has been resolved; the full update timeline is below.

Started
Sep 03, 2026, 06:45 AM UTC
Resolved
Sep 05, 2026, 02:41 PM UTC
Duration
2d 7h
Detected by Pingoru
Sep 03, 2026, 06:45 AM UTC

Affected components

Norwegian BankID

Update timeline

  1. investigating Sep 03, 2026, 06:45 AM UTC

    We’re currently experiencing partial outage with NO BankID. Our team is currently working to restore normal performance levels. We apologize for any inconvenience. eSign and eID Hub users may be affected.

  2. investigating Sep 04, 2026, 06:56 AM UTC

    Our eID provider is working towards a resolution. We apologize for any inconvenience. eSign and eID Hub users may still be affected. Updates will follow.

  3. monitoring Sep 04, 2026, 09:47 AM UTC

    We are continuing to monitor the ongoing disruption affecting Norwegian BankID QES signing. BankID reports that while a full resolution is still in progress, their engineering team has identified a solution and is actively implementing a fix over the next two hours. Signing transactions may remain degraded or unavailable during this time. We are tracking BankID’s progress closely and will provide our next update as soon as new details emerge.

  4. monitoring Sep 04, 2026, 11:09 AM UTC

    We are seeing improvements in transaction success rates for Norwegian BankID QES signing. While the service is stabilizing, we are continuing to closely monitor performance to ensure it remains reliable before confirming that the issue is fully resolved. We will provide a final update once the service has returned to normal.

  5. monitoring Sep 04, 2026, 02:20 PM UTC

    Performance and delivery for Norwegian BankID QES signing have stabilized following the recent mitigation. Success rates have improved, and the service is currently operating as expected. We will continue to actively monitor system stability throughout the weekend to ensure ongoing reliability. We will provide further updates if new issues arise.

  6. resolved Sep 05, 2026, 02:41 PM UTC

    This incident has been resolved.