Yousign kesinti geçmişi

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.

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.

We are continuing to investigate this issue.

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.

This incident has been resolved.

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.

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.

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.

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.

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.

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

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.

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

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.

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.

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.

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.

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.

We are continuing to investigate this issue.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

This incident has been resolved.

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.

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.

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.

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.

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

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.

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

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

This incident has been resolved.

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.

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.

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

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

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.

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.

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.

We are currently experiencing delays in signature processing affecting both our v2 and v3 platforms. Our team has identified the issue and is actively working on a resolution. Signatures are still being processed but may take longer than usual to complete. We apologize for any inconvenience this may cause.

We have identified the root cause of the signature processing delays. Our engineering team is currently working on implementing a fix. The issue is affecting signature callbacks across all our eSignature products (v2 and v3). We will notify you as soon as the fix is deployed. We apologize for the continued inconvenience and appreciate your patience.

We have deployed a fix to address the signature processing delays. Signature callbacks backlog is clearing. We are actively monitoring the situation to ensure full recovery. We will continue to monitor closely and will provide a final update once we confirm the incident is fully resolved. Thank you for your patience.

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.

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

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.

We are continuing to investigate this issue.

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.

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.

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.

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

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.

This incident has been resolved.

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.

Everything is now back to normal.

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