Looking for an update now? Check the current status, or follow DocuSign for future changes.
81.8%of 44 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
83.3%
24
4
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 78 Days)
Jul 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
January 2026
Some customers may be unable to switch accounts within the eSign (DIRCA-4105)
Provider resolved: . The notice publication date does not establish the outage start.
resolved
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Customers may have experienced errors from 2026-01-07 07:45 PM UTC until 2026-01-08 01:32 PM UTC
December 2025
Customers may experience latency or failures when signing in NA1 (DIRCA-3937)
Provider resolved: . The notice publication date does not establish the outage start.
eSignature / NA1
resolved
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Customers may have experienced latency or failures when signing in NA1 from 2025-12-08 09:41 AM UTC until 2025-12-08 11:45 AM UTC.
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are currently investigating this issue.
Some CLM NA21 customers may experience latency and timeouts when logging in, browsing documents, or performing workflow tasks (DIRCA-3921)
Provider resolved: . The notice publication date does not establish the outage start.
CLM / NA21
resolved
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Customers may have experienced errors from 2025-12-03 11:51 PM UTC until 2025-12-04 12:10 AM UTC.
investigating
We are currently investigating this issue.
Some customers may experience failures trying to create or update expressions that use XML (DIRCA-3916)
Provider resolved: . The notice publication date does not establish the outage start.
CLM / EU21CLM / NA11CLM / NA21
resolved
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Customers may have experienced errors from 2025-12-03 18:58 PM UTC until 2025-12-03 21:48 UTC.
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are continuing to work on a fix for this issue.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
Some users may encounter unsuccessful document uploads, version updates or other intermittent errors. (DIRCA-3912)
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Customers may have experienced errors from 2025-12-03 02:53 PM UTC until 2025-12-03 10:23 PM UTC.
identified
We are continuing to roll out the fix for this issue.
identified
A fix is being rolled out now
identified
New documents are unaffected. A small subset of documents created during the window are unable to be updated. We are working on a fix for the subset of documents
identified
We are continuing to work on a fix for this issue.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
Legacy Incident Archive
69 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
June 2026
Customers may see increased latency when sending and signing and intermittent errors (Incident 5232)
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We continue to work to implement a fix for the issue.
identified
The issue has been identified and we continue our work to implement a fix.
identified
We have identified the issue and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
We are actively investigating this issue.
Intermittent Errors and Delays (Incident 5219)
minorSource not attested
Last archived state: resolved
View archived record details
identified
We have identified the issue and a fix is being implemented.
investigating
We are actively investigating this issue.
Some customers may experience latency for any sending actions that involve conversions, generating documents and accessing tasks (Incident 5190) (Incident 5209)
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We have identified the issue and a fix is being implemented.
Some customers may experience latency for any sending actions that involve conversions, generating documents and accessing tasks (Incident 5190)
minorSource not attested
Last archived state: resolved
View archived record details
identified
We have identified the issue and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
We are actively investigating this issue.
Platform Latency in UAT (Incident 5187)
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Fix has been implemented and we are now monitoring telemetry to validate.
identified
We have identified the source of the issue and are preparing a fix.
investigating
Customers may be experiencing latency on the platform in the UAT Environment. Engineers have been engaged and are actively triaging this issue.
Users downloading archived document ZIP files may see missing official Docusign platform seals (Incident 5139)
minorSource not attested
Last archived state: resolved
View archived record details
identified
The fix is still in progress and being deployed. We will provide an update upon resolution.
identified
An issue has been identified where documents downloaded via archived ZIP files with "masked fields" enabled are missing their Docusign platform seals. A fix is underway. We will provide an update upon resolution.
Target Fix Date: June 23, 2026
Temporary Workaround: Download documents individually rather than as an archived ZIP file to ensure platform seals are successfully applied.
Salesforce for Gen customers may be unable to generate documents (Incident 5132)
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We continue to monitor the environment to ensure stability.
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are actively investigating this issue.
Salesforce for Gen customers are unable to generate documents (Incident-5122)
minorSource not attested
Last archived state: resolved
View archived record details
identified
We are continuing to work on a fix for this issue.
identified
We have identified the issue and a fix is being implemented.
investigating
We continue to investigate the issue and additional resources have been engaged.
investigating
We continue to investigate the issue and additional resources have been engaged.
investigating
We continue to investigate the issue and additional resources have been engaged.
investigating
We are continuing to investigate this issue.
investigating
We are actively investigating this issue.
Customers may experience intermittent latency (Incident 5118)
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We continue to investigate the issue. Performance has improved but the issue is still under investigation.
investigating
We are continuing to investigate this issue.
investigating
We are actively investigating this issue.
Users may experience performance latency when utilizing the doc2pdf service (Incident 5085)
minorSource not attested
Last archived state: resolved
View archived record details
identified
We are have identified the root cause and we are implementing a fix.
