Yousign Outage History

Started Oct 16, 2026, 12:22 PM UTC· resolved Oct 16, 2026, 12:40 PM UTC

1. investigating Oct 16, 2026, 12:22 PM UTC

   Since 14:03 CEST (12:03 UTC), we have been experiencing delays in the processing of simple and advanced electronic seals. All seal requests are successfully accepted by our application and API, and no request has been lost. However, sealed documents are currently made available with a delay. The backlog is already decreasing and processing times are returning to normal. We are closely monitoring the situation and will share an update once the delay is fully absorbed. We apologize for the inconvenience.

2. monitoring Oct 16, 2026, 12:27 PM UTC

   Since 14:19 CEST (12:19 UTC), processing times for simple and advanced electronic seals are back to normal, and the backlog has been fully cleared. All sealed documents that were delayed are now available. To absorb the peak in demand that caused these delays, our teams have increased the processing capacity of the system. We are keeping this degradation in monitoring while our technical teams confirm that processing is fully stabilized. We will post a final update once this is confirmed. Thank you for your patience.

3. resolved Oct 16, 2026, 12:40 PM UTC

   This incident is fully resolved. Our teams have confirmed that electronic seal processing is stable and that our processing capacity is aligned with current demand. To summarize, between 14:03 and 14:19 CEST, a peak in demand caused delays in the delivery of documents sealed with simple and advanced electronic seals. All requests were accepted and processed, and no action is required on your side. We have increased our processing capacity to prevent this from happening again. We apologize for the inconvenience and thank you for your patience.

Read the full incident report →

Started Oct 16, 2026, 09:46 AM UTC· resolved Oct 16, 2026, 10:11 AM UTC

1. investigating Oct 16, 2026, 09:46 AM UTC

   Since 11:20 CEST (09:20 UTC), our third-party identity verification provider has been experiencing an incident affecting its services. The provider is aware of the issue and is actively working on a resolution. Our application and API remain fully available. However, the following features are currently impacted: - Identity verification during Advanced Electronic Signature (AES) flows - Identity document verification through Verify Signers may be unable to complete identity verification steps until the provider’s service is restored. All other signature levels and features are working normally. We are closely monitoring the situation with our provider and will share an update as soon as we have more information, or within the next 60 minutes at the latest. We apologize for the inconvenience.

2. monitoring Oct 16, 2026, 10:02 AM UTC

   Our identity verification provider resolved the incident at 11:53 CEST (09:53 UTC). All new identity verification requests for Advanced Electronic Signature (AES) and Verify are now processed successfully. We are currently processing the requests that were pending during the incident, and we expect the situation to be fully resolved within the next few minutes. We will post a final update once all pending requests have been processed. Thank you for your patience.

3. resolved Oct 16, 2026, 10:11 AM UTC

   This incident is fully resolved. Since 12:11 CEST (10:11 UTC), all identity verification services for Advanced Electronic Signature (AES) and Verify are back to normal. All requests that were pending during the incident have been successfully processed. No action is required on your side. To summarize, between 11:20 and 11:53 CEST, our third-party identity verification provider experienced an outage that prevented identity verification steps from completing. Our application and API remained available throughout the incident. We apologize for the inconvenience and thank you for your patience.

Read the full incident report →

Started Oct 07, 2026, 10:10 AM UTC· resolved Oct 07, 2026, 03:50 PM UTC

1. monitoring Oct 07, 2026, 10:10 AM UTC

   Between 11:24 CEST and 11:35 CEST today, the Yousign v3 product experienced degraded performance. During this period: Some requests to the public API returned HTTP 500 errors. The web application behaved inconsistently, including issues displaying PDF documents and downloading audit trails. Service has been operating normally since 11:35 CEST. Our teams are actively investigating to identify the root cause, and we are closely monitoring the platform. If an API call failed during this window, we recommend retrying it. We will share an update as soon as more information is available. We apologize for any inconvenience this may have caused.

2. identified Oct 07, 2026, 12:50 PM UTC

   Since 14:42 CEST, we are once again experiencing degraded performance on the Yousign v3 product. Users may encounter HTTP 500 errors on the public API, as well as inconsistent behavior in the web application, including issues displaying PDF documents and downloading audit trails. We have confirmed that this degradation originates from one of our infrastructure providers. We are working closely with them to restore normal service, and our teams are continuing their investigation in parallel. We will provide a new update as soon as we have more information.

3. monitoring Oct 07, 2026, 01:26 PM UTC

   Since 15:19 CEST, all Yousign v3 services have been operating normally. This degradation was caused by an outage at one of our infrastructure providers. The impact was limited to certain operations on the public API and the web application, between 14:42 and 15:19 CEST, as well as during the earlier occurrence between 11:24 and 11:35 CEST. Our teams are now conducting a detailed analysis to precisely identify which features were affected. We will share additional information if needed. If an operation failed during these periods, we recommend retrying it. We apologize for the inconvenience caused and thank you for your patience.

4. resolved Oct 07, 2026, 03:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 02, 2026, 12:52 PM UTC· resolved Oct 04, 2026, 02:41 PM UTC

1. investigating Oct 02, 2026, 02:59 PM UTC

   Hello, The provider Orange Telecom is experiencing network routing issues. This is why some users connected through the Orange network (including Sosh) may experience slowness or errors on Yousign, mainly when uploading documents, saving changes or signing. Users on other networks are not affected. In the meantime, affected users can try another network, for example a mobile connection from a different operator. We will keep you informed as soon as this issue is resolved. In case of questions you can contact us at : [email protected]

2. identified Oct 02, 2026, 03:00 PM UTC

   The issue has been identified and a fix is being implemented.

3. resolved Oct 04, 2026, 10:21 AM UTC

   This incident has been resolved. Service has been operating normally since October 2 at 16:41 CEST. Between 14:52 and 16:41 CEST, some users connecting through the Orange network may have experienced slowness or difficulty accessing our services. The cause was a network interconnection issue between Orange and our hosting provider, which has now been fixed. No data was affected and no action is required on your side. We apologize for the inconvenience. All details are available here: https://network.status-ovhcloud.com/incidents/jqxcrgr138b4

Read the full incident report →

Started Sep 14, 2026, 10:08 AM UTC· resolved Sep 14, 2026, 11:50 AM UTC

1. investigating Sep 14, 2026, 10:08 AM UTC

   We're actually experiencing a slowdown of processing time for Advanced Electronic Signature identity verification and standalone Identity Verification service. We are actively working with our Identity Verification provider to understand the root cause and restore service as soon as possible.

2. identified Sep 14, 2026, 10:42 AM UTC

   Our identity verification provider has confirmed an issue at their side leading to instabilities. Although some identity verification requests are successful, the majority is either failing (for AES) or stuck in a pending status. We are actively monitoring the situation and communicate directly with our provider to bring the situation back to normal as soon as possible.

3. monitoring Sep 14, 2026, 11:31 AM UTC

   Our provider has stabilised their systems and we are now observing a gradual return to the nominal situation. We are still actively monitoring.

4. resolved Sep 14, 2026, 11:50 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 04, 2026, 12:30 PM UTC· resolved Sep 04, 2026, 09:06 PM UTC

1. investigating Sep 04, 2026, 12:30 PM UTC

   Some emails sent to Microsoft-hosted addresses (Outlook, Hotmail, Live and Microsoft 365) are arriving late or not at all. We were alerted by customers at 11:30 CEST, and the number of affected messages rose again after midday. Our own delivery tracking shows that every email is still being accepted by our sending providers, so the problem appears to occur after that hand-off. We are investigating with them to confirm the cause. Emails to all other providers are unaffected. No action is required on your side. We will post a new update as soon as we know more, and we are sorry for the disruption this is causing.

2. identified Sep 04, 2026, 12:43 PM UTC

   Update: This incident is on Microsoft's side, not ours. Our providers have confirmed a global Microsoft incident on inbound mail, which Microsoft has not published on its own status page. Our emails leave our systems and are accepted by our sending providers as usual, then stop at Microsoft. Since this morning, none of our email notifications reach business mailboxes hosted by Microsoft (Microsoft 365 and Exchange Online). Personal addresses such as outlook.com, hotmail.com and live.com are not affected, and neither is any other provider. Nothing we can change on our side will deliver these emails, so we cannot fix this incident or commit to a resolution time. We are tracking the fix with our providers, who are in direct contact with Microsoft. We will tell you whether the emails held since this morning are delivered on recovery or need to be sent again. Next update within the hour.

3. monitoring Sep 04, 2026, 03:14 PM UTC

   Microsoft has resolved its incident. Emails to Microsoft business mailboxes are being accepted again, so new notifications go through normally. The emails held up during the incident are still being sent out by our provider, which reports around 40% of them left to deliver. Until that backlog is cleared, recipients may still receive notifications with a delay. Nothing is lost, and you do not need to send anything again. How fast that backlog drains depends on our provider and on the rate Microsoft accepts, and is not something we control any more than the incident itself was. Next update once the backlog is fully delivered.

4. resolved Sep 04, 2026, 09:06 PM UTC

   Resolved. The backlog is fully delivered: every email held up during the incident has now been sent, and delivery to Microsoft business mailboxes has been back to normal since Microsoft closed its incident. What happened: from around 11:30 CEST, a global Microsoft incident on inbound mail stopped our notifications from reaching business mailboxes hosted by Microsoft 365 and Exchange Online. Personal addresses such as outlook.com, hotmail.com and live.com were never affected, and no other email provider was involved. Our systems kept sending normally throughout, and the messages were queued by our provider rather than lost. Once Microsoft restored service, that queue was flushed over the following hours, which is why some notifications arrived late this afternoon and this evening. The cause and the fix were both on Microsoft's side. What we can improve is how quickly we detect a blockage at a single provider and tell you about it, and we are working on that. Thank you for your patience, and sorry for the disruption this caused to your day.

Read the full incident report →

Started Sep 02, 2026, 02:28 PM UTC· resolved Sep 02, 2026, 03:19 PM UTC

1. investigating Sep 02, 2026, 02:28 PM UTC

   We are currently experiencing a degradation of the Qualified Electronic Signature (QES) service. Since 15:40 (CEST), some QES signature attempts are failing intermittently (during the identification part of the flow). The failures are random: when an error occurs, refreshing the page and retrying usually allows the signature to complete. A similar degradation was also observed earlier today, between 14:50 and 15:05. Signers who already have a wallet are not impacted: their signatures are working normally. Only signers going through the identity verification flow to obtain a new wallet may encounter these errors. We are in contact with our identity provider to resolve the issue and stabilize the service. We will share a new update as soon as we have more information and a clearer view of the impact. We sincerely apologize for the inconvenience and thank you for your patience and understanding.

2. monitoring Sep 02, 2026, 02:40 PM UTC

   Quick update on the QES degradation reported earlier today. Since 16:27 (CEST), we have not observed any further errors, and QES signatures are completing normally. We are currently confirming with our identity provider that the root cause has been definitively resolved. We will keep monitoring the service closely and will send a final update once we have this confirmation. Thank you for your patience and understanding.

3. resolved Sep 02, 2026, 03:19 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 31, 2026, 07:30 AM UTC· resolved Sep 01, 2026, 06:08 PM UTC

1. identified Aug 31, 2026, 09:42 AM UTC

   Dear users, One of our identity verification providers is currently facing technical difficulties. As a consequence, the following flows are impacted across our products: Advanced Electronic Signature: APP v3 signers might encounter long identification processing times, and a minor fraction of signers might also encounter errors when trying to perform an identification Verify Identity Verification: all API identity verification requests are rightly recorded and pending at our side and will be processed once the provider comes back online We are actively working with the provided to provide a swift recovery of our services, and will keep you updated along the process. We apologize for any inconvenience this may cause and appreciate your understanding as we work to enhance our service. For any questions or assistance, contact us at [email protected].

2. monitoring Aug 31, 2026, 10:03 AM UTC

   Our provider has restored their services and we are now closely monitoring the situation as we process the backlog of pending verifications: Advanced Electronic Signature: signers who attempted to perform identity verifications during the provider outage might still encounter errors in their sign flow. We are actively working towards normalising their situation. Other signers starting the flow now should not encounter any error anymore Verify Identity Verification: all requests should now be successfully processed according to standard processing times (a few seconds per request) We are monitoring and will keep you updated.

3. monitoring Aug 31, 2026, 10:55 AM UTC

   We confirm that the identification services are now fully back online, with some latency due to verification backlogs. This latency is improving gradually and we are continuing to monitor it. Advanced Electronic Signature signers who attempted to identify during the provider outage window should now retry their identification process successfully. The failed identification attempt made during the outage will not be accounted for in the billing / consumption data.

4. monitoring Aug 31, 2026, 01:28 PM UTC

   As our provider is scaling their operations to absorb the backlog of verifications, the Verify Identity Verification services are still impacted by a significant latency. We are closely working with the provider to ensure smooth restoration of services. Advanced Electronic Signature is not impacted.

5. monitoring Aug 31, 2026, 06:30 PM UTC

   We continue to observe latency on Identity Verification services. Our identity verification provider has fully mobilised their teams to absorb the backlog of pending verifications during the end-of-day and night period. As the volume of incoming requests gradually decreases, we expect their system to return to standard processing times overnight. No data will be lost: all identity verification requests submitted during this period are safely recorded on our side and will be processed, no action is required from you, and no request needs to be resubmitted. Advanced Electronic Signature is not impacted at this stage. We are continuously monitoring the situation and will provide a further update should anything change. Next update expected tomorrow morning, or earlier if the situation evolves. We apologize for the inconvenience. For any question, contact us at [email protected].

6. monitoring Sep 01, 2026, 06:00 AM UTC

   Our provider has identified the root cause of their system instabilities, linked to their orchestrator layer for verification services. They have fully stabilised their systems during the night, meaning Identity Verification processing times are now back to their standard duration of a few seconds. We are now gradually working through the backlog of pending verifications and expect them all to be processed during the morning hours. We are continuing to monitor the situation.

7. monitoring Sep 01, 2026, 08:44 AM UTC

   After consuming a significant share of pending verifications, our provider is again facing instabilities. Advanced Electronic Signature (AES) and Verify Identity Verification services are in a pending state as a consequence: AES signers are facing identification slowdowns or errors Identity Verification requests are pending and will be processed once our provider is up again We are monitoring the situation and will keep you updated.

8. monitoring Sep 01, 2026, 12:37 PM UTC

   We have held an in-depth exchange with our provider, which enabled us to locate the exact root cause of their scaling issue with a path to resolution identified. Advanced Electronic Signature is fully operational. Identify Verification is now also operational, while we still process the backlog of pending verifications in the coming hours.

9. resolved Sep 01, 2026, 06:08 PM UTC

   All Identity Verification services are now fully operational, and we have implemented additional measures to enhance service stability based on insights on our provider infrastructure. We are now closing this incident, and sincerely apologise for any inconvenience caused.

Read the full incident report →

Started Aug 13, 2026, 03:22 PM UTC· resolved Aug 13, 2026, 04:05 PM UTC

1. investigating Aug 13, 2026, 03:22 PM UTC

   Since 17:11 (CEST), we have been observing a degradation of our services, which may result in slowness or intermittent errors when using Product v2 and v3. Our technical teams are engaged and are currently assessing the precise scope and extent of the impact. An update will be published as soon as more information is available. Thank you for your patience.

2. investigating Aug 13, 2026, 03:28 PM UTC

   Since 17:11 (CEST), we have been observing a degradation of our services affecting Advanced (AES) and Qualified (QES) electronic signatures. Current impact: Advanced electronic signature (AES): signers can complete the signing flow, but signature finalisation is delayed. Documents will be finalised once the service is restored. Qualified electronic signature (QES): the signing flow is currently unavailable, and signers are unable to complete their signature. All other operations on the platform, including Simple electronic signature (SES), are operating normally. Our technical teams are actively working on a resolution. An update will be published as soon as more information is available. Thank you for your patience.

3. investigating Aug 13, 2026, 03:57 PM UTC

   As of 17:53 (CEST), the situation is stabilised. Both Advanced (AES) and Qualified (QES) signature flows are functional again, and signers are able to complete their signatures normally. We are currently processing the remaining signatures that were pending during the incident. This backlog should be fully cleared within the next few minutes. All other operations on the platform remain unaffected. We will continue to monitor the situation closely and will confirm full resolution shortly. Thank you for your patience.

4. resolved Aug 13, 2026, 04:05 PM UTC

   As of 18:05 (CEST), this incident is resolved. All pending Advanced (AES) signatures have been processed, and the signature delay has been fully cleared. Both Advanced (AES) and Qualified (QES) signature flows are operating normally, along with all other operations on the platform. We apologise for the inconvenience caused and thank you for your patience.

Read the full incident report →

Started Jul 24, 2026, 11:29 AM UTC· resolved Jul 25, 2026, 10:53 AM UTC

1. monitoring Jul 24, 2026, 11:29 AM UTC

   We're currently experiencing delays on Qualified eSignature (QES). These delays originate from one of our identity verification providers, which is currently experiencing elevated response times. As a result, identity verification and QES signature completion may take longer than usual. All other levels of signature (SES, AES) are not affected. We sincerely apologize for the inconvenience. Our teams are fully mobilized to monitor the situation and restore normal service as quickly as possible. We will provide updates here as soon as possible.

2. monitoring Jul 24, 2026, 12:03 PM UTC

   We are continuing to monitor for any further issues.

3. resolved Jul 25, 2026, 10:53 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 17, 2026, 08:46 AM UTC· resolved Jul 17, 2026, 02:03 PM UTC

1. investigating Jul 17, 2026, 08:46 AM UTC

   We're currently experiencing delays in the processing of some QES eSignature requests. Signatures are still being properly handled. Wallet creation and signature flow are functionals but signed documents cannot be retrieved yet. All other levels of signature are not affected. We sincerely apologize for the inconvenience. Our teams are fully mobilized to identify the root cause and implement a solution as quickly as possible.

2. identified Jul 17, 2026, 09:12 AM UTC

   One of our providers is experiencing an outage. We apologize for the inconvenience and will provide updates as soon as possible.

3. monitoring Jul 17, 2026, 09:25 AM UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring Jul 17, 2026, 09:26 AM UTC

   We are continuing to monitor for any further issues.

5. identified Jul 17, 2026, 09:32 AM UTC

   The issue has been identified and a fix is being implemented.

6. identified Jul 17, 2026, 09:44 AM UTC

   We are continuing to work on a fix for this issue.

7. monitoring Jul 17, 2026, 09:55 AM UTC

   A fix has been implemented and we are monitoring the results.

8. resolved Jul 17, 2026, 02:03 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 15, 2026, 07:25 PM UTC· resolved Jul 15, 2026, 07:45 PM UTC

1. investigating Jul 15, 2026, 07:25 PM UTC

   Some customers may be experiencing an issue with our service. Our engineers are working to identify and resolve this as fast as possible. We will update you again shortly here. If you have urgent questions, please contact our support team by sending an email to [email protected].

2. identified Jul 15, 2026, 07:34 PM UTC

   The issues has been identified. Our team is working on it.

3. resolved Jul 15, 2026, 07:45 PM UTC

   Our infrastructure provider performed an update on our low level infrastructure that was supposed to be without impact. The update is now finished and all services are back to normal. Sorry for the service degradation that may have happened during this time frame.

Read the full incident report →

Started Jul 05, 2026, 02:54 AM UTC· resolved Jul 05, 2026, 03:43 AM UTC

1. investigating Jul 05, 2026, 02:54 AM UTC

   Since 04:24 (CEST), our customers may experience HTTP 500 errors on the Public API and intermittent instabilities on the Yousign application. Our engineering teams are currently investigating the root cause. We will provide an update as soon as we have more information. We apologize for the inconvenience.

2. investigating Jul 05, 2026, 02:55 AM UTC

   We are continuing to investigate this issue.

3. investigating Jul 05, 2026, 03:20 AM UTC

   We are continuing to investigate this issue.

4. monitoring Jul 05, 2026, 03:22 AM UTC

   Since 04:24 (CEST), our customers may experience HTTP 500 errors on the Public API and intermittent instabilities on the Yousign application. Our engineering teams are currently investigating the root cause. We will provide an update as soon as we have more information. We apologize for the inconvenience.

5. resolved Jul 05, 2026, 03:43 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 30, 2026, 11:51 AM UTC· resolved Jun 30, 2026, 12:08 PM UTC

1. investigating Jun 30, 2026, 11:51 AM UTC

   Since 13:32 (CET), some signature and eSeal requests are experiencing increased processing times. Requests are not lost and continue to complete, though they may take longer than usual to finalize. All other services are operating normally. Our engineering teams have identified the issue and are actively working to reduce these delays. We will provide an update as soon as the situation improves. We apologize for any inconvenience.

2. identified Jun 30, 2026, 12:06 PM UTC

   Update: Since 14:00 (CET), processing times for signature and eSeal requests have started to recover. Delays are gradually decreasing and requests continue to complete normally. All other services remain unaffected. Our teams continue to monitor the situation closely. We will confirm once processing times have fully returned to normal. Thank you for your patience.

3. resolved Jun 30, 2026, 12:08 PM UTC

   Resolved: As of 14:07 (CET), processing times for signature and eSeal requests have fully returned to normal. All requests are completing as expected. This incident only affected Simple (SES) and Advanced (AES) levels. Qualified Electronic Signature (QES) and Qualified Electronic Seal (QES/qSeal) were not affected. This incident is now resolved. All services are operating normally. Thank you for your patience throughout this incident.

Read the full incident report →

Started Jun 29, 2026, 09:10 AM UTC· resolved Jun 29, 2026, 01:07 PM UTC

1. investigating Jun 29, 2026, 09:10 AM UTC

   Since 11:00 AM (CET), we are observing slowdowns as well as intermittent 500 errors affecting the web application and the API on version 3. Our engineering teams are engaged and currently investigating the root cause in order to restore normal operation as quickly as possible. Impact: some requests may fail or return degraded response times. Retrying the request is generally sufficient to succeed.

2. monitoring Jun 29, 2026, 09:15 AM UTC

   Since 11:07 AM (CET), the situation has stabilized: the slowdowns and intermittent 500 errors observed earlier are no longer occurring. The web application and the API are operating normally again. Our teams are maintaining active monitoring to confirm the return to normal operation and to prevent any recurrence.

3. identified Jun 29, 2026, 09:54 AM UTC

   [Investigating] New degradation on the App and API (v3) Since 11:46 AM (CET), we are observing a new degradation, with a return of slowdowns and intermittent 500 errors on the web application and the API on version 3. Our engineering teams are engaged again and actively investigating in order to identify the cause and restore normal operation as quickly as possible. Impact: some requests may fail or return degraded response times. Retrying the request may allow it to succeed. We apologize for any inconvenience caused.

4. monitoring Jun 29, 2026, 10:15 AM UTC

   Since 12:08 PM (CET), the situation is stable again: the slowdowns and intermittent 500 errors are no longer occurring. The web application and the API are operating normally. Our teams are continuing the investigation to identify the root cause and prevent any further recurrence. Active monitoring remains in place.

5. resolved Jun 29, 2026, 01:07 PM UTC

   [Resolved] Service back to normal on the App and API (v3) The incident that caused slowdowns and intermittent 500 errors on the web application and the API (v3) this morning is now resolved. Our teams performed an action on one of our infrastructure clusters, which was relocated. Since this intervention, the situation has been fully stable: everything has been operating normally since 12:08 PM (CET). We are continuing the analysis with our infrastructure provider to identify the cause of the transient saturation of this cluster and to put in place the measures needed to prevent any recurrence. We thank you for your patience and apologize for any inconvenience caused. At no point was the integrity of your signatures or your data affected.

Read the full incident report →

Started Jun 22, 2026, 10:34 AM UTC· resolved Jun 22, 2026, 10:40 AM UTC

1. investigating Jun 22, 2026, 10:34 AM UTC

   Since 12:06 PM (CET), we have identified an issue affecting the real-time update of element statuses within the application. All underlying processes are operating normally. Signatures, approvals, and document workflows are being processed and completed correctly. However, the application is not receiving the events that refresh the status of items on screen. As a result, an action that has actually completed - for example, a signature that has been successfully signed - may still appear with its previous status in the interface. To note: This is a display-only issue. No data is lost and no action is blocked. The actual state of your documents and signatures is correct on our side. API is not affected. Workaround: To see the up-to-date status, please force a refresh of your browser using CTRL+F5 (or the refresh button in your browser). Our teams are actively working on a resolution. We will provide an update as soon as more information is available.

2. resolved Jun 22, 2026, 10:40 AM UTC

   As of 12:35 PM (CET), the issue has been resolved. The application is once again receiving events normally, and element statuses are updating in real time as expected. To recap: between 12:06 PM and 12:35 PM (CET), the application was not receiving the events used to refresh the status of items on screen. All underlying processes continued to operate normally throughout this period - signatures, approvals, and document workflows were processed and completed correctly. The issue affected the display of statuses only; no data was lost and no action was blocked. You should no longer need to manually refresh your browser to see the current status of your documents and signatures. We are now investigating the root cause of this degradation to prevent it from recurring. Thank you for your patience.

Read the full incident report →

Started Jun 10, 2026, 07:51 AM UTC· resolved Jun 10, 2026, 08:04 AM UTC

1. investigating Jun 10, 2026, 07:51 AM UTC

   Since 9:31 AM (CEST), we are experiencing degraded performance affecting both the Yousign application and the API v3. The main impact is increased latency in the execution of our processes. Our team is actively investigating to assess the full scope of the impact and identify the root cause. We will provide a further update as soon as we have more information. We apologize for any inconvenience this may cause.

2. resolved Jun 10, 2026, 08:04 AM UTC

   As of 10:00 AM (CEST), the latency affecting the Yousign application and the API v3 has been resolved, and process execution times are back to normal. During the incident window (9:31 AM - 10:00 AM CEST), in addition to the delay in process execution, notifications to signers including email, SMS, and voice were also affected by delays. All notifications have now been delivered and the service is operating normally. We apologize for any inconvenience this may have caused and thank you for your patience.

Read the full incident report →

Started Jun 03, 2026, 03:36 PM UTC· resolved Jun 03, 2026, 04:10 PM UTC

1. investigating Jun 03, 2026, 03:36 PM UTC

   Since 4:24pm CET, we're currently experiencing degraded performance on Advanced eSignature identification and image Identity Verification for Verify due to an ongoing incident with one of our third-party providers. Some users may notice slower response times or intermittent errors. Our team is actively monitoring the situation and working with the provider to restore full functionality. We'll share updates as more information becomes available.

2. investigating Jun 03, 2026, 03:45 PM UTC

   We are continuing to investigate this issue.

3. monitoring Jun 03, 2026, 03:57 PM UTC

   Advanced eSignature identification and image Identity Verification are back to normal since 5:44pm CET. The incident impacted the service from 4:28pm to 5:44pm CET. We are monitoring the situation closely and awaiting confirmation from our third-party provider before resolving this incident.

4. resolved Jun 03, 2026, 04:10 PM UTC

   This incident is now resolved. Advanced eSignature identification and image Identity Verification for Verify have been fully operational since 5:44pm CEST. We will continue to investigate with our provider to identify the root cause and prevent any recurrence. We apologize for any inconvenience caused.

Read the full incident report →

Started May 25, 2026, 08:17 AM UTC· resolved May 25, 2026, 09:06 AM UTC

1. resolved May 25, 2026, 08:17 AM UTC

   Between 09:56 and 10:06 CET, customers may have experienced increased latency and intermittent slowness on API v2 and v3 endpoints. The issue has been identified and resolved. All services are now operating normally. We apologize for the inconvenience and thank you for your patience.

Read the full incident report →

Started May 21, 2026, 08:19 AM UTC· resolved May 21, 2026, 08:58 AM UTC

1. investigating May 21, 2026, 08:19 AM UTC

   Since 10:00 AM CET, we are observing increased processing times on electronic signature operations. Signatures are still being processed successfully, but with higher latency than usual. Our engineering teams are actively investigating the root cause. We will provide an update as soon as we have more information. Thank you for your patience.

2. investigating May 21, 2026, 08:44 AM UTC

   Since 10:00 AM CET, we are observing increased processing times on the following operations: - Simple Electronic Signature (SES) - Advanced Electronic Signature (AES) - Simple and Advanced eSeal Qualified Electronic Signature (QES) is not impacted and continues to operate normally. Operations are still being processed successfully, but with higher latency than usual. Our engineering teams are actively investigating the root cause and we will provide an update as soon as we have more information. Thank you for your patience.

3. resolved May 21, 2026, 08:58 AM UTC

   Processing times on Simple/Advanced Electronic Signature and Simple/Advanced eSeal started to recover at 10:51 AM CET and returned to normal at 10:57 AM CET. All operations are now processed with usual latency. Qualified Electronic Signature (QES) was not impacted at any point during the event. A post-event analysis is being conducted by our engineering teams to identify the root cause and prevent recurrence. Thank you for your patience.

Read the full incident report →

Started May 18, 2026, 08:00 AM UTC· resolved May 18, 2026, 08:11 AM UTC

1. identified May 18, 2026, 08:00 AM UTC

   Since 9:35 AM, we are experiencing an issue affecting the v3 application. The API and the application are working normally, and your actions are being processed correctly on our side. However, the browser is not receiving real-time status updates. For example, a signature request that has just been signed will not automatically appear as signed in the application. Workaround: Refresh the page manually to see the latest status. Next update: We are currently rolling back a recent configuration change to restore normal behavior. We will share an update as soon as the situation evolves. We apologize for the inconvenience and thank you for your patience.

2. resolved May 18, 2026, 08:11 AM UTC

   The application has been working normally since 9:57 AM. Notifications are now being delivered to users' browsers as expected. Important action is required for already-connected users: **If you were connected to the application between 9:35 AM and 9:57 AM, please force a refresh of your browser page to restore real-time updates.** You can do this by: Clicking the refresh button in your browser, or Pressing Ctrl + R (Windows / Linux) or Cmd + R (Mac). Users who connect (or reconnect) after 9:57 AM are not affected and do not need to take any action. We sincerely apologize for the inconvenience caused during this incident. We are now marking this incident as resolved and thank you for your patience and understanding.

Read the full incident report →

Started May 12, 2026, 03:20 PM UTC· resolved May 12, 2026, 04:04 PM UTC

1. investigating May 12, 2026, 03:20 PM UTC

   Since 17:03 (CET), our customers may experience HTTP 500 errors on the Public API and intermittent instabilities on the Yousign application. Our engineering teams are currently investigating the root cause. We will provide an update as soon as we have more information. We apologize for the inconvenience.

2. monitoring May 12, 2026, 03:32 PM UTC

   The incident has been resolved since 17:19 (CET). The root cause has been identified and the situation is now back to normal. The Public API and Yousign application are operating as expected.

3. resolved May 12, 2026, 04:04 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 30, 2026, 07:31 AM UTC· resolved Apr 30, 2026, 08:04 AM UTC

1. investigating Apr 30, 2026, 07:31 AM UTC

   We are currently experiencing delays in signature processing affecting both our v2 and v3 Products. Users may experience longer than usual processing times when signing documents.Status: We identified the issue at 09:19 AM CEST and our engineering team is actively working on restoring normal service. We are implementing a failover to resolve the situation. We will provide an update within the next 30 minutes. We apologize for the inconvenience.

2. identified Apr 30, 2026, 07:37 AM UTC

   Our teams have identified the issue, and we are actively working to resolve it. SES signatures have been processed since 9:33 a.m.; we are working to reduce the processing time for AES and QES.

3. monitoring Apr 30, 2026, 07:43 AM UTC

   Our teams have resolved the issue with the signature processing delay: * Processing of SES-level signatures has been back to normal since 9:33 a.m. * Processing of AES- and QES-level signatures has been back to normal since 9:38 a.m. Everything has been back to normal since 9:40 a.m. We apologize for the inconvenience.

4. resolved Apr 30, 2026, 08:04 AM UTC

   The incident is fully resolved. The root cause was a network outage on one of the datacenters hosting our electronic signature operations. The recovery time corresponds to the failover process to our secondary datacenter and the automatic patching of the affected components. SES signatures were restored first (9:33 AM), followed by AES and QES signatures (9:38 AM), with full service recovery at 9:40 AM. Our teams are currently investigating the root cause of the network outage. We thank you for your patience.

Read the full incident report →

Started Apr 08, 2026, 07:07 AM UTC· resolved Apr 08, 2026, 08:27 AM UTC

1. investigating Apr 08, 2026, 07:07 AM UTC

   Since 8:50 a.m., our webhooks/notifications are running slowly on API; The app and API remain functional and accessible. we are investigating the cause

2. identified Apr 08, 2026, 07:39 AM UTC

   A fix has just been deployed, and notifications regarding the status of the signatures are currently being sent out. Please note that the signatures were properly signed and accessible; only the API webhooks had not been sent since 8:50 a.m.

3. identified Apr 08, 2026, 07:53 AM UTC

   FYI - We have reassessed the initial impact. The response time is normal for both the app and the API. Only the webhooks (notifications) for the v3 API were down from 8:50 AM to 9:43 AM. Since 9:43 AM, notifications/webhooks have been sent (though there is still some delay).

4. monitoring Apr 08, 2026, 07:59 AM UTC

   All notifications/webhooks have been sent, and the service is back to normal.

5. resolved Apr 08, 2026, 08:27 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 07, 2026, 08:23 AM UTC· resolved Apr 07, 2026, 09:19 AM UTC

1. investigating Apr 07, 2026, 08:23 AM UTC

   We are experiencing performance slowdowns on our v3 Application and API since 9:47 AM UTC+2. Application: Slower navigation and page load times API: Increased response times on API requests and delays in webhook delivery Signing delays are not affected by this issue. Our team is actively investigating the root cause. We have increased system capacity to help reduce the impact while we work on a resolution. We will provide updates as we learn more.

2. identified Apr 07, 2026, 08:28 AM UTC

   As of 10:22 a.m., the situation has returned to normal. We have increased our system's processing capacity while we identify the cause of the slowdown.

3. monitoring Apr 07, 2026, 08:35 AM UTC

   The incident is now under monitoring; the situation has been stable since 10:22 a.m.

4. resolved Apr 07, 2026, 09:19 AM UTC

   The issue has been resolved since 10:22 a.m; our teams are investigating the root cause.

Read the full incident report →