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
May 2026
Salesforce is experiencing an outage that may impact customers using the Salesforce integration (Incident-4935)
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.
Some customers may have experienced issues using the Salesforce integration from 2026-05-21 08:00 PM UTC until 2026-05-22 01:37 AM UTC.
investigating
Salesforce is experiencing an outage that may impact customers using the Salesforce integration. Docusign services are not experiencing any outages at this time. The issue will resolve when Salesforce resolves their outage.
Some customers may experience latencies sending and signing in EU (Incident-4915)
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.
Some customers may have experienced issues from 2026-05-19 12:39 PM UTC until 2026-05-19 2:33 PM UTC.
investigating
We are continuing to investigate the issue.
investigating
We are currently investigating the issue.
Some customers may experience latencies sending and signing in NA1 and NA3 (Incident-4902)
Provider resolved: . The notice publication date does not establish the outage start.
eSignature / NA1eSignature / NA3
resolved
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Some customers may experience latencies sending and signing in NA1 and NA3 from 2026-05-18 05:29 PM UTC until 2026-05-18 06:10 PM UTC.
investigating
We are currently investigating this issue.
Users may experience document report failures and loading delays in the EU11 and EU21 sites (incident 4863)
Provider resolved: . The notice publication date does not establish the outage start.
CLM / EU11CLM / EU21
resolved
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 errors from 2026-05-11 10:15 PM UTC until 2026-05-14 07:58 PM 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.
Provider resolved: . The notice publication date does not establish the outage start.
CLM / EU11CLM / EU21
resolved
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 errors from 2026-04-19 10:00 PM UTC until 2026-05-13 02:20 PM UTC.
monitoring
A fix has been implemented and we are observing telemetry to validate.
identified
We are continuing to work on a fix for this issue.
identified
Customers may be experiencing timeout errors with Workflow and Document Reports. Engineering teams have been engaged and the issue has been identified, a fix is currently being implemented.
Customers may experience issues accessing PowerForms (Incident 4870)
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 accessing PowerForms from 2026-05-12 06:10 PM UTC until 2026-05-12 07:59 PM UTC.
investigating
We are currently investigating this issue.
Users may experience timeouts when attempting to complete document transactions (Incident 4866)
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 errors from 2026-05-12 05:22 PM UTC until 2026-05-12 08:59 PM UTC.
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 currently investigating this issue.
Users may experience connection errors when trying to switch to CLM or utilising DocuSign edit (Incident 4862)
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-05-12 01:29 PM UTC until 2026-05-12 04:01 PM UTC.
monitoring
A fix has now been implemented and we are seeing improvements, we will continue monitoring telemetry to ensure the fix is final.
identified
Additional Engineering teams have been engaged to triage this issue, the current workaround is still functional:
To restore access, please contact your IT department or security team and request that the following URL be unblocked/allowed:
https://login.springcm.com
Once this URL has been added to your allowlist, you should be able to log in without any further issues.
Further investigation with our engineering teams is underway to fully resolve this issue.
monitoring
Our engineering teams have deployed a fix and we are now monitoring to validate.
identified
We are continuing to work on a fix for this issue.
identified
We are currently investigating an issue where a subset of customers utilising a particular firewall may experience issues when attempting to switch to CLM.
To restore access, please contact your IT department or security team and request that the following URL be unblocked/allowed:
https://login.springcm.com
Once this URL has been added to your allowlist, you should be able to log in without any further issues.
Further investigation with our engineering teams is underway to fully resolve this issue.
Users may encounter errors that will prevent document uploading or envelope creation (Incident 4860)
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 errors from 2026-05-11 09:21 PM UTC until 2026-05-11 11:14 PM UTC.
identified
The issue has been identified and a fix is being implemented.
Provider resolved: . The notice publication date does not establish the outage start.
eSignature / AU
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-05-08 01:45 AM UTC until 03:09 AM UTC
monitoring
We have implemented a mitigation and are monitoring the results.
investigating
We are continuing to investigate this issue.
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.
