Historial de interrupciones de Yousign

1. September 4, 2026 at 12:30 PM UTCinvestigating

   Algunos correos electrónicos enviados a direcciones organizadas por Microsoft (Outlook, Hotmail, Live y Microsoft 365) llegan tarde o no. Fuimos alertados por clientes a las 11:30 CEST, y el número de mensajes afectados aumentó de nuevo después del mediodía. Nuestro propio seguimiento de la entrega muestra que cada email sigue siendo aceptado por nuestros proveedores de envío, por lo que el problema parece ocurrir después de esa entrega. Estamos investigando con ellos para confirmar la causa. Los correos electrónicos a todos los demás proveedores no son afectados. No se requiere acción a su lado. Publicaremos una nueva actualización tan pronto como sepamos más, y sentimos la interrupción que esto está causando.

2. September 4, 2026 at 12:43 PM UTCidentified

   Actualización: Este incidente está del lado de Microsoft, no del nuestro. Nuestros proveedores han confirmado un incidente global de Microsoft en correo inbound, que Microsoft no ha publicado en su propia página de estado. Nuestros correos electrónicos salen de nuestros sistemas y son aceptados por nuestros proveedores de envío como de costumbre, y luego paran en Microsoft. Desde esta mañana, ninguna de nuestras notificaciones de correo electrónico llega a los buzones de correo de negocios alojados por Microsoft (Microsoft 365 y Exchange Online). Las direcciones personales como Outlook.com, hotmail.com y live.com no están afectadas, y tampoco es otro proveedor. Nada que podamos cambiar a nuestro lado entregará estos correos electrónicos, por lo que no podemos arreglar este incidente o comprometernos a un tiempo de resolución. Estamos rastreando la solución con nuestros proveedores, que están en contacto directo con Microsoft. Le diremos si los correos electrónicos mantenidos desde esta mañana se entregan en recuperación o necesitan ser enviados de nuevo. Siguiente actualización dentro de la hora.

3. September 4, 2026 at 3:14 PM UTCmonitoring

   Microsoft ha resuelto su incidente. Los correos electrónicos a los buzones comerciales de Microsoft están siendo aceptados de nuevo, por lo que las nuevas notificaciones pasan normalmente. Los correos electrónicos mantenidos durante el incidente siguen siendo enviados por nuestro proveedor, que reporta alrededor del 40% de ellos dejados para entregar. Hasta que se haya despejado ese atraso, los receptores podrán recibir notificaciones con retraso. Nada se pierde, y no necesitas enviar nada de nuevo. Cuán rápido que los desagües atrasados dependen de nuestro proveedor y de la tasa que Microsoft acepta, y no es algo que controlamos más que el incidente en sí mismo fue. Siguiente actualización una vez que el atraso se entrega completamente.

4. September 4, 2026 at 9:06 PM UTCresolved

   Resolvido. El atraso se entrega completamente: cada correo electrónico mantenido durante el incidente ha sido enviado ahora, y la entrega a Microsoft buzones de correo de negocios ha vuelto a la normalidad desde que Microsoft cerró su incidente. Lo que sucedió: a partir de las 11:30 CEST, un incidente global de Microsoft en correo de entrada impidió que nuestras notificaciones llegaran a los buzones de correo de negocios alojados por Microsoft 365 y Exchange Online. Las direcciones personales como Outlook.com, hotmail.com y live.com nunca fueron afectadas, y ningún otro proveedor de correo electrónico estuvo involucrado. Nuestros sistemas seguían enviando normalmente a lo largo de todo, y los mensajes fueron consultados por nuestro proveedor en lugar de perdidos. Una vez que Microsoft restauró el servicio, esa cola fue removida durante las siguientes horas, por lo que algunas notificaciones llegaron tarde esta tarde y esta noche. La causa y la solución estaban al lado de Microsoft. Lo que podemos mejorar es lo rápido que detectamos un bloqueo en un solo proveedor y le contamos sobre ello, y estamos trabajando en ello. Gracias por su paciencia, y lamento la interrupción que esto causó a su día.

Traducido automáticamente desde la actualización oficial del incidente.

1. September 2, 2026 at 2:28 PM UTCinvestigating

   Actualmente estamos experimentando una degradación del servicio de Firma Electrónica Calificada (QES). Desde 15:40 (CEST), algunos intentos de firma QES están fallando intermitentemente (durante la parte de identificación del flujo). Los fallos son aleatorios: cuando se produce un error, refrescar la página y reintentar generalmente permite que la firma se complete. También se observó una degradación similar a principios de hoy, entre las 14:50 y las 15:05. Los firmantes que ya tienen una cartera no son impactados: sus firmas están trabajando normalmente. Sólo los firmantes que pasan por el flujo de verificación de identidad para obtener una nueva cartera pueden encontrar estos errores. Estamos en contacto con nuestro proveedor de identidad para resolver el problema y estabilizar el servicio. Compartiremos una nueva actualización tan pronto como tengamos más información y una visión más clara del impacto. Sinceramente nos disculpamos por la inconveniencia y les agradecemos su paciencia y comprensión.

2. September 2, 2026 at 2:40 PM UTCmonitoring

   Actualización rápida sobre la degradación de QES reportada anteriormente. Desde 16:27 (CEST), no hemos observado más errores, y las firmas QES se completan normalmente. Actualmente estamos confirmando con nuestro proveedor de identidad que la causa raíz se ha resuelto definitivamente. Seguiremos monitoreando el servicio de cerca y enviaremos una actualización final una vez tengamos esta confirmación. Gracias por su paciencia y comprensión.

3. September 2, 2026 at 3:19 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 31, 2026 at 9:42 AM UTCidentified

   Queridos usuarios, Uno de nuestros proveedores de verificación de identidad se enfrenta actualmente a dificultades técnicas. Como consecuencia, los siguientes flujos se impactan a través de nuestros productos: Firma electrónica avanzada: Los firmantes APP v3 pueden encontrar largos tiempos de procesamiento de identificación, y una pequeña fracción de firmas también pueden encontrar errores al intentar realizar una identificación Verificar la verificación de identidad: todas las solicitudes de verificación de identidad de API se registran correctamente y están pendientes a nuestro lado y se procesarán una vez que el proveedor vuelva en línea Trabajamos activamente con los proporcionados para proporcionar una rápida recuperación de nuestros servicios, y lo mantendremos actualizado a lo largo del proceso. Nos disculpamos por cualquier inconveniente que esto pueda causar y apreciar su comprensión mientras trabajamos para mejorar nuestro servicio. Para cualquier pregunta o asistencia, contáctenos en [email protected].

2. August 31, 2026 at 10:03 AM UTCmonitoring

   Nuestro proveedor ha restaurado sus servicios y ahora estamos monitoreando de cerca la situación mientras procesamos el atraso de las verificaciones pendientes: Firma electrónica avanzada: los firmantes que intentaron realizar verificaciones de identidad durante el outage del proveedor podrían encontrar errores en su flujo de signos. Estamos trabajando activamente para normalizar su situación. Otros firmantes que comienzan el flujo ahora no deben encontrar ningún error más Verificar la verificación de identidad: todas las solicitudes deben ser procesadas con éxito según los tiempos de procesamiento estándar (unos segundos por solicitud) Estamos monitoreando y lo mantendremos actualizado.

3. August 31, 2026 at 10:55 AM UTCmonitoring

   Confirmamos que los servicios de identificación están ahora completamente en línea, con cierta latencia debido a los atrasos de verificación. Esta latencia está mejorando gradualmente y seguimos monitoreándola. Los firmantes avanzados de firma electrónica que intentaron identificar durante la ventana de salida del proveedor ahora deben reiniciar su proceso de identificación con éxito. El fallido intento de identificación realizado durante la salida no se contabilizará en los datos de facturación / consumo.

4. August 31, 2026 at 1:28 PM UTCmonitoring

   A medida que nuestro proveedor está escalando sus operaciones para absorber el atraso de las verificaciones, los servicios de verificación de identidad de verificación de verificación de identidad siguen siendo afectados por una latencia significativa. Estamos colaborando estrechamente con el proveedor para garantizar la restauración sin problemas de los servicios. La firma electrónica avanzada no está impactada.

5. August 31, 2026 at 6:30 PM UTCmonitoring

   Seguimos observando latencia en los servicios de verificación de identidad. Nuestro proveedor de verificación de identidad ha movilizado plenamente a sus equipos para absorber el atraso de las verificaciones pendientes durante el final del día y la noche. A medida que el volumen de solicitudes entrantes disminuye gradualmente, esperamos que su sistema vuelva a los tiempos de procesamiento estándar durante la noche. No se perderán datos: todas las solicitudes de verificación de identidad presentadas durante este período se registran de forma segura a nuestro lado y serán procesadas, no se requiere ninguna acción de usted, y no hay necesidad de presentar ninguna solicitud. Electrónica avanzada La firma no se impacta en esta etapa. Estamos monitoreando continuamente la situación y proporcionaremos una actualización adicional si algo cambia. Siguiente actualización esperada mañana por la mañana, o antes si la situación evoluciona. Nos disculpamos por la molestia. Para cualquier pregunta, comuníquese con nosotros en [email protected].

6. September 1, 2026 at 6:00 AM UTCmonitoring

   Nuestro proveedor ha identificado la causa raíz de sus inestabilidades del sistema, vinculadas a su capa de orquestador para los servicios de verificación. Han estabilizado completamente sus sistemas durante la noche, lo que significa que los tiempos de procesamiento de la verificación de identidad están ahora de vuelta a su duración estándar de unos segundos. Ahora estamos trabajando gradualmente a través del atraso de las verificaciones pendientes y esperamos que todos sean procesados durante las horas de la mañana. Seguimos vigilando la situación.

7. September 1, 2026 at 8:44 AM UTCmonitoring

   Después de consumir una parte significativa de las verificaciones pendientes, nuestro proveedor se enfrenta de nuevo a inestabilidades. Los servicios avanzados de firma electrónica (AES) y verificación de identidad están en un estado pendiente como consecuencia: Los firmantes de AES se enfrentan a desaceleraciones de identificación o errores Solicitudes de verificación de identidad están pendientes y se procesarán una vez que nuestro proveedor esté de nuevo Estamos monitoreando la situación y lo mantendremos actualizado.

8. September 1, 2026 at 12:37 PM UTCmonitoring

   Hemos mantenido un intercambio profundo con nuestro proveedor, que nos permitió localizar la causa raíz exacta de su problema de escalada con un camino a la resolución identificada. Firma electrónica avanzada está totalmente operativa. Identificar la verificación es ahora también operacional, mientras que seguimos procesando el atraso de las verificaciones pendientes en las próximas horas.

9. September 1, 2026 at 6:08 PM UTCresolved

   Todos los servicios de verificación de identidad están ahora plenamente operativos, y hemos implementado medidas adicionales para mejorar la estabilidad de los servicios sobre la base de información sobre nuestra infraestructura de proveedores. Ahora estamos cerrando este incidente, y sinceramente nos disculpamos por cualquier inconveniente causado.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 13, 2026 at 3:22 PM UTCinvestigating

   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. August 13, 2026 at 3:28 PM UTCinvestigating

   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. August 13, 2026 at 3:57 PM UTCinvestigating

   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. August 13, 2026 at 4:05 PM UTCresolved

   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.

1. July 24, 2026 at 11:29 AM UTCmonitoring

   Actualmente estamos experimentando retrasos en la firma calificada (QES). Estos retrasos provienen de uno de nuestros proveedores de verificación de identidad, que actualmente está experimentando tiempos elevados de respuesta. Como resultado, la verificación de identidad y la terminación de firmas QES pueden tardar más de lo habitual. Todos los demás niveles de firma (SES, AES) no están afectados. Sinceramente nos disculpamos por la molestia. Nuestros equipos están totalmente movilizados para supervisar la situación y restaurar el servicio normal lo antes posible. Proporcionaremos actualizaciones aquí lo antes posible.

2. July 24, 2026 at 12:03 PM UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

3. July 25, 2026 at 10:53 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 17, 2026 at 8:46 AM UTCinvestigating

   Actualmente estamos experimentando retrasos en el procesamiento de algunas solicitudes de QES eSignature. Las firmas siguen siendo manejadas correctamente. La creación de cartera y el flujo de firma son funcionales pero los documentos firmados no pueden recuperarse aún. Todos los demás niveles de firma no se ven afectados. Sinceramente nos disculpamos por la molestia. Nuestros equipos están totalmente movilizados para identificar la causa raíz e implementar una solución lo antes posible.

2. July 17, 2026 at 9:12 AM UTCidentified

   Uno de nuestros proveedores está experimentando un outage. Nos disculpamos por la molestia y proporcionaremos actualizaciones lo antes posible.

3. July 17, 2026 at 9:26 AM UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

4. July 17, 2026 at 9:32 AM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

5. July 17, 2026 at 9:44 AM UTCidentified

   Seguimos trabajando para solucionar este problema.

6. July 17, 2026 at 9:55 AM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

7. July 17, 2026 at 2:03 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 15, 2026 at 7:25 PM UTCinvestigating

   Algunos clientes pueden estar experimentando un problema con nuestro servicio. Nuestros ingenieros están trabajando para identificar y resolver esto lo más rápido posible. Lo actualizaremos de nuevo en breve. Si tiene preguntas urgentes, póngase en contacto con nuestro equipo de soporte enviando un correo electrónico a [email protected].

2. July 15, 2026 at 7:34 PM UTCidentified

   Se han determinado las cuestiones. Nuestro equipo está trabajando en ello.

3. July 15, 2026 at 7:45 PM UTCresolved

   Nuestro proveedor de infraestructura realizó una actualización sobre nuestra infraestructura de bajo nivel que se suponía que no tenía impacto. La actualización ya está terminada y todos los servicios están de vuelta a la normalidad. Perdón por la degradación del servicio que pudo haber ocurrido durante este período.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 5, 2026 at 2:54 AM UTCinvestigating

   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. July 5, 2026 at 2:55 AM UTCinvestigating

   Since 04:26 (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.

3. July 5, 2026 at 3:20 AM UTCinvestigating

   We are continuing to investigate this issue.

4. July 5, 2026 at 3:22 AM UTCmonitoring

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

5. July 5, 2026 at 3:43 AM UTCresolved

   This incident has been resolved.

1. June 30, 2026 at 11:51 AM UTCinvestigating

   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. June 30, 2026 at 12:06 PM UTCidentified

   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. June 30, 2026 at 12:08 PM UTCresolved

   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.

1. June 29, 2026 at 9:10 AM UTCinvestigating

   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. June 29, 2026 at 9:15 AM UTCmonitoring

   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. June 29, 2026 at 9:54 AM UTCidentified

   [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. June 29, 2026 at 10:15 AM UTCmonitoring

   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. June 29, 2026 at 1:07 PM UTCresolved

   [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.

1. June 22, 2026 at 10:34 AM UTCinvestigating

   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. June 22, 2026 at 10:40 AM UTCresolved

   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.

1. June 10, 2026 at 7:51 AM UTCinvestigating

   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. June 10, 2026 at 8:04 AM UTCresolved

   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.

1. June 3, 2026 at 3:36 PM UTCinvestigating

   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. June 3, 2026 at 3:45 PM UTCinvestigating

   We are continuing to investigate this issue.

3. June 3, 2026 at 3:57 PM UTCmonitoring

   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. June 3, 2026 at 4:10 PM UTCresolved

   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.

1. May 25, 2026 at 8:17 AM UTCresolved

   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.

1. May 21, 2026 at 8:19 AM UTCinvestigating

   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. May 21, 2026 at 8:44 AM UTCinvestigating

   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. May 21, 2026 at 8:58 AM UTCresolved

   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.

1. May 18, 2026 at 8:00 AM UTCidentified

   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. May 18, 2026 at 8:11 AM UTCresolved

   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.

1. May 12, 2026 at 3:20 PM UTCinvestigating

   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. May 12, 2026 at 3:32 PM UTCmonitoring

   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. May 12, 2026 at 4:04 PM UTCresolved

   This incident has been resolved.

1. April 30, 2026 at 7:31 AM UTCinvestigating

   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. April 30, 2026 at 7:37 AM UTCidentified

   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. April 30, 2026 at 7:43 AM UTCmonitoring

   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. April 30, 2026 at 8:04 AM UTCresolved

   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.

1. April 8, 2026 at 7:07 AM UTCinvestigating

   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. April 8, 2026 at 7:39 AM UTCidentified

   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. April 8, 2026 at 7:53 AM UTCidentified

   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. April 8, 2026 at 7:59 AM UTCmonitoring

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

5. April 8, 2026 at 8:27 AM UTCresolved

   This incident has been resolved.

1. April 7, 2026 at 8:23 AM UTCinvestigating

   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. April 7, 2026 at 8:28 AM UTCidentified

   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. April 7, 2026 at 8:35 AM UTCmonitoring

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

4. April 7, 2026 at 9:19 AM UTCresolved

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