Skribble incident
QES and AES signing currently unavailable
Skribble experienced a minor incident on October 14, 2026 affecting skribble.com Services (Skribble API CH) and skribble.com Services (Skribble Platform CH) and 1 more component, lasting 3h 35m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 14, 2026, 06:51 AM UTC
Signatures with Qualified (QES) and Advanced (AES) quality fail at the final signing step. The cause is a disruption at our trust service provider, Swisscom. We've escalated it to them and are working with them to restore service. Simple electronic signatures (SES) are not affected. Open signature requests stay valid and can be signed once the service is back. No data has been lost. We'll post an update as soon as we know more.
- monitoring Oct 14, 2026, 07:55 AM UTC
QES and AES signatures are completing successfully again, and we no longer see any errors. We're keeping a close eye on the service with Swisscom to make sure it stays stable. If a signature failed during the disruption, please try again. Open signature requests stayed valid throughout. If you still have problems, please contact our support.
- resolved Oct 14, 2026, 10:26 AM UTC
The disruption at our trust service provider Swisscom is resolved. QES and AES signatures have been working normally again, and no further errors have occurred. If a signature failed during this period, please simply try again. All signature requests remained valid. We apologise for the inconvenience.
- resolved Oct 15, 2026, 08:52 AM UTC
A postmortrem report by Swisscom can be found here: