Yousign Outage History

Started Apr 02, 2026, 08:07 AM UTC· resolved Apr 02, 2026, 08:26 AM UTC

1. monitoring Apr 02, 2026, 08:07 AM 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.

2. resolved Apr 02, 2026, 08:26 AM 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.

Read the full incident report →

Started Mar 03, 2026, 12:00 AM UTC· resolved Mar 03, 2026, 12:00 AM UTC

1. resolved Mar 03, 2026, 12:33 PM 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.

Read the full incident report →

Started Feb 18, 2026, 10:04 AM UTC· resolved Feb 18, 2026, 02:42 PM UTC

1. investigating Feb 18, 2026, 10:04 AM UTC

   Since 10:49 AM, we have been experiencing instabilities affecting V3 applications, resulting in intermittent errors and latencies. We will keep you informed of any updates and will confirm once the situation is fully resolved.

2. investigating Feb 18, 2026, 11:01 AM UTC

   We are continuing to investigate this issue.

3. monitoring Feb 18, 2026, 11:18 AM UTC

   The applications are now fully functional. At this stage, the root cause has not yet been clearly identified. Our teams remain fully mobilized, actively monitoring the platform and continuing the investigation to determine the origin of the incident.

4. resolved Feb 18, 2026, 02:42 PM 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.

Read the full incident report →

Started Feb 12, 2026, 09:58 AM UTC· resolved Feb 12, 2026, 11:54 AM UTC

1. investigating Feb 12, 2026, 09:58 AM UTC

   We're currently experiencing delays in the processing of some eSignature requests sine 10:47 CET. Signature requests are still being properly handled. 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. investigating Feb 12, 2026, 10:17 AM UTC

   The queued messages are currently being processed, and we should return to normal within a few minutes.

3. monitoring Feb 12, 2026, 11:53 AM UTC

   Between 10:44 AM and 11:16 AM, all customers experienced service delays. From 11:16 AM to 12:30 PM, the impact was limited to a subset of customers. The incident has been fully resolved and is now closed.

4. resolved Feb 12, 2026, 11:54 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 11, 2026, 10:38 AM UTC· resolved Feb 11, 2026, 05:07 PM UTC

1. investigating Feb 11, 2026, 10:38 AM UTC

   Since 11:18 AM (CET), we are experiencing intermittent issues affecting our Application and API. These disruptions are resulting in API errors and application slowdowns. Our engineering teams are actively investigating the root cause and working to resolve this issue as quickly as possible. We apologize for any inconvenience this may cause and will provide updates as soon as more information becomes available.

2. monitoring Feb 11, 2026, 11:02 AM UTC

   Everything is now back to normal.

3. resolved Feb 11, 2026, 05:07 PM UTC

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

Read the full incident report →

Started Feb 09, 2026, 10:27 AM UTC· resolved Feb 09, 2026, 02:06 PM UTC

1. investigating Feb 09, 2026, 10:27 AM UTC

   We're currently experiencing delays in the processing of some eSignature requests sine 10:55 CET. Signature requests are still being properly handled. 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. monitoring Feb 09, 2026, 10:45 AM UTC

   Everything is now back to normal.

3. resolved Feb 09, 2026, 02:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 23, 2026, 04:34 PM UTC· resolved Jan 23, 2026, 04:34 PM UTC

1. resolved Jan 23, 2026, 04:34 PM 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.

Read the full incident report →

Started Dec 18, 2025, 10:59 AM UTC· resolved Dec 18, 2025, 05:06 PM UTC

1. investigating Dec 18, 2025, 10:59 AM UTC

   Since 11:54 AM, we have been experiencing instabilities affecting our applications and API, resulting in intermittent access to the services. We will keep you informed of any updates and will confirm once the situation is fully resolved.

2. monitoring Dec 18, 2025, 11:19 AM UTC

   Incident Update – Delay in document archiving and audit trails Dear users, As of 12:06 PM (CET), the application and the v3 API are stable and fully operational. At this stage, the root cause has not yet been clearly identified. Our teams remain fully mobilized, actively monitoring the platform and continuing the investigation to determine the origin of the incident. We will share further updates as soon as more information becomes available. Thank you for your patience and understanding.

3. resolved Dec 18, 2025, 05:06 PM 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.

Read the full incident report →

Started Dec 16, 2025, 02:12 PM UTC· resolved Dec 16, 2025, 02:53 PM UTC

1. identified Dec 16, 2025, 02:12 PM UTC

   We're currently experiencing delays in the processing of some eSignature requests. QES eSignatures are not impacted. Signature requests are still being properly handled. 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. resolved Dec 16, 2025, 02:53 PM UTC

   Pending signatures have been processed. We sincerely apologize for the inconvenience. For any questions or assistance, contact us at [email protected].

Read the full incident report →

Started Dec 16, 2025, 01:01 PM UTC· resolved Dec 16, 2025, 04:28 PM UTC

1. identified Dec 16, 2025, 01:01 PM UTC

   Dear users, We are currently experiencing an issue impacting the archiving of documents and audit trails. What happened: The issue started today at 10:15 AM (CET) and is related to our third-party archiving provider, Arkhineo. Arkhineo has informed us that they are performing an operation on their side, which is temporarily affecting their service. Current impact: Documents and audit trails intended for archiving are currently on hold on our side. Attempts to retrieve document archives or audit trails may result in errors during this period. Data integrity: Please note that no archives have been lost. All documents and audit trails are safely retained and will be archived retroactively as soon as Arkhineo's service is fully restored. Next steps: We are closely monitoring the situation with Arkhineo. Once their service is back to normal, the backlog will be processed automatically. We apologize for the inconvenience and will keep you informed if the situation evolves.

2. identified Dec 16, 2025, 02:54 PM UTC

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

3. resolved Dec 16, 2025, 04:28 PM UTC

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

Read the full incident report →

Started Dec 04, 2025, 11:19 AM UTC· resolved Dec 04, 2025, 12:22 PM UTC

1. investigating Dec 04, 2025, 11:19 AM UTC

   We are seeing a signature delay. We apologize for any inconvenience. If you have urgent questions, please contact our support team by sending an email to [email protected]

2. investigating Dec 04, 2025, 11:20 AM UTC

   We are continuing to investigate this issue.

3. identified Dec 04, 2025, 11:20 AM UTC

   The issue has been identified and our team is working on a fix. All applications are accessible, however signature processing is still experiencing a delay.

4. identified Dec 04, 2025, 11:50 AM UTC

   The v2 and v3 applications have been unavailable since 12:46. Our teams are currently investigating the issue.

5. identified Dec 04, 2025, 11:57 AM UTC

   Applications v2 and v3 are now available. We continue to experience delays in signing.

6. monitoring Dec 04, 2025, 12:17 PM UTC

   eSignature and eSeal are fully back to normal. A Postmortem will be publish soon.

7. resolved Dec 04, 2025, 12:22 PM UTC

   All applications have been operational again since 13:15, and all pending eSignatures and eSeal were fully processed by 13:10. All services are now fully operational. The root cause of the incident has been clearly identified. We apologize for the impact this has had on your activity, and we will provide a full description of these events in the upcoming postmortem.

8. postmortem Dec 04, 2025, 03:48 PM 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.

Read the full incident report →

Started Dec 03, 2025, 02:27 PM UTC· resolved Dec 03, 2025, 03:41 PM UTC

1. investigating Dec 03, 2025, 02:27 PM UTC

   All applications are currently unavailable since 15:23 CET. Our teams are actively working on the issue.

2. identified Dec 03, 2025, 02:31 PM UTC

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

3. monitoring Dec 03, 2025, 02:37 PM UTC

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

4. resolved Dec 03, 2025, 03:41 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 02, 2025, 10:37 AM UTC· resolved Dec 02, 2025, 11:01 AM UTC

1. investigating Dec 02, 2025, 10:37 AM UTC

   All applications (including API) are currently unavailable since 11:32 CET. Our teams are actively working on the issue. We will keep you updated.

2. monitoring Dec 02, 2025, 10:51 AM UTC

   Our teams have identified the root cause of the issue, and the fix is being applied. All our Applications are available since 11:48 CET. Please note that the eSignature will still experience some delay while we process the backlog accumulated during the outage. We will keep you updated as soon as everything is fully back to normal.

3. monitoring Dec 02, 2025, 10:53 AM UTC

   We are continuing to monitor for any further issues.

4. resolved Dec 02, 2025, 11:01 AM UTC

   All applications have been operational again since 11:51, and all pending eSignatures were fully processed by 11:53. The root cause of the second incident has been clearly identified. One of our datacenter servers experienced a failure. We performed an initial restart, and the datacenter technician - informed of the inaccessibility - initiated a second restart. The sequence of these actions caused a second incident immediately after the first. All services are now fully operational. We apologize for the impact this has had on your activity, and we will provide a full description of these events in the upcoming postmortem.

5. postmortem Dec 03, 2025, 09:13 AM 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.

Read the full incident report →

Started Nov 27, 2025, 07:52 AM UTC· resolved Nov 27, 2025, 11:03 AM UTC

1. investigating Nov 27, 2025, 07:52 AM UTC

   Since 08:36, access to Yousign products v2 and v3 has been degraded, affecting both the applications and the API. Our teams are actively investigating to identify the root cause and restore normal service as quickly as possible. We will provide updates as the situation evolves.

2. investigating Nov 27, 2025, 08:06 AM UTC

   Since 09:00, both the applications and the API are available again. We are still processing the different backlogs accumulated during the incident, which may cause some delays. We will notify you as soon as everything is fully back to normal.

3. monitoring Nov 27, 2025, 08:13 AM UTC

   Since 09:10, all services are fully back to normal, the delay has been recovered. Our Engineering teams are now analyzing the root cause of the incident. At this stage, the issue appears to be linked to an impact on our provider’s infrastructure. We will conduct a joint analysis with them to confirm and understand the sequence of events. We remain in active monitoring.

4. resolved Nov 27, 2025, 11:03 AM UTC

   This incident has been resolved.

5. postmortem Nov 27, 2025, 04:03 PM 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.

Read the full incident report →

Started Nov 27, 2025, 02:28 AM UTC· resolved Nov 27, 2025, 05:04 AM UTC

1. investigating Nov 27, 2025, 02:28 AM UTC

   We are currently experiencing 500 errors with our V2 and V3. primarily affecting document upload and download requests.

2. monitoring Nov 27, 2025, 02:50 AM UTC

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

3. resolved Nov 27, 2025, 05:04 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 24, 2025, 11:00 AM UTC· resolved Nov 24, 2025, 11:41 AM UTC

1. resolved Nov 25, 2025, 03:35 PM UTC

   This incident has been resolved.

2. postmortem Nov 26, 2025, 09:10 AM 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.

Read the full incident report →

Started Oct 31, 2025, 11:38 AM UTC· resolved Oct 31, 2025, 01:43 PM UTC

1. investigating Oct 31, 2025, 11:38 AM UTC

   Our provider for the long term archiving service is currenty facing a partial outage. Impact: downloading archives may lead to unexpected errors or long delays. Please be reassured that no data is lost. Thank you for your understanding. For any questions or assistance, please contact us at [email protected].

2. resolved Oct 31, 2025, 01:43 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 22, 2025, 08:14 AM UTC· resolved Oct 22, 2025, 12:04 PM UTC

1. monitoring Oct 22, 2025, 08:14 AM UTC

   One of our providers for the QES (Qualified Electronic Signature) ID verification has experienced a transient and intermittent outage between 09:46 CEST and 10:06 CEST. As a consequence, some users may have experienced some delay and potential errors for their QES signature flow during this timeframe. We are currently monitoring the provider.

2. resolved Oct 22, 2025, 12:04 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 07, 2025, 09:10 AM UTC· resolved Oct 07, 2025, 10:08 AM UTC

1. identified Oct 07, 2025, 09:37 AM UTC

   Simple and advanced signatures ( SES / AES ) have been slowed down during the 11h10 - 11h30 time slot. We are seeing a signature delay of up to 10 minutes Our system capacity has been increased to bring this delay back to normal as soon as possible. We apologize for any inconvenience. If you have urgent questions, please contact our support team by sending an email to [email protected]

2. monitoring Oct 07, 2025, 09:40 AM UTC

   All pending late signatures have been processed. We are actively monitoring the situation.

3. resolved Oct 07, 2025, 10:08 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 30, 2025, 01:25 PM UTC· resolved Sep 30, 2025, 02:54 PM UTC

1. investigating Sep 30, 2025, 01:25 PM UTC

   Some clients may experience delay in signing documents and API requests. Our engineers are working to 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. monitoring Sep 30, 2025, 02:40 PM UTC

   We would like to inform you that a remediation has been implemented following the recent incident. Our technical teams are actively monitoring all services to ensure continued stability and prevent any further impact. We experienced an influx of traffic in parallel with a supplier incident generating a stacking phenomenon leading to our service degradation. We are closely monitoring the situation and taking all necessary measures to ensure a full return to normal operations as quickly as possible.

3. resolved Sep 30, 2025, 02:54 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 30, 2025, 10:31 AM UTC· resolved Sep 30, 2025, 10:31 AM UTC

1. resolved Sep 30, 2025, 10:47 AM UTC

   Our provider for the QES ID verification has experienced an outage from 12:12pm CEST to 12:31pm CEST. Impact: Delays on QES with PVID identification creation and processing.

Read the full incident report →