Is Skribble down?

We are cWe are currently experiencing an issue affecting our platform, making it temporarily unavailable. Our engineering team is actively investigating the root cause to restore service as quickly as possible. Currently investigating this incident.

Our cloud infrastructure provider is currently investigating failures affecting multiple Linux nodes. We are monitoring the situation and will provide updates as more information becomes available.

**Update:** We have identified the root cause as an update by our cloud infrastructure provider that caused multiple Linux nodes to fail. We are currently restoring the platform on new nodes. The platform remains unavailable at this time. We will provide another update as soon as the platform is restored.

Update: Our attempt to restore the platform on new nodes was unsuccessful due to the underlying storage issues within the Kubernetes cluster. Both of our infrastructure providers are actively working to resolve these issues. The platform remains unavailable at this time. \- \- We will provide another update as soon as we have further information.

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.

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.

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.

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.

We are currently investigating an ongoing issue affecting the IONOS managed service used by our German platform. We are in contact with the provider and are monitoring the situation closely. We will provide another update as soon as more information is available or the issue has been resolved. We apologize for any inconvenience this may cause.

IONOS is rolling back their changes. We are monitoring the progress.

This incident has been resolved.

We are currently investigating an issue where some signers receive an error message when attempting to access a document. Based on our current findings, the issue primarily affects signers **without a Skribble account**, while signers with an account appear to be largely unaffected. Our team is actively investigating the root cause and is already implementing potential fixes. We will provide another update as soon as more information becomes available.

We have identified the root cause of the issue and are actively working on a resolution. A potential fix has been implemented, and we are currently monitoring the system to verify that it resolves the issue. We will provide another update once we have confirmed the outcome.

We are no longer seeing any new occurrences of this issue following the implemented fix. We will continue to closely monitor the system to ensure the issue has been fully resolved and remains stable.

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.