Skribble incident

Issues with QES signing

Minor Resolved

Skribble experienced a minor incident on August 12, 2026 affecting skribble.com Services (Skribble Platform CH), lasting 15h. The incident has been resolved; the full update timeline is below.

Started
Aug 12, 2026, 03:12 PM UTC
Resolved
Aug 13, 2026, 06:12 AM UTC
Duration
15h
Detected by Pingoru
Aug 12, 2026, 03:12 PM UTC

Affected components

skribble.com Services (Skribble Platform CH)

Update timeline

  1. investigating Aug 12, 2026, 03:12 PM UTC

    We are currently experiencing issues with the qualified electronic signature (QES). Some users may incorrectly be asked to upgrade their signature quality or repeat their identification, even though their identification is valid — **no re-identification is necessary.** Signing with other signature qualities (SES/AES) is not affected. The issue is caused by a disruption at one of our partners; we are in close contact with them to resolve it as quickly as possible. We will provide an update as soon as the service is fully restored.

  2. investigating Aug 12, 2026, 03:44 PM UTC

    We are continuing to work with our partner on resolving this issue. Clarification on scope: the disruption affects **both** qualified (QES) and advanced (AES) electronic signatures. Affected users may incorrectly be asked to increase their signature quality, repeat their identification, or purchase an identification — even though their identification is valid. No re-identification or purchase is necessary, and already completed signatures remain fully valid. Signing with simple electronic signatures (SES) is not affected. We will provide a further update as soon as the service is restored.

  3. resolved Aug 13, 2026, 06:12 AM UTC

    The issue affecting qualified (QES) and advanced (AES) electronic signatures has been resolved, and signing is operating normally again. Users with a valid identification can now sign as expected without being incorrectly prompted to increase their signature quality, repeat their identification, or purchase an identification. No action is required from affected users. All signatures completed during the incident remain fully valid. We apologize for the inconvenience and thank you for your patience while we worked to resolve the issue.