DocuSign had 117 outages in the last 2 years totaling 63h 2m of downtime — averaging 4.8 incidents per month.
There were 117 DocuSign outages since October 21, 2025 totaling 63h 2m of downtime. Each is summarised below — incident details, duration, and resolution information.
Customers may be experiencing latency when loading the CLM UI in S1.EU. We are actively investigating this issue.
We are continuing to investigate this issue.
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
We are investigating delays across the site.
We have identified the underlying cause and are working to implement a fix.
The issue has been identified and we continue our work to implement a fix.
A fix has been implemented and we are monitoring the results.
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US
This incident has been resolved.
Customers in JP1 may experience issues when writing back to Salesforce after signing a document. Engineering teams are engaged and are actively triaging this issue.
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
We are actively investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Some customers may be experiencing issues when attempting to sign in to Docusign in the AU region. Engineering teams have been engaged and we are actively triaging this issue.
Our engineering teams have identified the potential cause of this issue and we are in the process of deploying a fix.
Our engineering teams have deployed a fix to the affected environments and we are monitoring our telemetry to validate.
Further monitoring has concluded that the fix implemented by our engineering teams has resolved this incident.
Customers across NA11 are seeing latency and delays across the service. We have identified the underlying issue and are taking action to mitigate the issue.
A fix has been implemented and we are monitoring the results.
The issue has been identified and we continue our work to implement a fix.
The fix was implemented and we are monitoring to ensure stability.
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
We are actively investigating this issue.
We are continuing to investigate this issue.
We have identified the issue and a fix is being implemented.
The issue has been identified and we continue our work to implement a fix.
A fix has been implemented and we are monitoring the results.
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
We are actively investigating this issue.
We are continuing to investigate this issue.
We continue to investigate the issue and additional resources have been engaged.
We have identified the issue and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
We are investigating this issue.
We are continuing to investigate this issue.
We have identified the issue and a fix is being implemented.
The issue has been identified and we continue our work to implement a fix.
A fix has been implemented and we are monitoring the results.
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Customers may encounter document generation failures with salesforce integration. We are currently investigating the issue.
We are continuing to investigate this issue.
We have identified the issue and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
We are actively investigating this issue.
A fix has been implemented and we are monitoring the results.
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Customers in Europe may experience failures with envelope writeback and status update when reviewing Connect logs for DAl envelopes. Engineering teams are engaged and are actively triaging.
We are continuing to investigate this issue.
We continue to investigate the issue and additional resources have been engaged.
We are currently investigating an issue affecting customers using the Salesforce integration across EU and NA regions. Customers may experience failures with envelope write-back and status updates, with the error: "The underlying connection was closed. An unexpected error occurred on send." Services affected: Salesforce connector (envelope write-back, status updates) Impact: Completed envelope statuses may not be reflected in Salesforce. Our engineering teams are actively investigating the root cause across multiple workstreams. We will provide updates as the investigation progresses.
We have identified the issue and a fix is being implemented.
The issue has been identified and we continue our work to implement a fix.
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
We are actively investigating this issue.
We are continuing to investigate this issue.
We have identified the issue and a fix is being implemented.
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
We are actively investigating this issue.
Customers may be experiencing issues when attempting qualified verifications. Engineering teams have been engaged and are actively triaging this issue.
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
We are actively investigating this issue.
We are continuing to investigate this issue.
AU and JP are stable at present. Teams are continuing to investigate the issue.
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
We are actively investigating this issue.
We have identified the issue and a fix is being implemented.
The issue has been identified and we continue our work to implement a fix.
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
We are actively investigating this issue.
We have identified the issue and a fix is being implemented.
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
We are actively investigating this issue.
We have identified the issue and a fix is being implemented.
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
We are actively investigating this issue.
We are continuing to investigate this issue.
We have identified the issue and a fix is being implemented.
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
LexisNexis has been made aware of the issue and are currently investigating.
LexisNexis is continuing to investigate the issue.
LexisNexis is continuing to investigate the issue.
LexisNexis has reported resolving the issue. We are continuing to monitor.
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
We have identified the issue and a fix is being implemented.
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.