Yousign Outage History

Yousign experienced degraded performance on Advanced eSignature identification and image Identity Verification for Verify from 4:28pm to 5:44pm CET due to an incident with a third-party provider. Users encountered slower response times and intermittent errors during the 76-minute outage that affected both the API V2 and web application. The service was fully restored and Yousign is investigating with their provider to prevent recurrence.

Yousign experienced degraded performance affecting Simple/Advanced Electronic Signature and eSeal operations from 10:00 AM to 10:57 AM CET, causing increased processing times while signatures continued to process successfully. The API V2 and APP V2 components were impacted, but Qualified Electronic Signature (QES) remained unaffected throughout the 42-minute incident. Processing times began recovering at 10:51 AM CET and returned to normal latency by 10:57 AM CET.

Yousign's v3 application experienced a major incident where real-time status updates were not being delivered to users' browsers, meaning actions like completed signatures would not automatically appear as processed in the application. The API and core application functionality remained operational throughout the incident, with users able to see current status by manually refreshing their browser pages. The issue was resolved by rolling back a recent configuration change, restoring normal real-time notifications after 22 minutes.

Yousign experienced instability issues starting at 17:03 CET, causing HTTP 500 errors on their Public API and intermittent problems with their main application. The incident affected customer access to both services for 48 minutes before being resolved at 17:19 CET, with normal operations restored after the engineering team identified and addressed the root cause.

Yousign experienced signature processing delays across both v2 and v3 products due to a network outage in one of their datacenters, causing users to experience longer than usual processing times when signing documents. The incident affected the API V2 and APP V2 components and lasted 35 minutes from 9:19 AM to 9:40 AM CEST. The issue was resolved through a failover to their secondary datacenter, with SES signatures restored first, followed by AES and QES signatures.

Yousign experienced a delay in v3 API webhook notifications from 8:50 AM to approximately 9:43 AM, while the main app and API remained fully functional and signatures continued to process normally. The webhook notification system was completely down during the initial period, then experienced delays until full resolution at 10:27 AM. A fix was deployed around 9:39 AM that restored webhook delivery, and all pending notifications were successfully sent by 9:59 AM.

Yousign experienced performance slowdowns on their v3 Application and API for 55 minutes, causing slower navigation, delayed page loads, increased API response times, and webhook delivery delays. The team increased system capacity to mitigate the impact while investigating the root cause. The issue was resolved and service returned to normal, though the underlying cause remained under investigation.

Yousign experienced degraded performance affecting both their API and application from 09:36 to 09:47 CEST, causing users to encounter access difficulties and slower response times. The incident also created a backlog in signature processing that persisted after the initial performance issues were resolved. All services returned to normal operation by 10:20 CEST, with signature processing times fully restored.

Yousign experienced signature processing delays across both v2 and v3 platforms for 42 minutes, affecting API V2 and APP V2 components. While signatures continued to be processed, they took longer than usual to complete due to issues with signature callbacks. The engineering team identified the root cause, deployed a fix, and cleared the processing backlog, restoring normal operations.