DocuSign Outage History
Uptime record, past incidents, and downtime history for DocuSign.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| May 2026 | 64% | 25 | 9 |
| April 2026 | 83.3% | 30 | 5 |
| March 2026 | 64.5% | 31 | 11 |
| February 2026 | 80% | 5 | 1 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Feb 24
Today
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)
Started: May 21, 11:12 PM
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.
May 21, 11:12 PM
Some customers may experience latencies sending and signing in EU (Incident-4915)
Started: May 19, 12:59 PM
investigating
We are continuing to investigate the issue.
May 19, 1:30 PM
investigating
We are currently investigating the issue.
May 19, 12:59 PM
Some customers may experience latencies sending and signing in NA1 and NA3 (Incident-4902)
Started: May 18, 5:55 PM
investigating
We are currently investigating this issue.
May 18, 5:55 PM
Users may experience document report failures and loading delays in the EU11 and EU21 sites (incident 4863)
Started: May 14, 6:45 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 14, 7:54 PM
identified
The issue has been identified and a fix is being implemented.
May 14, 7:23 PM
investigating
We are currently investigating this issue.
May 14, 6:45 PM
Workflow Reports Experiencing Timeout Errors (Incident 4874)
Started: May 13, 11:49 AM
monitoring
A fix has been implemented and we are observing telemetry to validate.
May 13, 1:41 PM
identified
We are continuing to work on a fix for this issue.
May 13, 11:50 AM
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.
May 13, 11:49 AM
Customers may experience issues accessing PowerForms (Incident-4870)
Started: May 12, 7:41 PM
investigating
We are currently investigating this issue.
May 12, 7:41 PM
Users may experience timeouts when attempting to complete document transactions (incident 4866)
Started: May 12, 6:17 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 12, 7:51 PM
identified
We are continuing to work on a fix for this issue.
May 12, 7:33 PM
identified
The issue has been identified and a fix is being implemented.
May 12, 6:43 PM
investigating
We are currently investigating this issue.
May 12, 6:17 PM
Users may experience connection errors when trying to switch to CLM or utilising DocuSign edit (Incident 4862)
Started: May 12, 1:42 PM
monitoring
A fix has now been implemented and we are seeing improvements, we will continue monitoring telemetry to ensure the fix is final.
May 12, 3:55 PM
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.
May 12, 3:20 PM
monitoring
Our engineering teams have deployed a fix and we are now monitoring to validate.
May 12, 2:24 PM
identified
We are continuing to work on a fix for this issue.
May 12, 2:23 PM
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 ...
May 12, 1:42 PM
Users may experience connection errors when trying to switch to CLM (Incident 4861)
Started: May 12, 8:46 AM
investigating
Additional teams have been engaged to triage this issue.
May 12, 9:45 AM
investigating
A subset of customers may be experiencing connection errors in the UI when attempting to switch to CLM. Engineering teams have been engaged and are actively triaging this issue.
May 12, 8:46 AM
Users may encounter errors that will prevent document uploading or envelope creation (Incident 4860)
Started: May 11, 11:14 PM
identified
The issue has been identified and a fix is being implemented.
May 11, 11:14 PM
AU Site Outage (Incident 4840)
Started: May 8, 2:09 AM
monitoring
We have implemented a mitigation and are monitoring the results.
May 8, 3:03 AM
investigating
We are continuing to investigate this issue.
May 8, 2:35 AM
investigating
We are currently investigating this issue.
May 8, 2:09 AM
April 2026
Send Latency in EU (Incident 4776)
Started: Apr 28, 9:03 AM
identified
Engineers have identified a root cause and are working on releasing a fix.
Apr 28, 9:24 AM
investigating
A subset of customers in EU may experience latency with Send operations. Engineering teams have been engaged and are actively triaging.
Apr 28, 9:03 AM
Some customers are seeing errors previewing and sending envelopes via Docusign App Launcher (Incident 4752)
Started: Apr 23, 8:14 PM
identified
The issue has been identified and a fix is being implemented.
Apr 23, 8:27 PM
investigating
We are currently investigating this issue.
Apr 23, 8:14 PM
Some users might experience latency when attempting to convert non-PDF documents (Incident-4750)
Started: Apr 23, 4:28 PM
monitoring
We continue to monitor for stability while we investigate possible secondary factors.
Apr 23, 10:34 PM
monitoring
We are continuing to monitor for any further issues.
Apr 23, 9:23 PM
monitoring
We are continuing to monitor for any further issues.
Apr 23, 8:02 PM
monitoring
We continue to monitor the environment to ensure stability.
Apr 23, 7:18 PM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 23, 5:31 PM
identified
The issue has been identified and a fix is being implemented.
Apr 23, 5:07 PM
investigating
We are currently investigating this issue.
Apr 23, 4:28 PM
Customers may experience intermittent latency and errors in Navigator (Incident 4748)
Started: Apr 23, 3:27 PM
identified
The issue has been identified and a fix is being implemented.
Apr 23, 9:21 PM
investigating
We are continuing to investigate this issue.
Apr 23, 7:37 PM
investigating
We are continuing to investigate this issue.
Apr 23, 6:35 PM
investigating
More engineering teams have been engaged to triage this error and investigation is continuing.
Apr 23, 5:40 PM
investigating
We are continuing to investigate this issue.
Apr 23, 4:44 PM
investigating
We are currently investigating the issue.
Apr 23, 3:27 PM
Login failures and Latency Issues with Sending and Signing Envelopes
Started: Apr 17, 2:47 PM
monitoring
We are continuing to monitor for any further issues.
Apr 17, 3:57 PM
monitoring
Internal testing is showing the implemented fix has resolved the impact, we are continuing to monitor to ensure the issue is fully mitigated.
Apr 17, 3:12 PM
identified
Our engineering teams have identified the root cause of this issue and are in the process of deploying a fix.
Apr 17, 2:53 PM
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.
Apr 17, 2:47 PM
Intermittent Errors in UAT (Incident 4682)
Started: Apr 11, 3:54 AM
identified
The issue has been identified and a fix is being implemented.
Apr 11, 4:41 AM
investigating
We are continuing to investigate this issue.
Apr 11, 4:19 AM
investigating
Customers may experience intermittent errors, jobs not completing, and the inability to login to UAT.
Apr 11, 3:54 AM
User Membership Group Update Delays (Incident 4672)
Started: Apr 9, 7:40 PM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 9, 9:01 PM
identified
We are implementing a change to resolve the AU delay.
Apr 9, 8:39 PM
identified
NA1 is now back to normal operational expectations. We are working to resolve the issue in AU now.
Apr 9, 7:56 PM
identified
Changes to user membership groups is significantly delayed. We are making changes to reduce or remove the delay.
Apr 9, 7:40 PM
March 2026
Issues in UAT and DEMO S1 when attempting to complete tasks in task groups (Incident 4591)
Started: Mar 27, 12:41 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 27, 10:39 PM
identified
We are continuing to work on a fix for this issue.
Mar 27, 9:00 PM
identified
We are continuing to work on a fix for this issue.
Mar 27, 5:22 PM
identified
We are continuing to work on a fix for this issue.
Mar 27, 4:21 PM
identified
Engineers are continuing to triage and develop a fix to the identified issue.
Mar 27, 3:42 PM
identified
A potential cause has been identified, engineering teams are reproducing the issue and reviewing telemetry before applying a fix.
Mar 27, 2:59 PM
investigating
More engineering teams have been engaged to triage this error and investigation is continuing.
Mar 27, 2:26 PM
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.
Mar 27, 12:41 PM
Search Indexing Delays (Incident 4539)
Started: Mar 18, 12:13 AM
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.
Mar 18, 12:13 AM
CLM & Salesforce Integration Customers may be having difficulties accessing EU sites (Incident 4517)
Started: Mar 14, 4:54 PM
monitoring
We continue to monitor the environment to ensure stability.
Any company logos that were missing or outdated have been updated.
Mar 17, 7:40 PM
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.
Mar 17, 4:36 AM
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.
Mar 17, 12:51 AM
identified
The failover steps for EU21 are nearing completion. A subset of customers have been enabled and we are monitoring carefully.
Mar 16, 10:03 PM
identified
We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.
Mar 16, 7:25 PM
identified
We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.
Mar 16, 5:19 PM
identified
We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.
Mar 16, 3:15 PM
identified
We are still continuing to work through the failover steps for EU21.
Mar 16, 12:49 PM
identified
We are still continuing to work through the failover steps for EU21, additional engineering resources have been engaged. EU11 is now full recovered.
Mar 16, 11:12 AM
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.
Mar 16, 11:03 AM
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.
Mar 16, 10:46 AM
identified
We are still continuing to work through the failover steps for EU21. Engineering teams are still triaging issues on EU11.
Mar 16, 9:32 AM
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.
Mar 16, 8:58 AM
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.
Mar 16, 8:27 AM
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.
Mar 16, 6:59 AM
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.
Mar 16, 4:49 AM
identified
We have identified an intermittent degradation in our EU11 environment and are working on fixing it.
Mar 16, 3:31 AM
identified
We are continuing to work through failover steps.
Mar 16, 2:47 AM
identified
We are continuing to work through failover steps.
Mar 16, 12:51 AM
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.
Mar 15, 11:25 PM
identified
We are continuing to work on a fix for this issue.
Mar 15, 10:31 PM
identified
The issue has been identified and a fix is being implemented.
Mar 15, 8:00 PM
identified
We are continuing to work on a fix for this issue.
Mar 15, 5:17 PM
identified
We are continuing to work on a fix for this issue.
Mar 15, 11:40 AM
identified
The issue has been identified and a fix is being implemented.
Mar 15, 8:30 AM
monitoring
We are continuing to monitor for any further issues.
Mar 15, 4:23 AM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 14, 11:41 PM
identified
We are continuing to remediate impact to EU21 customers.
Mar 14, 11:11 PM
identified
We are continuing to work on a fix for this issue.
Mar 14, 10:09 PM
identified
We are continuing to work on a fix for this issue.
Mar 14, 8:24 PM
identified
We are continuing to remediate impact to EU11 and EU21 customers.
Mar 14, 6:27 PM
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.
Mar 14, 4:58 PM
monitoring
A fix has been implemented for US sites as of approximately 09:00 UTC.
Mar 14, 4:54 PM
identified
We are continuing to work on a fix for this issue.
Mar 14, 3:59 PM
identified
We are continuing to work on a fix for this issue.
Mar 14, 2:44 PM
identified
We are continuing to work on a fix for this issue.
Mar 14, 9:19 AM
identified
We are continuing to work on a fix for this issue.
Mar 14, 9:17 AM
identified
We are continuing to work on a fix for this issue.
Mar 14, 6:07 AM
identified
We are continuing to work on a fix for this issue.
Mar 14, 3:11 AM
identified
The issue has been identified and a fix is being implemented.
Mar 14, 2:42 AM
investigating
We are continuing to investigate this issue.
Mar 14, 2:27 AM
investigating
We are continuing to investigate this issue.
Mar 14, 2:08 AM
investigating
We are currently investigating this issue.
Mar 14, 2:07 AM
Users may encounter errors while attempting to upload or edit documents. (Incident 4504)
Started: Mar 12, 8:23 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 12, 9:41 PM
identified
We are continuing to work on a fix for this issue. We estimate the fix will be deployed by 22:30 UTC
Mar 12, 8:49 PM
identified
We are continuing to work on a fix for this issue. We estimate the fix will be deployed by 22:30 UTC
Mar 12, 8:23 PM
identified
The issue has been identified and a fix is being implemented.
Mar 12, 7:23 PM
investigating
We are currently investigating this issue.
Mar 12, 6:15 PM