New Multi-region uptime checks and custom-domain status pages

DocuSign Outage History

Daily provider-status observations and published incident history for DocuSign.

Operational

DocuSign is operational. Verified . Official provider source.

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

Jul 23Oct 21

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 23 Today
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)
minor

View incident details and source

Notice published:

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)
minor

View incident details and source

Notice published:

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)
minor

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

eSignature / NA1 eSignature / 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)
minor

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

CLM / EU11 CLM / 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.
investigating
We are currently investigating this issue.
Workflow Reports Experiencing Timeout Errors (Incident 4874)
minor

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

CLM / EU11 CLM / 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)
minor

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

eSignature / AU eSignature / CA eSignature / EU eSignature / JP1 eSignature / NA1 eSignature / NA2 eSignature / NA3 eSignature / NA4
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 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)
minor

View incident details and source

Notice published:

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)
minor

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

CLM / EU11 CLM / EU21 CLM / NA11 CLM / NA21 CLM / S1.US CLM / S2.US CLM / S1.EU CLM / S1.AU CLM / US11 CLM / US12 CLM / US13 CLM / UAT NA11 CLM / 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 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)
minor

View incident details and source

Notice published:

Provider resolved: . The notice publication date does not establish the outage start.

eSignature / NA2 eSignature / 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.
AU Site Outage (Incident 4840)
major

View incident details and source

Notice published:

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.

July 2026
Some customers (including Notary customers) may not be able to authenticate via LexisNexis' Knowledge-Based Authentication, leading to failure in signing envelopes. (Incident 5383)
minor Source not attested
Last archived state: resolved
View archived record details
investigating
LexisNexis is continuing to investigate the issue.
investigating
LexisNexis is continuing to investigate the issue.
investigating
LexisNexis has been made aware of the issue and are currently investigating.
Some customers may not able to open any CLM documents (Incident 5375)
minor Source not attested
Last archived state: resolved
View archived record details
identified
We have identified the issue and a fix is being implemented.
Errors accessing the sending web application (Incident 5334)
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We continue to investigate with our CDN partner to determine why a very small group of end users are seeing errors. Disabling browser cache completely or completely emptying browser cache and trying again will unblock users. Please contact docusign support if you need assistance. An update will be provided when a significant update is available.
investigating
We continue to investigate with our CDN partner to determine why a very small group of end users are seeing errors. Disabling browser cache completely or completely emptying browser cache and trying again will unblock users. Please contact docusign support if you need assistance. An update will be provided when a significant update is available.
investigating
We are continuing to investigate the web cache issue. A small subset of customers may see an error when accessing the send web application page. Completely emptying the browser cache and trying again is a viable fix. Updates will be posted when there is a significant update.
investigating
We continue to investigate and have engaged external vendor resources
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
A small subset of customers may see errors accessing the sending web application. We are actively investigating the underlying cause.
Intermittent Issues With Delivery of e-mail Notifications (Incident 5326)
minor Source not attested
Last archived state: resolved
View archived record details
identified
A subset of customers may experience intermittent failures of email notifications upon sending of envelopes. To mitigate this customers can log into their DocuSign account and access the envelope directly. Engineering teams have identified the issue and are currently working to resolve this issue.
Intermittent Errors and Delays (Incident 5312)
minor Source 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 actively investigating this issue.
June 2026
Customers may experience latency (Incident 5259)
minor Source not attested
Last archived state: resolved
View archived record details
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. We will provide the next update in approximately 24 hours.
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.
Some customers may experience errors with Sending and Signing (Incident 5252)
minor Source 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 with Sending and Signing in NA3 (Incident 5247)
minor Source 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.
Intermittent issues with Reports and Search on S1 Prod (Incident 5233)
minor Source not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating issues with both report and search on S1 prod. Engineering teams have been engaged and are actively triaging.
Intermittent issues with Reports and Search on S1 Prod (Incident 5233)
minor Source not attested
Last archived state: resolved
View archived record details
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.