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.
April 2026
Send Latency in EU (Incident 4776)
minorSource not attested
Last archived state: resolved
View archived record details
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)
minorSource not attested
Last archived state: resolved
View archived record details
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)
minorSource not attested
Last archived state: resolved
View archived record details
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)
minorSource not attested
Last archived state: resolved
View archived record details
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
majorSource not attested
Last archived state: resolved
View archived record details
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.
Intermittent Errors in UAT (Incident 4682)
majorSource not attested
Last archived state: resolved
View archived record details
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)
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 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)
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 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.
Search Indexing Delays (Incident 4539)
Source not attested
Last archived state: resolved
View archived record details
identified
As a continuation of incident 4517, a subset of customers may experience incomplete search results for historical documents older than one year. A fix is currently underway, and full resolution is anticipated by Wednesday, March 18, 2026 at 11:00 AM UTC.
