Skribble Outage History

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.

The issue with QES identifications has been resolved. Following our previous update, we continued to monitor the situation and have not received any further reports of issues from customers. We therefore consider this incident resolved. If you are still experiencing any issues, please contact our support team at [[email protected]](mailto:[email protected]).

A fix has been implemented by IONOS. This incident has been resolved.

The issue has been resolved. We temporarily switched to alternative DNS servers to restore normal service. We will continue to monitor the situation.

This incident has been resolved. The issue affecting the Skribble platform, caused by scheduled security maintenance at our infrastructure provider, has been fixed. If you still experience issues, please log out and log back in. We apologise for the inconvenience.

On August 25, scheduled infrastructure maintenance was performed on parts of our messaging infrastructure. While the maintenance itself completed successfully, some application components did not properly restore their connections afterward. As a result, certain operations on the Skribble platform, including signing and accessing signed documents, could fail with an error. The impact increased as traffic picked up the following morning. We identified the affected components and restored their connections, returning the platform to normal operation. We are reviewing our connection recovery mechanisms to ensure application components automatically and reliably reconnect after similar infrastructure maintenance in the future.

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.

This incident has been resolved.

The issue has been resolved, and our monitoring has confirmed that affected signers can now access documents as expected. **Root Cause** A recent update to our Identity and Access Management (IAM) system introduced changes that caused unexpected malfunctions in specific scenarios, primarily affecting signers without a Skribble account. We apologize for any inconvenience this may have caused and thank you for your patience while we resolved the issue.

SMS authentication for AES signing was unavailable for users with **non-Swiss mobile numbers** during the incident window. Our SMS authentication provider, **Tyntec**, experienced an issue that prevented SMS delivery to users with non-Swiss mobile numbers. The issue has been resolved, and SMS authentication is now functioning normally for all supported mobile numbers. **What you need to do** If you were unable to complete an AES signature during the affected time period, please retry the signing process. SMS authentication is now working as expected.

We experienced an issue affecting SSO logins this morning. Users attempting to sign in via their organization's identity provider were unable to complete the login redirect. The issue was identified following customer reports and internal testing. We resolved the problem within 30 minutes of processing the first complaint. The root cause was traced back to a regression introduced during a recent deployment. The fix has been applied and SSO logins are operating normally again. We apologize for the inconvenience and appreciate your patience.

The login issue affecting [skribble.de](http://skribble.de) has been resolved. All systems are now operational.