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
June 2026
Intermittent issues with Reports and Search on S1 Prod (Incident 5233)
Provider resolved: . The notice publication date does not establish the outage start.
CLM / S1.US
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-06-29 08:20 AM UTC until 2026-06-29 04:46 PM UTC.
monitoring
A fix has been implemented and we are monitoring the results.
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 with both report and search on S1 prod. Engineering teams have been engaged and are actively triaging.
Customers may see increased latency when sending and signing and intermittent errors (Incident 5232)
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 and intermittent errors when sending and signing from 2026-06-29 08:18 AM UTC until 2026-06-29 06:05 PM UTC.
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.
Provider resolved: . The notice publication date does not establish the outage start.
CLM / NA21CLM / NA11
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-06-28 04:10 UTC until 2026-06-28 06:56 AM UTC.
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)
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Some customers may have experienced latency for any sending actions involving conversions, generating documents and accessing tasks from 2026-06-25 07:36 PM UTC until 2026-06-25 10:29 PM UTC.
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)
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Some customers may have experienced latency for any sending actions involving conversions, generating documents and accessing tasks from 2026-06-25 07:20 PM UTC until 2026-06-26 06:20 PM UTC.
identified
We have identified the issue and a fix is being implemented.
Provider resolved: . The notice publication date does not establish the outage start.
CLM / UAT NA11
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 issues from 2026-06-25 05:33 AM UTC until 2026-06-25 10:38 AM UTC.
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)
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Customers may have experienced issues from 2026-06-18 03:05 PM UTC until 2026-06-25 07:05 PM UTC.
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)
Provider resolved: . The notice publication date does not establish the outage start.
CLM / S1.USCLM / S2.US
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 issues from 2026-06-17 07:03 PM UTC until 2026-06-17 11:27 PM UTC.
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)
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. Salesforce for Gen customers were unable to generate documents from 2026-06-16 2:52 PM UTC until 2026-06-16 11:21 PM UTC.
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)
Provider resolved: . The notice publication date does not establish the outage start.
CLM / UAT NA11
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 issues from 2026-06-16 03:00 AM UTC until 2026-06-16 05:26 PM UTC.
resolved
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
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.
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.
