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.
August 2026
Issues in JP1 with Salesforce Writeback (Incident 5648)
Source not attested
Last archived state: resolved
View archived record details
JP1
investigating
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.
Document Upload and Generation Errors (Incident 5595)
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are continuing to investigate this issue.
investigating
We are actively investigating this issue.
Degraded Task Processing and Latency across multiple services (Incident 5576)
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We continue to monitor the environment to ensure stability.
monitoring
We continue to monitor the environment to ensure stability.
identified
We continue to work to implement a fix for the issue.
identified
Our initial fix did not fully mitigate this issue. Our teams are continuing to work to implement a fix to resolve the issue.
monitoring
A fix has been implemented and we are monitoring the results.
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 continue to investigate the issue and additional resources have been engaged.
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating issues where some customers may see latency or failures when generating documents. Engineering teams have been engaged and are actively triaging.
Login Issues in AU region (Incident 5572)
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
Our engineering teams have deployed a fix to the affected environments and we are monitoring our telemetry to validate.
identified
Our engineering teams have identified the potential cause of this issue and we are in the process of deploying a fix.
investigating
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.
Latency and Errors Across NA11 (Incident 5558)
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The fix was implemented and we are monitoring to ensure stability.
identified
The issue has been identified and we continue our work to implement a fix.
monitoring
A fix has been implemented and we are monitoring the results.
identified
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.
