DocuSign Outage History
DocuSign degraded · 1 active incident View live status →Pingoru has recorded 137 incidents for DocuSign: 133 in the last 12 months and 30 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 7 | 13 of 720 (2%) |
| May 2026 | 14 | 48 of 744 (6%) |
| June 2026 | 23 | 219 of 720 (30%) |
| July 2026 | 17 | 88 of 744 (12%) |
| August 2026 | 13 | 30 of 744 (4%) |
| September 2026 | 8 | 43 of 720 (6%) |
| October 2026 | 10 | 21 of 744 (3%) |
| November 2026 | 0 | 23 of 23 (100%) |
Incidents, newest first
Major October 21, 2026 Signing and login unavailable for Docusign France customers (Incident 5945) – Trusted Service Provider (PROD)
Started Oct 21, 2026, 05:51 PM UTC· resolved Oct 21, 2026, 05:51 PM UTC
- resolved Oct 21, 2026, 05:51 PM UTC
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Minor October 21, 2026 Errors for templates, reports, envelope preparation and other features (Incident 6034) 2h 27m eSignature (AU)
Started Oct 21, 2026, 02:31 AM UTC· resolved Oct 21, 2026, 04:59 AM UTC
- investigating Oct 21, 2026, 02:31 AM UTC
We are actively investigating this issue.
- investigating Oct 21, 2026, 03:08 AM UTC
We are continuing to investigate this issue.
- monitoring Oct 21, 2026, 04:57 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 21, 2026, 04:59 AM UTC
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Minor October 20, 2026 Insight Customers Impacted by OCR Processing Issue (Incident 6027) 3h 31m Insight (EU.C), Insight (EU.N), Insight (EU.W), Insight (NA.C) and 3 more
Started Oct 20, 2026, 03:38 PM UTC· resolved Oct 20, 2026, 07:10 PM UTC
- identified Oct 20, 2026, 03:38 PM UTC
We are currently investigating an issue affecting Insights, where document import and OCR processing may be delayed or unavailable for some customers. The team is actively working to restore full service as quickly as possible.
- investigating Oct 20, 2026, 04:15 PM UTC
Our engineering team continues to investigate an issue affecting Insights, where document import and OCR processing may be delayed or unavailable for some customers.
- identified Oct 20, 2026, 04:57 PM UTC
The issue has been identified and we continue our work to implement a fix.
- identified Oct 20, 2026, 05:47 PM UTC
We continue to work to implement a fix for the issue.
- monitoring Oct 20, 2026, 06:16 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 20, 2026, 07:10 PM UTC
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Minor October 19, 2026 Customers may have experienced intermittent latency and disruption using eSign services (Incident 6014) – eSignature (NA1), eSignature (NA3), eSignature (NA4)
Started Oct 19, 2026, 11:23 PM UTC· resolved Oct 19, 2026, 11:23 PM UTC
- resolved Oct 19, 2026, 11:23 PM UTC
Between 08:36 PM and 10:11 PM UTC, some customers may have experienced intermittent latency and disruption with eSign services. The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Minor October 16, 2026 Errors for templates, reports, envelope preparation and other features (Incident 5994) – eSignature (AU)
Started Oct 16, 2026, 07:13 AM UTC· resolved Oct 16, 2026, 07:13 AM UTC
- resolved Oct 16, 2026, 07:13 AM UTC
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Customers may have seen errors when using and managing templates, reports, envelope preparation and other features from 2026-10-16 06:08 AM UTC until 2026-10-16 06:33 AM UTC.
Minor October 8, 2026 Errors for templates, reports, envelope preparation and other features (Incident 5932) 7h 10m eSignature (EU)
Started Oct 08, 2026, 09:28 AM UTC· resolved Oct 08, 2026, 04:39 PM UTC
- investigating Oct 08, 2026, 09:28 AM UTC
Customers may see errors when using and managing templates, reports, envelope preparation and other features. The issue is under investigation.
- identified Oct 08, 2026, 10:27 AM UTC
We have identified a potential cause of this issue and are deploying a fix.
- identified Oct 08, 2026, 12:58 PM UTC
We are continuing the analysis into this issue and have swarmed additional teams to triage.
- investigating Oct 08, 2026, 02:29 PM UTC
We are continuing to investigate the issue.
- monitoring Oct 08, 2026, 04:17 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 08, 2026, 04:39 PM UTC
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 with templates, reports, envelope preparation and other features from 2026-10-08 08:47 AM UTC until 2026-10-08 04:15 PM UTC
Minor October 7, 2026 Failures to grant users access to CLM in account admin (Incident 5922) 3h 53m CLM (EU11), CLM (EU21), CLM (NA11), CLM (NA21) and 7 more
Started Oct 07, 2026, 12:18 PM UTC· resolved Oct 07, 2026, 04:12 PM UTC
- investigating Oct 07, 2026, 12:18 PM UTC
Customers may see failures in account admin when granting users access to CLM. The issue is under investigation.
- monitoring Oct 07, 2026, 01:09 PM UTC
We have implemented a fix to resolve this issue and are currently monitoring telemetry to confirm mitigation.
- monitoring Oct 07, 2026, 01:39 PM UTC
We are seeing successes with our deployed fix, this will now be deployed sequentially to affected environments. We will update this status page as we progress.
- monitoring Oct 07, 2026, 02:57 PM UTC
All deployments have completed and we are now validating mitgation via telemetry
- resolved Oct 07, 2026, 04:12 PM UTC
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Notice October 2, 2026 CLM workflow update salesforce step latency (Incident 5893) 2d 2h CLM (NA11)
Started Oct 02, 2026, 03:40 PM UTC· resolved Oct 04, 2026, 06:16 PM UTC
- investigating Oct 02, 2026, 03:40 PM UTC
We are investigating the issue. Customers may encounter latency in the update salesforce step of CLM workflows.
- identified Oct 02, 2026, 05:49 PM UTC
Support times have identified the root cause of the latency and are continuing to troubleshoot in order to mitigate impact for affected users.
- identified Oct 02, 2026, 07:03 PM UTC
A fix was implemented and we are monitoring to ensure stability. Impact to customers is now mitigated.
- resolved Oct 04, 2026, 06:16 PM UTC
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-10-02 2:42:00 PM UTC until 2026-10-02 6:47:00 PM UTC.
Minor October 2, 2026 Customers may experience intermittent disruption logging in and using services (Incident 5888) 1h 54m CLM (US13)
Started Oct 02, 2026, 02:19 PM UTC· resolved Oct 02, 2026, 04:13 PM UTC
- investigating Oct 02, 2026, 02:19 PM UTC
We are investigating the issue.
- investigating Oct 02, 2026, 04:13 PM UTC
We are continuing to investigate this issue.
- resolved Oct 02, 2026, 04:13 PM UTC
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Notice September 30, 2026 Customers unable to access custom scripts following recent update (Incident 5878) 7d 3h eSignature (NA1)
Started Sep 30, 2026, 08:02 PM UTC· resolved Oct 07, 2026, 11:19 PM UTC
- investigating Sep 30, 2026, 08:02 PM UTC
A small subset of customer are reporting that they are unable to use their custom scripts following a recent update. We are actively investigating the issue and its cause.
- investigating Sep 30, 2026, 08:54 PM UTC
We are continuing to investigate this issue. Next update will occur at or before 3p PT/ 6p ET.
- investigating Sep 30, 2026, 10:02 PM UTC
We are continuing to investigate this issue. Next update will occur at or before 5p PT/ 8p ET.
- investigating Sep 30, 2026, 11:05 PM UTC
Support teams continue to investigate and have found that this issue impacted a smaller subset of customers than originally reported. Teams continue to troubleshoot and work with third parties to mitigate impact for affected users. Our next update will occur when a significant change in status has been confirmed.
- resolved Oct 07, 2026, 11:19 PM UTC
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. A small subset of customer may have been unable to use custom scripts from 2026-09-30 09:30 AM UTC until 2026-10-07 11:18 PM UTC.
Minor September 30, 2026 Some customers may experience issues with Salesforce Connect (Incident 5872) 6h 24m eSignature (USFED)
Started Sep 30, 2026, 12:21 AM UTC· resolved Sep 30, 2026, 06:46 AM UTC
- investigating Sep 30, 2026, 12:21 AM UTC
We are actively investigating this issue.
- investigating Sep 30, 2026, 01:09 AM UTC
We are continuing to investigate this issue.
- identified Sep 30, 2026, 01:14 AM UTC
We have identified the issue and a fix is being implemented.
- identified Sep 30, 2026, 02:10 AM UTC
The issue has been identified and we continue our work to implement a fix.
- identified Sep 30, 2026, 02:56 AM UTC
We continue to work to implement a fix for the issue.
- identified Sep 30, 2026, 06:05 AM UTC
We continue to work to implement a fix for the issue.
- monitoring Sep 30, 2026, 06:28 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 30, 2026, 06:46 AM UTC
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 with Salesforce Connect from 2026-09-21 12:00 AM UTC until 2026-09-30 06:45 AM UTC.
Minor September 28, 2026 Email Delivery Failures impacting customers (Incident 5861) 1d 7h eSignature (DEMO), eSignature (AU), eSignature (CA), eSignature (EU) and 5 more
Started Sep 28, 2026, 06:08 PM UTC· resolved Sep 30, 2026, 01:37 AM UTC
- identified Sep 28, 2026, 06:08 PM UTC
Docusign is working with third parties to unblock email delivery for customers.
- investigating Sep 28, 2026, 06:31 PM UTC
We continue to work to mitigate this issue.
- identified Sep 28, 2026, 07:07 PM UTC
Docusign continues to work with third parties to unblock email delivery for customers.
- identified Sep 28, 2026, 07:41 PM UTC
Docusign is continuing to work with third parties to unblock email delivery for customers.
- identified Sep 28, 2026, 08:08 PM UTC
Docusign is continuing to work with third parties to unblock email delivery for customers.
- identified Sep 28, 2026, 08:45 PM UTC
Docusign is continuing to work to unblock email delivery for customers.
- identified Sep 28, 2026, 09:14 PM UTC
Docusign is continuing to work to unblock email delivery for customers.
- identified Sep 28, 2026, 09:52 PM UTC
Docusign is continuing mitigation work to unblock email delivery for customers.
- identified Sep 28, 2026, 10:28 PM UTC
Support teams have identified a potential root cause and we are in the process of implementing a fix to alleviate customer impact.
- identified Sep 28, 2026, 10:58 PM UTC
Support teams continue to work on implementing a fix to alleviate customer impact.
- identified Sep 28, 2026, 11:35 PM UTC
Support teams continue to implement a fix for this issue and we are monitoring the results.
- identified Sep 29, 2026, 12:08 AM UTC
A fix is in progress and we are monitoring the results.
- identified Sep 29, 2026, 12:43 AM UTC
A fix is in progress and we are continuing to monitor the results.
- identified Sep 29, 2026, 01:18 AM UTC
A fix is in progress and we are continuing to monitor the results.
- identified Sep 29, 2026, 01:42 AM UTC
Support teams have confirmed that a fix is in place and that they will continue to monitor recovery through the evening.
- identified Sep 29, 2026, 09:44 AM UTC
Support teams are continuing to monitor recovery. The next update will be posted at 4pm UTC (9am PT).
- identified Sep 29, 2026, 04:14 PM UTC
Mitigation steps have successfully resolved the issue for a large group of customers. We're continuing to work with third parties to resolve issues for the remaining affected customers. Our next update will be at 11a PT / 2p ET.
- identified Sep 29, 2026, 06:04 PM UTC
Docusign is continuing to work with third parties to resolve issues for the remaining affected customers.
- identified Sep 29, 2026, 06:05 PM UTC
Docusign is continuing to work with third parties to resolve issues for the remaining affected customers. Our next update will be at 12p PT / 3p ET.
- identified Sep 29, 2026, 07:00 PM UTC
Docusign is continuing to see recovery improvements for affected customers. We continue to work with third parties to resolve issues for outstanding customer issues. Our next update will be at 1p PT / 4p ET.
- identified Sep 29, 2026, 08:06 PM UTC
Docusign is seeing continued improvements for remaining affected customers and continues to work with third parties toward resolution. Our next update will be at 2p PT / 5p ET.
- identified Sep 29, 2026, 09:23 PM UTC
Docusign is seeing continued improvements for remaining affected customers and continues to work with third parties toward resolution. Our next update will be at 4p PT / 7p ET, or earlier if a significant change in status occurs.
- identified Sep 29, 2026, 11:06 PM UTC
We have taken additional steps to improve the experience for affected customers and continue to work with third parties toward resolution. Our next update will be at 6p PT / 9p ET, or earlier if a significant change in status occurs.
- resolved Sep 30, 2026, 01:36 AM UTC
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-09-25 13:00:00 UTC until 2026-09-30 00:15 UTC. Any customers experiencing residual issues from this issue are encouraged to reach out to support for additional assistance.
Notice September 16, 2026 Customers may be impacted by a disruption to Salesforce (Incident 5788) 8h 36m CLM (DEMO S1), CLM (EU21), CLM (NA11), CLM (NA21) and 4 more
Started Sep 16, 2026, 09:45 AM UTC· resolved Sep 16, 2026, 06:21 PM UTC
- investigating Sep 16, 2026, 09:45 AM UTC
Customers may experience intermittent latency and connection issues with Salesforce integrations. Additionally, customers may also experience difficulty contacting Docusign Support or viewing our support pages. Docusign services remain functional and are performing as intended. Please refer to the Salesforce Trust site for additional information: https://status.salesforce.com/incidents/20004433
- identified Sep 16, 2026, 12:00 PM UTC
Salesforce are rolling out a fix. Please refer to the Salesforce Trust site for additional information: https://status.salesforce.com/incidents/20004433
- monitoring Sep 16, 2026, 04:35 PM UTC
Salesforce has implemented a fix and are monitoring the results. Please refer to the Salesforce Trust site for additional information: https://status.salesforce.com/incidents/20004433
- monitoring Sep 16, 2026, 05:40 PM UTC
Salesforce is continuing to monitor the results. Please refer to the Salesforce Trust site for additional information: https://status.salesforce.com/incidents/20004433
- resolved Sep 16, 2026, 06:21 PM UTC
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Please refer to the Salesforce Trust site for additional information: https://status.salesforce.com/incidents/20004433 Customers may have experienced issues (resulting from the Salesforce disruption) from 2026-09-16 07:50 A:M UTC until 2026-09-16 16:23 PM UTC.
Minor September 9, 2026 Some users were unable to preview documents (Incident 5749) 2h 3m CLM (NA11)
Started Sep 09, 2026, 10:06 PM UTC· resolved Sep 10, 2026, 12:10 AM UTC
- investigating Sep 09, 2026, 10:06 PM UTC
Support teams are engaged and currently investigating reports of customers being unable to preview documents.
- identified Sep 09, 2026, 11:19 PM UTC
Teams have identified what they believe to be the root cause of the issue and are putting mitigation steps in play to mitigate impact for affected customers.
- monitoring Sep 09, 2026, 11:44 PM UTC
Support teams have confirmed that mitigation steps were successful and customer impact has been mitigated. Teams are now monitoring performance.
- resolved Sep 10, 2026, 12:10 AM UTC
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 previewing documents from 2026-09-09 18:42 PM UTC until 2026-09-10 23:03 PM UTC.
Minor September 9, 2026 High latency affecting send and sign across production environments (Incident 5741) 1h 56m eSignature (NA1), eSignature (NA2), eSignature (NA3), eSignature (NA4)
Started Sep 09, 2026, 01:52 AM UTC· resolved Sep 09, 2026, 03:49 AM UTC
- investigating Sep 09, 2026, 01:52 AM UTC
We are currently investigating high latency affecting the Signing API across production environments NA1, NA2, NA3, and NA4. Teams are engaged and investigating recent deployments to determine if a rollback is possible for mitigation.
- investigating Sep 09, 2026, 02:32 AM UTC
Teams are now investigating the settings-service while working on a forward fix and root cause investigation, in parallel. We have seen a decrease in latency for impacted customers, however both send and sign are still in a degraded state.
- resolved Sep 09, 2026, 03:49 AM UTC
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Customers may have experienced elevated latency and errors from 2026-09-09 00:42 AM UTC until 2026-09-09 03:12 AM UTC.
Minor September 7, 2026 CLM workflow and expression evaluation degradation and failures (Incident 5734) 1h 29m CLM (NA21)
Started Sep 07, 2026, 12:18 AM UTC· resolved Sep 07, 2026, 01:48 AM UTC
- investigating Sep 07, 2026, 12:18 AM UTC
We are investigating the issue. Some customers may experience degradation and failures in CLM workflow and expression evaluation.
- identified Sep 07, 2026, 12:57 AM UTC
We have identified the issue and are implementing a fix.
- resolved Sep 07, 2026, 01:48 AM UTC
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-09-06 11:17 PM UTC until 2026-09-07 01:34 PM UTC.
Minor September 4, 2026 Intermittent login and API failures (Incident 5729) 41m eSignature (AU), eSignature (JP1)
Started Sep 04, 2026, 08:41 AM UTC· resolved Sep 04, 2026, 09:23 AM UTC
- investigating Sep 04, 2026, 08:41 AM UTC
We are investigating the issue.
- resolved Sep 04, 2026, 09:23 AM UTC
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Customers may have experienced Intermittent login and API failures from 2026-09-04 06:15 AM UTC until 2026-09-04 08:36 AM UTC.
Minor August 31, 2026 UI Latency Issues (Incident 5692) 1h 22m CLM (S1.EU)
Started Aug 31, 2026, 04:06 PM UTC· resolved Aug 31, 2026, 05:29 PM UTC
- investigating Aug 31, 2026, 04:06 PM UTC
Customers may be experiencing latency when loading the CLM UI in S1.EU. We are actively investigating this issue.
- investigating Aug 31, 2026, 04:45 PM UTC
We are continuing to investigate this issue.
- resolved Aug 31, 2026, 05:29 PM UTC
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Customers may have experienced increased latency and delays from 2026-08-31 03:15 PM UTC until 2026-08-31 04:56 PM UTC.
Minor August 27, 2026 Slow performance and delays for Agreement Manager, CLM, and eSign (Incident 5674) 2h 9m eSignature (AU), eSignature (CA)
Started Aug 27, 2026, 11:39 PM UTC· resolved Aug 28, 2026, 01:49 AM UTC
- investigating Aug 27, 2026, 11:39 PM UTC
We are investigating delays across the site.
- identified Aug 28, 2026, 12:04 AM UTC
We have identified the underlying cause and are working to implement a fix.
- identified Aug 28, 2026, 12:25 AM UTC
The issue has been identified and we continue our work to implement a fix.
- monitoring Aug 28, 2026, 01:27 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 28, 2026, 01:49 AM UTC
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-27 11:27 PM UTC until 2026-08-28 01:18 AM UTC.
Notice August 27, 2026 New Docusign Status Center: Subscribe by September 1 to Receive Updates 28s PROD, Headquarters, DEMO, North Central and 44 more
Started Aug 27, 2026, 10:07 PM UTC· resolved Aug 27, 2026, 10:07 PM UTC
- investigating Aug 27, 2026, 10:07 PM UTC
On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US
- resolved Aug 27, 2026, 10:07 PM UTC
This incident has been resolved.
Notice August 24, 2026 Issues in JP1 with Salesforce Writeback (Incident 5648) 6h 8m eSignature (JP1)
Started Aug 24, 2026, 10:10 AM UTC· resolved Aug 24, 2026, 04:19 PM UTC
- investigating Aug 24, 2026, 10:10 AM UTC
Customers in JP1 may experience issues when writing back to Salesforce after signing a document. Engineering teams are engaged and are actively triaging this issue.
- resolved Aug 24, 2026, 04:19 PM UTC
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-22 05:44 PM UTC until 2026-08-24 02:55 PM UTC.
Minor August 12, 2026 Document Upload and Generation Errors (Incident 5595) 40m eSignature (DEMO)
Started Aug 12, 2026, 11:21 PM UTC· resolved Aug 13, 2026, 12:01 AM UTC
- investigating Aug 12, 2026, 11:21 PM UTC
We are actively investigating this issue.
- investigating Aug 12, 2026, 11:25 PM UTC
We are continuing to investigate this issue.
- monitoring Aug 12, 2026, 11:47 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 13, 2026, 12:01 AM UTC
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
- resolved Aug 19, 2026, 08:31 PM UTC
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-12 10:20 PM UTC until 2026-08-12 11:39 PM UTC.
Minor August 11, 2026 Degraded Task Processing and Latency across multiple services (Incident 5576) 13h 34m CLM (NA11)
Started Aug 11, 2026, 01:14 PM UTC· resolved Aug 12, 2026, 02:49 AM UTC
- investigating Aug 11, 2026, 01:14 PM UTC
We are currently investigating issues where some customers may see latency or failures when generating documents. Engineering teams have been engaged and are actively triaging.
- investigating Aug 11, 2026, 02:42 PM UTC
We are continuing to investigate this issue.
- investigating Aug 11, 2026, 04:12 PM UTC
We continue to investigate the issue and additional resources have been engaged.
- identified Aug 11, 2026, 05:08 PM UTC
We have identified the issue and a fix is being implemented.
- identified Aug 11, 2026, 05:58 PM UTC
The issue has been identified and we continue our work to implement a fix.
- monitoring Aug 11, 2026, 06:17 PM UTC
A fix has been implemented and we are monitoring the results.
- identified Aug 11, 2026, 06:54 PM UTC
Our initial fix did not fully mitigate this issue. Our teams are continuing to work to implement a fix to resolve the issue.
- identified Aug 11, 2026, 07:49 PM UTC
We continue to work to implement a fix for the issue.
- monitoring Aug 11, 2026, 09:09 PM UTC
We continue to monitor the environment to ensure stability.
- monitoring Aug 12, 2026, 12:16 AM UTC
We continue to monitor the environment to ensure stability.
- resolved Aug 12, 2026, 02:49 AM UTC
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-11 12:05 PM UTC until 2026-08-12 02:50 AM UTC.
Minor August 11, 2026 Login Issues in certain regions (Incident 5572) 2h 1m eSignature (AU), eSignature (CA), eSignature (EU), eSignature (JP1) and 4 more
Started Aug 11, 2026, 04:49 AM UTC· resolved Aug 11, 2026, 06:50 AM UTC
- investigating Aug 11, 2026, 04:49 AM UTC
Some customers may be experiencing issues when attempting to sign in to Docusign in the AU region. Engineering teams have been engaged and we are actively triaging this issue.
- identified Aug 11, 2026, 05:01 AM UTC
Our engineering teams have identified the potential cause of this issue and we are in the process of deploying a fix.
- monitoring Aug 11, 2026, 05:46 AM UTC
Our engineering teams have deployed a fix to the affected environments and we are monitoring our telemetry to validate.
- resolved Aug 11, 2026, 06:50 AM UTC
Further monitoring has concluded that the fix implemented by our engineering teams has resolved this incident.
- resolved Sep 17, 2026, 12:38 AM UTC
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-11 04:00 AM UTC until 2026-08-11 06:58 AM UTC.
Notice August 7, 2026 Latency and Errors Across NA11 (Incident 5558) 1h 14m CLM (NA11)
Started Aug 07, 2026, 04:59 PM UTC· resolved Aug 07, 2026, 06:13 PM UTC
- identified Aug 07, 2026, 04:59 PM UTC
Customers across NA11 are seeing latency and delays across the service. We have identified the underlying issue and are taking action to mitigate the issue.
- monitoring Aug 07, 2026, 05:36 PM UTC
A fix has been implemented and we are monitoring the results.
- identified Aug 07, 2026, 05:37 PM UTC
The issue has been identified and we continue our work to implement a fix.
- monitoring Aug 07, 2026, 05:55 PM UTC
The fix was implemented and we are monitoring to ensure stability.
- resolved Aug 07, 2026, 06:13 PM UTC
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
- monitoring Aug 07, 2026, 07:33 PM UTC
Customers may experience delays while the backlog is cleared.
- monitoring Aug 07, 2026, 09:39 PM UTC
We continue to monitor the environment and optimize traffic handling. Customers should see normal performance at this time.
- monitoring Aug 07, 2026, 09:39 PM UTC
We continue to monitor the environment to ensure stability.
- resolved Aug 07, 2026, 10:12 PM UTC
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-07 1:13 PM UTC until 2026-08-07 09:51 PM UTC.