Yousign Incident History

1. CompletedOct 22 · 06:30 UTC

   The scheduled maintenance has been completed.

Reported by Yousign on their status page.

1. resolvedOct 16 · 12:40 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.

Reported by Yousign on their status page.

1. ResolvedOct 16 · 12:40 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.

Reported by Yousign on their status page.

1. resolvedOct 16 · 10:11 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.

Reported by Yousign on their status page.

1. ResolvedOct 16 · 10:11 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.

Reported by Yousign on their status page.

1. resolvedOct 7 · 15:50 UTC

   This incident has been resolved.

Reported by Yousign on their status page.

1. CompletedOct 14 · 23:10 UTC

   The scheduled maintenance has been completed.

Reported by Yousign on their status page.

1. resolvedOct 4 · 14:41 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

Reported by Yousign on their status page.

1. ResolvedOct 4 · 14:41 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

Reported by Yousign on their status page.

1. resolvedSep 14 · 11:50 UTC

   This incident has been resolved.

Reported by Yousign on their status page.

1. resolvedSep 4 · 21:06 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.

Reported by Yousign on their status page.

1. resolvedSep 2 · 15:19 UTC

   This incident has been resolved.

Reported by Yousign on their status page.

1. resolvedSep 1 · 18:08 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.

Reported by Yousign on their status page.

1. resolvedAug 13 · 16:05 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.

Reported by Yousign on their status page.

1. resolvedJul 25 · 10:53 UTC

   This incident has been resolved.

Reported by Yousign on their status page.

1. resolvedJul 17 · 14:03 UTC

   This incident has been resolved.

Reported by Yousign on their status page.

1. resolvedJul 15 · 19:45 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.

Reported by Yousign on their status page.

1. resolvedJul 5 · 03:43 UTC

   This incident has been resolved.

Reported by Yousign on their status page.

1. resolvedJun 30 · 12:08 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.

Reported by Yousign on their status page.

1. resolvedJun 29 · 13:07 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.

Reported by Yousign on their status page.

1. resolvedJun 22 · 10:40 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.

Reported by Yousign on their status page.

1. resolvedJun 10 · 08:04 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.

Reported by Yousign on their status page.

1. resolvedJun 3 · 16:10 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.

Reported by Yousign on their status page.

1. resolvedMay 25 · 08:17 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.

Reported by Yousign on their status page.

1. resolvedMay 21 · 08:58 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.

Reported by Yousign on their status page.

1. resolvedMay 18 · 08:11 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.

Reported by Yousign on their status page.

1. resolvedMay 12 · 16:04 UTC

   This incident has been resolved.

Reported by Yousign on their status page.

1. resolvedApr 30 · 08:04 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.

Reported by Yousign on their status page.

1. resolvedApr 8 · 08:27 UTC

   This incident has been resolved.

Reported by Yousign on their status page.

1. resolvedApr 7 · 09:19 UTC

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

Reported by Yousign on their status page.

1. resolvedApr 2 · 08:26 UTC

   Between 09:36 and 09:47 CEST, we experienced degraded performance affecting access to both our API and application. Since 10:20 CEST, all signature processing times have returned to normal and the platform is operating as expected. We are investigating the root cause of this incident. We apologize for any inconvenience this may have caused.

Reported by Yousign on their status page.

1. resolvedApr 2 · 08:05 UTC

   Between 09:36 and 09:47 CEST, we experienced degraded performance affecting access to both our API and application. Some users may have encountered difficulties accessing the platform or experienced slower response times during this period. The situation has been stable since 09:47 CEST. However, we are currently experiencing delays in signature processing as a result of this incident. Our team is actively working to clear the backlog and return to normal processing times. We continue to investigate the root cause of this degradation and will provide an update once our analysis is complete. We apologize for any inconvenience this may have caused.

Reported by Yousign on their status page.

1. resolvedMar 25 · 12:05 UTC

   The signature processing delays have been fully resolved. Following the deployment of our fix at 12:50, all pending signatures were progressively processed and the backlog was fully cleared by 13:02. All signatures are now being processed normally. All systems are operating as expected. We apologize for the inconvenience caused during this incident and thank you for your patience.

Reported by Yousign on their status page.

1. resolvedMar 3 · 00:00 UTC

   [Resolved] Between 13:11 and 13:23 (CEST), users experienced issues with document manipulation - specifically, uploads and downloads were unavailable from both the Yousign App and API. Our team identified and resolved the issue at 13:23. All document-related operations are now fully restored and functioning normally. We apologize for any disruption this may have caused to your workflows. If you are still experiencing issues, please do not hesitate to contact our support team.

Reported by Yousign on their status page.

1. resolvedFeb 18 · 14:42 UTC

   Resolved – This incident has been resolved. Here is a summary of the event:

   • Starting at 10:00 AM UTC, we observed degraded performance across our services. The platform remained fully functional, but response times were higher than normal.
   • From 11:46 AM to 12:12 PM UTC, access to the service was severely degraded, with intermittent availability and reduced performance.
   • As of 12:12 PM UTC, all services have fully recovered. Access times have returned to normal and no further issues have been observed.

   We have thoroughly verified that all systems are now operating as expected. We sincerely apologize for any inconvenience this may have caused. Thank you for your patience.

Reported by Yousign on their status page.

1. resolvedFeb 12 · 11:54 UTC

   This incident has been resolved.

Reported by Yousign on their status page.

1. resolvedFeb 11 · 17:07 UTC

   This incident has been resolved. An exceptional maintenance will be carried tonight. See https://yousign.statuspage.io/incidents/4k77yv97894b for more details.

Reported by Yousign on their status page.

1. resolvedFeb 9 · 14:06 UTC

   This incident has been resolved.

Reported by Yousign on their status page.

1. resolvedFeb 5 · 10:24 UTC

   Yousign V3 (APP+API) had a momentary PDF handling issue that was self-healed by resilience mechanism. The issue was identified and is now fixed. Issues occurred between 11:24 and 11:29 CET. We apologize for any inconvenience caused. Our support teams remain available should you need any further assistance.

Reported by Yousign on their status page.

1. resolvedJan 23 · 16:34 UTC

   Between 5:12 PM and 5:20 PM (CET), some users may have experienced slowdowns or errors when uploading or previewing documents. Full service was restored by 5:20 PM, and all features are now operating normally. We apologize for any inconvenience caused. Our support teams remain available should you need any further assistance.

Reported by Yousign on their status page.

1. resolvedDec 18 · 17:06 UTC

   Dear users, We have not observed any new events since the service stabilization. The application and the v3 API remain fully operational. At this stage, the incident is considered closed on our side. We are now awaiting the post-mortem from our infrastructure provider, OVH, to better understand the underlying cause of the issue. Thank you for your patience throughout this incident. We apologize for any inconvenience caused. Our support teams remain available should you need any further assistance.

Reported by Yousign on their status page.

1. resolvedDec 17 · 16:19 UTC

   The service is now stable. We have switched to a backup storage system located in another data center. OVH’s status page confirms an incident affecting the primary storage we were using: https://bare-metal-servers.status-ovhcloud.com/incidents/wvy4v173tkb1 We are no longer observing any instability and are therefore closing this communication. We are now awaiting the postmortem from our provider (OVH) to fully understand the root cause. We apologize for any inconvenience this may have caused. Our support teams remain available should you need any assistance.

Reported by Yousign on their status page.

1. resolvedDec 16 · 14:53 UTC

   Pending signatures have been processed. We sincerely apologize for the inconvenience. For any questions or assistance, contact us at support@yousign.com.

Reported by Yousign on their status page.

1. resolvedDec 16 · 16:28 UTC

   The incident is resolved. Pending archives have been processed. We sincerely apologize for the inconvenience.

Reported by Yousign on their status page.

1. postmortemDec 4 · 15:48 UTC

   Impact and Incident Resolution Report

   Dear Yousign users,

   On December 4th, 2025 at 12:09 CET, our services experienced delays in signatures.

   The resolution required a hardware intervention at 12:46 CET which led to service unavailability.

   With the end of the intervention, all services were fully restored at 12:57 CET and delay returned to normal at 13:10 CET.

   Below is a detailed explanation of the events and the actions being taken.

   Summary of the incident

   A network malfunction occurred on one of the components of our load balancing layer, responsible for directing incoming traffic to our application services.

   The load balancer entered again in a faulty state.

   During this period, Yousign applications and API were still available but delaying signatures (including eSeal).

   After investigation, the engineering team had to perform hardware intervention on the faulty equipment in order to restore nominal state.

   In the mean time, all services were unreachable between 12:46 CET and 12:57 CET.

   The engineering team had to reload all network configuration.

   All application services were restored at 12:57 CET.

   Delay was totally absorbed at 13:10 CET.

   It is important to known that the failing load balancer is the same one as in recent incidents.

   Root Cause

   A hardware failure on a load balancing component within our datacenter.

   Next Actions

   An exceptional maintenance is already planned on Monday December 8th for this equipment.

   The maintenance is a cornerstone towards increase resilience of all Yousign services.

   We sincerely apologize for the impact this incident may have had on your operations.

   Thank you for your understanding and continued trust in Yousign.

Reported by Yousign on their status page.

1. resolvedDec 3 · 15:41 UTC

   This incident has been resolved.

Reported by Yousign on their status page.

1. postmortemDec 3 · 09:13 UTC

   Impact and Incident Resolution Report

   Dear Yousign users,

   On December 2nd, 2025, our services experienced two consecutive incidents impacting access to the Yousign platform and temporarily delaying signature processing.
   All services were fully restored at 11:53 CET.

   Below is a detailed explanation of the events and the actions being taken.

   Summary of the two incidents

   First Incident (10:53 CET → 11:10 CET)

   A hardware malfunction occurred on one of the components of our load balancing layer, responsible for directing incoming traffic to our application services.
   The component entered a fault state and shut down, causing a temporary interruption of access to the platform.

   It automatically restarted according to its configuration, and all application services were restored at 11:10 CET.

   Second Incident (11:32 CET → 11:53 CET)

   Immediately after the first recovery, we notified our infrastructure provider.
   During the provider's on-site verification of the faulty hardware, a manual reset was triggered on the same component, even though the services had already recovered.

   This second reset generated a new interruption between 11:32 CET and 11:45 CET, with signature delays fully resolved at 11:53 CET.

   Root Cause

   A hardware failure on a load balancing component within our datacenter.

   Next Actions

   Execution of an exceptional maintenance operation on Monday, December 8th, contributing to the ongoing reinforcement of our traffic management layer and its fault tolerance.

   Updated operational guidelines with our infrastructure provider to avoid unnecessary manual resets on recovered systems.

   Additional diagnostics and hardware-level actions to ensure long-term reliability.

   We sincerely apologize for the impact this incident may have had on your operations.

   Thank you for your understanding and continued trust in Yousign.

Reported by Yousign on their status page.

1. postmortemDec 3 · 09:11 UTC

   Impact and Incident Resolution Report

   Dear Yousign users,

   On December 2nd, 2025, our services experienced two consecutive incidents impacting access to the Yousign platform and temporarily delaying signature processing.
   All services were fully restored at 11:53 CET.

   Below is a detailed explanation of the events and the actions being taken.

   Summary of the two incidents

   First Incident (10:53 CET → 11:10 CET)

   A hardware malfunction occurred on one of the components of our load balancing layer, responsible for directing incoming traffic to our application services.
   The component entered a fault state and shut down, causing a temporary interruption of access to the platform.

   It automatically restarted according to its configuration, and all application services were restored at 11:10 CET.

   Second Incident (11:32 CET → 11:53 CET)

   Immediately after the first recovery, we notified our infrastructure provider.
   During the provider's on-site verification of the faulty hardware, a manual reset was triggered on the same component, even though the services had already recovered.

   This second reset generated a new interruption between 11:32 CET and 11:45 CET, with signature delays fully resolved at 11:53 CET.

   Root Cause

   A hardware failure on a load balancing component within our datacenter.

   Next Actions

   Execution of an exceptional maintenance operation on Monday, December 8th, contributing to the ongoing reinforcement of our traffic management layer and its fault tolerance.

   Updated operational guidelines with our infrastructure provider to avoid unnecessary manual resets on recovered systems.

   Additional diagnostics and hardware-level actions to ensure long-term reliability.

   We sincerely apologize for the impact this incident may have had on your operations.

   Thank you for your understanding and continued trust in Yousign.

Reported by Yousign on their status page.

1. postmortemNov 27 · 16:03 UTC

   \## Incident Impact and Resolution Report Dear Yousign Users, On November 27, 2025 between 08:36 and 09:00 CET, we encountered production issues leading to an important degradation of our services. \## Root Cause Analysis The virtualization service provided by our infrastructure vendor entered a partially unresponsive state, causing a subset of Virtual Machines to stop responding. Our engineering team quickly reacted to qualify the issue and then restarted and conciliated the impacted services. \## Next Actions We are actively challenging our infrastructure provider to determine the root cause of this incident and to elaborate a plan to avoid it in the future as this incident take place after an upgrade of the virtualization service. As of today we have already identified technical points of failure and we will prioritize the remediation accordingly. We would like to apologize for the impact on your service and assure you that every effort is being made to learn from this event and ensure that it does not happen again. Thank you for your understanding and thank you for your continued trust in Yousign.

Reported by Yousign on their status page.

1. resolvedNov 27 · 05:04 UTC

   This incident has been resolved.

Reported by Yousign on their status page.

1. postmortemNov 26 · 09:10 UTC

   Incident Impact and Resolution Report

   Dear Yousign Users,

   On November 24, 2025 between 12:24 and 12:35 CET, we performed a routine maintenance operation on the equipment responsible for electronic signatures, in accordance with our standard software lifecycle policy.

   While these updates are typically not visible for our customers, this specific operation took longer than anticipated. Consequently, our engineering team promptly initiated a rollback procedure to restore optimal performance.

   The time required to detect the anomaly and complete the rollback resulted in a temporary increase in signature processing times across our services.

   Once the rollback was completed, signature processing resumed at normal speed at 12:41 CET.

   Root Cause Analysis

   The routine software update applied to our signature hardware equipment did not complete within the expected timeframe compared to our test validations.

   Next Actions

   We are actively reviewing the update process for this specific equipment to ensure future maintenance operations remain fully transparent and to further minimize reaction times in case of anomalies.

   We would like to apologize for the impact on your service and assure you that every effort is being made to learn from this event and ensure that it does not happen again.

   Thank you for your understanding and thank you for your continued trust in Yousign.

Reported by Yousign on their status page.

1. resolvedOct 31 · 13:43 UTC

   This incident has been resolved.

Reported by Yousign on their status page.

1. resolvedOct 22 · 12:04 UTC

   This incident has been resolved.

Reported by Yousign on their status page.

1. resolvedOct 7 · 10:08 UTC

   This incident has been resolved.

Reported by Yousign on their status page.

1. resolvedOct 3 · 08:12 UTC

   A fix has been implemented. Pending signatures have been processed. We sincerely apologize for the inconvenience. For any questions or assistance, contact us at support@yousign.com.

Reported by Yousign on their status page.