Skribble AG - Issues with QES signing – Incident details

All systems operational

Show current status

Issues with QES signing

ResolvedPartial outage 30%15 hours

Affected

Internal Services

Degraded performance from 3:12 PM to 3:44 PM, Partial outage from 3:44 PM to 6:12 AM

skribble.com Services

Degraded performance from 3:12 PM to 3:44 PM, Partial outage from 3:44 PM to 6:12 AM

Skribble Platform CH

Degraded performance from 3:12 PM to 3:44 PM, Partial outage from 3:44 PM to 6:12 AM

  • ResolvedUTC

    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.

  • UpdateUTC

    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.

  • InvestigatingUTC

    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.