Yousign Status Page

Jun 10, 2026 · resolved Jun 10

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.

Jun 3, 2026 · resolved Jun 3

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.

May 25, 2026 · resolved May 25

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.

May 21, 2026 · resolved May 21

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.

May 18, 2026 · resolved May 18

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.