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
Provider resolved: . The notice publication date does not establish the outage start.
eSignature / EU
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 from 2026-04-28 08:07 AM UTC until 2026-04-28 09:46 AM UTC.
monitoring
A fix has been implemented and engineers are now monitoring telemetry to validate.
identified
Engineers have identified a root cause and are working on releasing a fix.
investigating
A subset of customers in EU may experience latency with Send operations. Engineering teams have been engaged and are actively triaging.
Some customers are seeing errors previewing and sending envelopes via Docusign App Launcher (Incident 4752)
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 utilizing the Docusign App Launcher in Salesforce may have seen errors from 2026-04-23 04:40 PM UTC until 2026-04-23 08:35 PM UTC.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
Some users might experience latency when attempting to convert non-PDF documents (Incident 4750)
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 from 2026-04-23 02:53 PM UTC until 2026-04-23 08:09 PM UTC
monitoring
We continue to monitor for stability while we investigate possible secondary factors.
monitoring
We are continuing to monitor for any further issues.
monitoring
We are continuing to monitor for any further issues.
monitoring
We continue to monitor the environment to ensure stability.
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.
Customers may experience intermittent latency and errors in Navigator (Incident 4748)
Provider resolved: . The notice publication date does not establish the outage start.
eSignature / NA2eSignature / NA4
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 intermittent latency and errors in Navigator from 2026-04-23 12:57 PM UTC until 2026-04-23 11:12 PM UTC.
identified
The issue has been identified and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
We are continuing to investigate this issue.
investigating
More engineering teams have been engaged to triage this error and investigation is continuing.
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating the issue.
Login failures and Latency Issues with Sending and Signing Envelopes (Incident 4717)
Provider resolved: . The notice publication date does not establish the outage start.
eSignature / CA
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 login failures and latency issues with Sending and Signing from 2026-04-17 02:08 PM UTC until 2026-04-17 03:09 PM UTC
monitoring
We are continuing to monitor for any further issues.
monitoring
Internal testing is showing the implemented fix has resolved the impact, we are continuing to monitor to ensure the issue is fully mitigated.
identified
Our engineering teams have identified the root cause of this issue and are in the process of deploying a fix.
investigating
We are currently investigating a spike in latency for send and sign services which may affect a subset of customers. We have engaged our engineering teams and are actively triaging this issue.
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 intermittent errors, jobs not completing, and the inability to login to UAT from 2026-04-11 01:32 AM UTC April 11 until 2026-04-11 04:53 AM UTC.
identified
The issue has been identified and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
Customers may experience intermittent errors, jobs not completing, and the inability to login to UAT.
User Membership Group Update Delays (Incident 4672)
Provider resolved: . The notice publication date does not establish the outage start.
eSignature / AUeSignature / 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 delays from 2026-04-09 04:24 AM UTC until 2026-04-09 09:22 PM UTC.
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are implementing a change to resolve the AU delay.
identified
NA1 is now back to normal operational expectations. We are working to resolve the issue in AU now.
identified
Changes to user membership groups is significantly delayed. We are making changes to reduce or remove the delay.
March 2026
Issues in UAT and DEMO S1 when attempting to complete tasks in task groups (Incident 4591)
Provider resolved: . The notice publication date does not establish the outage start.
CLM / UAT NA11CLM / DEMO S1
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-03-27 12:32 AM UTC until 2026-03-27 11:30 PM 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
We are continuing to work on a fix for this issue.
identified
We are continuing to work on a fix for this issue.
identified
Engineers are continuing to triage and develop a fix to the identified issue.
identified
A potential cause has been identified, engineering teams are reproducing the issue and reviewing telemetry before applying a fix.
investigating
More engineering teams have been engaged to triage this error and investigation is continuing.
investigating
Due to a recently identified issue in our UAT environments, tasks may be routed incorrectly, leading to failures. Our team is actively working on identifying the root cause and mitigating it, and we will keep you updated as progress is made. Please note that any workflows and tasks on your Production environment should not be affected, and will still be executed normally.
CLM & Docusign Gen for Salesforce Customers may be having difficulties accessing EU sites (Incident 4517)
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Some CLM sites experienced a service disruption impacting some users’ ability to access the site. The impacted time windows are the following:
US11: 2026-03-14 1:20 AM UTC until 2026-03-14 9:20 AM UTC
US12: 2026-03-14 1:20 AM UTC until 2026-03-14 10:15 AM UTC
US13: 2026-03-14 1:20 AM UTC until 2026-03-14 7:35 AM UTC
EU11: 2026-03-16 8:05 PM UTC until 2026-03-16 10:45 PM UTC
EU21: 2026-03-14 1:20 AM UTC until 2026-03-17 00:15 AM UTC
monitoring
We continue to monitor the environment to ensure stability.
Any company logos that were missing or outdated have been updated.
monitoring
We continue to monitor the environment to ensure stability. Updates will be posted less often during monitoring unless a significant issue develops.
Customers may notice some visual issues, such as custom logos not appearing. Services are functional.
monitoring
A fix has been implemented and we are monitoring the results.
Customers may notice some visual issues, such as custom logos not appearing. Services are functional.
identified
The failover steps for EU21 are nearing completion. A subset of customers have been enabled and we are monitoring carefully.
identified
We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.
identified
We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.
identified
We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.
identified
We are still continuing to work through the failover steps for EU21.
identified
We are still continuing to work through the failover steps for EU21, additional engineering resources have been engaged. EU11 is now full recovered.
identified
We are still continuing to work through the failover steps for EU21. EU11 is now showing signs of recovery and we are continuing to monitor the health of the site to ensure stability.
identified
We are still continuing to work through the failover steps for EU21. Eu11 Remains in a degraded state, additional engineering teams haven been engaged and triage is continuing.
identified
We are still continuing to work through the failover steps for EU21. Engineering teams are still triaging issues on EU11.
identified
We are continuing to work through the failover steps for EU21. We have identified the issue with EU11 and are now working to implement a fix to restore service.
identified
We are continuing to work through the failover steps for EU21. We are now seeing additional impact to our EU11 site and have engaged further engineering resources to triage.
identified
We are continuing to work through the failover steps for EU21. Meanwhile, we have implemented a fix and are seeing improved stability on our EU11 environment.
identified
We are continuing to work through the failover steps for EU21. Meanwhile, we have implemented a fix and are seeing improved stability on our EU11 environment.
identified
We have identified an intermittent degradation in our EU11 environment and are working on fixing it.
identified
We are continuing to work through failover steps.
identified
We are continuing to work through failover steps.
identified
We have identified that the recovery of EU21 will require the failover of our compute systems. This is a complex operation and will take some time. We will provide updates every 2 hours as recovery progresses.
identified
We are continuing to work on a fix for this issue.
identified
The issue has been identified and a fix is being implemented.
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to work on a fix for this issue.
identified
The issue has been identified and a fix is being implemented.
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 remediate impact to EU21 customers.
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to remediate impact to EU11 and EU21 customers.
identified
We are continuing to work on a fix for EU21 customers. EU21 customers may observe issues accessing the site. EU11 customers may see intermittent issues generating documents.
monitoring
A fix has been implemented for US sites as of approximately 09:00 UTC.
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to work on a fix for this issue.
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.
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating this issue.
Users may encounter errors while attempting to upload or edit documents. (Incident 4504)
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-03-04 03:04 PM UTC until 2026-03-12 10:06 PM 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. We estimate the fix will be deployed by 22:30 UTC
identified
We are continuing to work on a fix for this issue. We estimate the fix will be deployed by 22:30 UTC
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.
