Is DocuSign Down?
Real-time status check for docusign.com
Checking status...
About DocuSign Status
BlueMonitor checks DocuSign (docusign.com) by sending automated requests to its servers. If the service responds within a normal timeframe and returns a successful status code, it's marked as operational. Response times over 3 seconds indicate the service is slow, and connection failures or server errors indicate the service may be down.
Recent Incidents
Issues in UAT and DEMO S1 when attempting to complete tasks in task groups (Incident 4591)
Mar 27 , 23:33 UTC 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-03-27 12:32 AM UTC until 2026-03-27 11:30 PM UTC Mar 27 , 22:39 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 27 , 21:00 UTC Update - We are continuing to work on a fix for this issue. Mar 27 , 17:22 UTC Update - We are continuing to work on a fix for this issue. Mar 27 , 16:21 UTC Update - We are continuing to work on a fix for this issue. Mar 27 , 15:42 UTC Update - Engineers are continuing to triage and develop a fix to the identified issue. Mar 27 , 14:59 UTC Identified - A potential cause has been identified, engineering teams are reproducing the issue and reviewing telemetry before applying a fix. Mar 27 , 14:26 UTC Update - More engineering teams have been engaged to triage this error and investigation is continuing. Mar 27 , 12:41 UTC 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)
Mar 18 , 08:22 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Mar 18 , 00:13 UTC 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.
CLM & Docusign Gen for Salesforce Customers may be having difficulties accessing EU sites (Incident 4517)
Mar 17 , 23:40 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. An RCA is anticipated to be shared here by 2026-03-19 12:00 AM UTC Mar 17 , 19:40 UTC Update - We continue to monitor the environment to ensure stability. Any company logos that were missing or outdated have been updated. Mar 17 , 04:36 UTC Update - 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 , 00:51 UTC 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 16 , 22:03 UTC Update - The failover steps for EU21 are nearing completion. A subset of customers have been enabled and we are monitoring carefully. Mar 16 , 19:25 UTC Update - We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process. Mar 16 , 17:19 UTC Update - We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process. Mar 16 , 15:15 UTC Update - We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process. Mar 16 , 12:49 UTC Update - We are still continuing to work through the failover steps for EU21. Mar 16 , 11:12 UTC Update - 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:03 UTC Update - 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 , 1
Users may encounter errors while attempting to upload or edit documents. (Incident 4504)
Mar 12 , 22:06 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Mar 12 , 21:41 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 12 , 20:49 UTC Update - We are continuing to work on a fix for this issue. We estimate the fix will be deployed by 22:30 UTC Mar 12 , 20:23 UTC Update - We are continuing to work on a fix for this issue. We estimate the fix will be deployed by 22:30 UTC Mar 12 , 19:23 UTC Identified - The issue has been identified and a fix is being implemented. Mar 12 , 18:15 UTC Investigating - We are currently investigating this issue.
A subset of Insight customers may experience issues accessing the Product (Incident 4480)
Mar 11 , 00:24 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Mar 10 , 23:21 UTC Update - We are continuing to monitor for any further issues. Mar 10 , 22:02 UTC Update - We are continuing to monitor for any further issues. Mar 10 , 21:04 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 10 , 20:15 UTC Update - We are continuing to work on a fix for this issue. Mar 10 , 18:49 UTC Identified - The issue has been identified and a fix is being implemented. Mar 10 , 18:11 UTC Update - Incident is actively being investigated. Mar 10 , 17:28 UTC Update - We are continuing to investigate this issue. Mar 10 , 16:58 UTC Update - We are continuing to investigate this issue. Mar 10 , 16:12 UTC Investigating - We are currently investigating this issue.
Users may experience delays or failures when attempting to upload documents via the MuleSoft API (incident 4455)
Mar 6 , 18:57 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Mar 6 , 18:49 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 6 , 17:37 UTC Identified - The issue has been identified and a fix is being implemented.
eSign Prod: Customers using Authorize.net to Include a One-Time Payment Request may experience issues completing envelopes (Incident 4445)
Mar 5 , 20:50 UTC Resolved - This incident has been resolved. Mar 5 , 16:41 UTC Update - Our team is working closely with the payment gateway to resolve the issue. We are monitoring the situation and will post an update here as soon as we receive one. Mar 4 , 23:22 UTC Update - We are continuing to investigate this issue. Mar 4 , 19:26 UTC Update - We are continuing to investigate this issue. Mar 4 , 18:45 UTC Investigating - We are currently investigating this issue.
Customers may experience latency when sending and signing (Incident 4392)
Feb 24 , 11:59 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Feb 24 , 10:04 UTC Investigating - We are currently investigating the issue.
A Subset of Customers May Experience Intermittent Latency When Sending or Receiving (Incident-4356)
Feb 17 , 15:51 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Feb 17 , 14:57 UTC Investigating - A subset of customers may be experiencing intermittent latency on executing send and receive jobs. Our engineering teams are engaged on this and are actively triaging.
Users may experience slowness and failures during content uploads and downloads (Incident 4352)
Feb 16 , 22:19 UTC Resolved - This incident has been resolved. Feb 16 , 21:50 UTC Identified - The issue has been identified and a fix is being implemented. Feb 16 , 21:26 UTC Investigating - We are currently investigating this issue.
Frequently Asked Questions
Is DocuSign down right now?
This page shows the real-time status of DocuSign. The status is checked automatically by pinging DocuSign's servers. If the status shows "Down", it means DocuSign is currently experiencing issues.
Why is DocuSign not working?
DocuSign may not be working due to server outages, scheduled maintenance, network issues, or high traffic. Check the current status above for real-time information.
How do I check if DocuSign is down for everyone?
BlueMonitor checks DocuSign's servers from our monitoring infrastructure. If the status shows "Down" here, it's likely down for everyone. If it shows "Up" but you can't access it, the issue may be on your end.
What should I do if DocuSign is down?
If DocuSign is down, you can: wait a few minutes and try again, check their official social media for updates, clear your browser cache, or try using a different network connection.