Looking for an update now? Check the current status, or follow DocuSign for future changes.
81.8%of 44 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 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
August 2026
Document generation failures in salesforce integration (Incident 5525)
Provider resolved: . The notice publication date does not establish the outage start.
eSignature / EUCLM / EU21
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-08-03 05:59 PM UTC until 2026-08-04 04:53 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 continuing to investigate this issue.
investigating
Customers may encounter document generation failures with salesforce integration.
We are currently investigating the issue.
Powerforms Intermittently Not Loading (Incident 5517)
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-08-03 01:00 PM UTC until 2026-08-03 08:45 PM UTC.
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are actively investigating this issue.
July 2026
Failures with Envelope Writeback and Status Updates (Incident 5505)
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-07-29 01:43 AM UTC until 2026-07-31 05:14 PM UTC.
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 the root cause across multiple workstreams. We will provide updates as the investigation progresses.
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.
Provider resolved: . The notice publication date does not establish the outage start.
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-07-30 06:49 PM UTC until 2026-07-30 08:51 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.
Customers may experience errors when signing up for new accounts (Incident 5500)
Provider resolved: . The notice publication date does not establish the outage start.
eSignature / DEMO
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-07-30 06:14 PM UTC until 2026-07-30 07:47 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.
Trusted Service Provider / PROD
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-07-27 09:05 AM UTC until 2026-07-27 05:10 PM UTC.
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)
Provider resolved: . The notice publication date does not establish the outage start.
eSignature / AUeSignature / JP1
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-07-23 05:30 PM UTC until 2026-07-23 10:16 PM UTC.
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)
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-07-22 05:24 PM UTC until 2026-07-22 09:15 PM UTC.
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)
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-07-17 03:55 PM UTC until 2026-07-17 05:57 PM UTC.
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 5399)
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 errors from 2026-07-15 02:56 AM UTC until 2026-07-15 03:24 AM UTC.
identified
We have identified the issue and a fix is being implemented.
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
Some customers (including Notary customers) may not be able to authenticate via LexisNexis' Knowledge-Based Authentication, leading to failure in signing envelopes. (Incident 5383)
minorSource 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)
minorSource 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)
minorSource 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)
minorSource 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)
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 actively investigating this issue.
June 2026
Customers may experience latency (Incident 5259)
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 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)
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 with Sending and Signing in NA3 (Incident 5247)
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.
Intermittent issues with Reports and Search on S1 Prod (Incident 5233)
minorSource 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)
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 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.
