Is Skribble down?

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.

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.

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.

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.

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