Looking for an update now? Check the current status, or follow DocuSign for future changes.
82.2%of 45 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 23Today
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.
July 2026
Failures with Envelope Writeback and Status Updates (Incident 5505)
minorSource not attested
Last archived state: resolved
View archived record details
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 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 th...
investigating
We continue to investigate the issue and additional resources have been engaged.
investigating
We are continuing to investigate this issue.
investigating
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.
Latency and Intermittent Errors (Incident 5501)
majorSource 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.
investigating
We are actively investigating this issue.
Customers may experience errors when signing up for new accounts (Incident 5500)
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.
Inbound email not may be working for some customers (Incident 5475)
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are actively investigating this issue.
Qualified Verification Latency (Incident 5472)
minorSource not attested
Last archived state: resolved
View archived record details
identified
Customers may be experiencing issues when attempting qualified verifications. Engineering teams have been engaged and are actively triaging this issue.
Customers in AU/JP may experience errors or delays when logging in, sending, or signing envelopes (Incident 5409)
minorSource not attested
Last archived state: resolved
View archived record details
investigating
AU and JP are stable at present. Teams are continuing to investigate the issue.
investigating
We are continuing to investigate this issue.
investigating
We are actively investigating this issue.
Customers may be unable to complete purchases on ecom.docusign.com (Incident 5438)
minorSource not attested
Last archived state: resolved
View archived record details
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 actively investigating this issue.
Customers may experience errors loading PowerForms to sign envelopes (Incident 5417)
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.
Customers may experience errors executing workflows and uploading documents (Incident 5386)
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 Document Generation customers are being redirected to the CLM home page (Incident 5384)
minorSource not attested
Last archived state: resolved
View archived record details
identified
We have identified the issue and a fix is being implemented.
