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
Users may experience performance latency when utilizing document conversion (Incident 5085)
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-12 01:15 AM UTC until 2026-06-15 06:30 PM UTC.
identified
We are have identified the root cause and we are implementing a fix.
Email notifications sent from custom domains were delayed (Incident 5106)
Provider resolved: . The notice publication date does not establish the outage start.
eSignature / DEMOCLM / DEMO S1CLM / 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-15 3:30 AM UTC until 2026-05-15 1:30 PM UTC.
investigating
We are actively investigating the issue.
Notification failures when utilising Outlook (Incident 5087)
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-12 02:52 AM UTC until 2026-06-12 05:43 AM UTC.
monitoring
A fix has been applied and our engineering teams are actively reviewing our telemetry to confirm this fix has mitigated the issue.
investigating
Customers utilising Outlook may receive delivery notification failures when sending envelopes to signers. Engineering teams have been engaged and we are actively triaiging this issue.
Document Upload and Generation Errors (Incident 5073)
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-11 06:35 PM UTC until 2026-06-11 10:52 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.
investigating
We continue to investigate the issue.
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.
CLM: Resolved Authentication/Access Issues in EU11 (Incident 5040)
Provider resolved: . The notice publication date does not establish the outage start.
CLM / EU11
resolved
An unexpected system dependency caused a temporary service disruption affecting a subset of accounts in the CLM EU11 environment between 21:09 UTC and 22:40 UTC on June 5, 2026. During this time, impacted users may have experienced authentication errors or issues accessing certain features.
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-05 21:09 UTC until 2026-06-05 22:40 UTC
Customers Unable to Purchase Plans (Incident 5034)
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-06-05 09:05 PM UTC until 2026-06-05 10:20 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.
investigating
We are actively investigating this issue.
Reports May Remain in "Exporting" Status (Incident 5020)
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Any organization reports that failed to complete during the incident can be manually re-created and run. Any scheduled reports will complete in the next run. Again, customers can manually create and run these sooner if required.
Customers may have experienced errors from 2026-06-03 05:00 AM UTC until 2026-06-04 10:50 AM UTC.
identified
Customers may be experiencing issues when attempting to export reports. Our engineering teams are engaged and have identified the cause and are working on a fix for this.
Customers dependent on deprecated TLS ciphers will experience interruption (Incident-5003)
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Some customers dependent on deprecated TLS ciphers may have experienced interruptions from 2026-06-02 10:49 PM UTC until 2026-06-03 12:49 AM UTC.
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
May 2026
Issues utilising +86 country code for sending envelopes and phone authentication (Incident 4968)
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 issues from 2026-05-28 02:06 AM UTC until 2026-05-28 04:29 PM UTC.
identified
Engineers have identified the root cause and are executing a fix.
identified
Customers attempting to send an envelope or use SMS/Phone Authentication for Envelopes utilising a +86 will experience errors during this process. Engineering teams have been engaged and triage is underway.
Customers may experience timeouts related to core AI features which include document summarization and extractions. (incident 4961)
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 issues from 2026-05-26 06:04 PM UTC until 2026-05-28 01:44 AM UTC.
monitoring
We are continuing to monitor for any further issues.
monitoring
We are continuing to monitor for any further issues.
monitoring
We are continuing to monitor for any further issues.
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 continuing to investigate 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.
