Skribble Outage History

Started Oct 14, 2026, 06:51 AM UTC· resolved Oct 14, 2026, 10:26 AM UTC

1. 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.

2. 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.

3. 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.

4. resolved Oct 15, 2026, 08:52 AM UTC

   A postmortrem report by Swisscom can be found here:

Read the full incident report →

Started Oct 06, 2026, 09:23 AM UTC· resolved Oct 06, 2026, 10:47 AM UTC

1. investigating Oct 06, 2026, 09:23 AM UTC

   Our identification partner for QES identifications has reported an issue affecting their services. As a result, users may experience errors or difficulties when completing an identification. If you encounter any issues, we recommend trying the identification again later. Our partner is investigating the issue, and we are closely monitoring the situation. We will provide an update as soon as more information becomes available.

2. monitoring Oct 06, 2026, 09:38 AM UTC

   Our identification partner has informed us that the previously reported issues **should now be resolved.** QES identifications should be working as expected again. We will continue to monitor the situation and provide a final update shortly. If you are still experiencing any issues, please contact our support team at [[email protected]](mailto:[email protected]).

3. resolved Oct 06, 2026, 10:47 AM UTC

   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]).

Read the full incident report →

Started Sep 29, 2026, 06:30 AM UTC· resolved Sep 29, 2026, 11:28 AM UTC

1. investigating Sep 29, 2026, 06:30 AM UTC

   We are currently investigating an issue in context with IONOS managed service used by our German platform. The German platform is currently unavailable. We a investigating. We apologize for any inconvenience this may cause.

2. investigating Sep 29, 2026, 07:21 AM UTC

   We are currently investigating this incident.

3. monitoring Sep 29, 2026, 08:42 AM UTC

   Although IONOS has not yet issued an all-clear, the system appears to be stabilizing again. We will keep monitoring this.

4. resolved Sep 29, 2026, 11:28 AM UTC

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

Read the full incident report →

Started Sep 24, 2026, 01:30 PM UTC· resolved Sep 24, 2026, 02:50 PM UTC

1. monitoring Sep 24, 2026, 01:30 PM UTC

   We are currently experiencing DNS service issues in our IONOS datacenter. The issue affects [skribble.de](http://skribble.de) and is primarily impacting signing with Swisscom TSP. We are monitoring the DNS issues and will provide updates as the situation develops.

2. resolved Sep 24, 2026, 02:50 PM UTC

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

Read the full incident report →

Started Sep 04, 2026, 06:21 AM UTC· resolved Sep 04, 2026, 09:36 AM UTC

1. investigating Sep 04, 2026, 06:21 AM UTC

   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.

2. identified Sep 04, 2026, 06:57 AM UTC

   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.

3. identified Sep 04, 2026, 07:26 AM UTC

   **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.

4. monitoring Sep 04, 2026, 08:26 AM UTC

   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.

5. resolved Sep 04, 2026, 09:36 AM UTC

   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.

Read the full incident report →

Started Aug 25, 2026, 08:00 PM UTC· resolved Aug 25, 2026, 08:00 PM UTC

1. resolved Aug 25, 2026, 08:00 PM UTC

   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.

Read the full incident report →

Started Aug 12, 2026, 03:12 PM UTC· resolved Aug 13, 2026, 06:12 AM UTC

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.

Read the full incident report →

Started Jul 28, 2026, 11:47 AM UTC· resolved Jul 28, 2026, 02:13 PM UTC

1. investigating Jul 28, 2026, 11:47 AM UTC

   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.

2. monitoring Jul 28, 2026, 02:02 PM UTC

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

3. resolved Jul 28, 2026, 02:13 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 08, 2026, 10:00 AM UTC· resolved Jul 08, 2026, 01:01 PM UTC

1. investigating Jul 08, 2026, 10:00 AM UTC

   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.

2. identified Jul 08, 2026, 12:05 PM UTC

   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.

3. monitoring Jul 08, 2026, 12:31 PM UTC

   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.

4. resolved Jul 08, 2026, 01:01 PM UTC

   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.

Read the full incident report →

Started Jul 02, 2026, 04:00 AM UTC· resolved Jul 03, 2026, 06:30 AM UTC

1. investigating Jul 02, 2026, 04:00 AM UTC

   We identified an issue affecting SMS authentication for AES signing with non-Swiss mobile numbers. Users with international mobile numbers may not have received SMS authentication codes and may have been unable to complete AES signatures.

2. resolved Jul 03, 2026, 06:30 AM UTC

   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.

Read the full incident report →

Started May 27, 2026, 07:04 AM UTC· resolved May 27, 2026, 07:04 AM UTC

1. resolved May 27, 2026, 06:30 AM UTC

   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.

Read the full incident report →

Started May 26, 2026, 06:21 AM UTC· resolved May 26, 2026, 07:28 AM UTC

1. investigating May 26, 2026, 06:21 AM UTC

   Users are currently unable to log in via [skribble.de](http://skribble.de). ([skribble.com](http://skribble.com) is not affected and works as expected.) We are investigating the issue and will provide updates as soon as possible.

2. resolved May 26, 2026, 07:28 AM UTC

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

Read the full incident report →

Started Apr 04, 2026, 09:48 AM UTC· resolved Apr 04, 2026, 09:48 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Feb 17, 2026, 09:00 PM UTC· resolved Feb 17, 2026, 09:00 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Feb 11, 2026, 09:19 AM UTC· resolved Feb 11, 2026, 09:19 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Dec 12, 2025, 09:34 AM UTC· resolved Dec 12, 2025, 09:34 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Dec 05, 2025, 07:56 AM UTC· resolved Dec 05, 2025, 07:56 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Dec 01, 2025, 04:26 PM UTC· resolved Dec 01, 2025, 04:26 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Nov 18, 2025, 11:35 AM UTC· resolved Nov 18, 2025, 11:35 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Nov 02, 2025, 10:07 AM UTC· resolved Nov 02, 2025, 10:07 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →