Aug 31, 17:29 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Aug 31, 16:45 UTC Update - We are continuing to investigate this issue. Aug 31, 16:06 UTC Investigating - Customers may be experiencing latency when loading the CLM UI in S1.EU. We are actively investigating this issue.
Aug 28, 01:49 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 errors from 2026-08-27 11:27 PM UTC until 2026-08-28 01:18 AM UTC. Aug 28, 01:27 UTC Monitoring - A fix has been implemented and we are monitoring the results. Aug 28, 00:25 UTC Update - The issue has b…
Aug 27, 22:07 UTC Resolved - This incident has been resolved. Aug 27, 22:07 UTC Investigating - 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
Aug 24, 16:19 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Aug 24, 10:10 UTC Investigating - 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.
Aug 13, 00:01 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Aug 12, 23:47 UTC Monitoring - A fix has been implemented and we are monitoring the results. Aug 12, 23:25 UTC Update - We are continuing to investigate this issue. Aug 12, 23:21 UTC Investigating - We are actively investigating this…
Aug 12, 02:49 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Aug 12, 00:16 UTC Update - We continue to monitor the environment to ensure stability. Aug 11, 21:09 UTC Monitoring - We continue to monitor the environment to ensure stability. Aug 11, 19:49 UTC Update - We continue to work to imple…
Aug 11, 06:50 UTC Resolved - Further monitoring has concluded that the fix implemented by our engineering teams has resolved this incident. Aug 11, 05:46 UTC Monitoring - Our engineering teams have deployed a fix to the affected environments and we are monitoring our telemetry to validate. Aug 11, 05:01 UTC Identified - Our engineering teams have identified the potential cause of this issue and we…
Aug 7, 18:13 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Aug 7, 17:55 UTC Monitoring - The fix was implemented and we are monitoring to ensure stability. Aug 7, 17:37 UTC Identified - The issue has been identified and we continue our work to implement a fix. Aug 7, 17:36 UTC Monitoring - A…
Aug 6, 21:23 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Aug 6, 21:04 UTC Monitoring - A fix has been implemented and we are monitoring the results. Aug 6, 20:43 UTC Update - The issue has been identified and we continue our work to implement a fix. Aug 6, 20:14 UTC Identified - We have ide…
Aug 5, 21:09 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Aug 5, 20:42 UTC Monitoring - A fix has been implemented and we are monitoring the results. Aug 5, 20:41 UTC Identified - We have identified the issue and a fix is being implemented. Aug 5, 20:11 UTC Update - We continue to investigat…
Aug 5, 04:42 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Aug 5, 04:39 UTC Monitoring - A fix has been implemented and we are monitoring the results. Aug 5, 04:20 UTC Update - The issue has been identified and we continue our work to implement a fix. Aug 5, 03:14 UTC Identified - We have ide…
Aug 4, 16:00 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Aug 4, 15:47 UTC Monitoring - A fix has been implemented and we are monitoring the results. Aug 4, 15:10 UTC Identified - We have identified the issue and a fix is being implemented. Aug 4, 14:30 UTC Update - We are continuing to inve…
Aug 3, 20:44 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Aug 3, 20:26 UTC Monitoring - A fix has been implemented and we are monitoring the results. Aug 3, 20:07 UTC Investigating - We are actively investigating this issue.
Jul 31, 18:01 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 errors from 2026-07-29 01:43 AM UTC until 2026-07-31 05:14 PM UTC. Jul 31, 17:51 UTC Update - The issue has been identified and we continue our work to implement a fix. Jul 31, 17:33 UTC Identified - We…
Jul 30, 21:02 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Jul 30, 20:32 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jul 30, 20:11 UTC Identified - We have identified the issue and a fix is being implemented. Jul 30, 19:53 UTC Investigating - We are activel…
Jul 30, 20:34 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 errors from 2026-07-30 06:14 PM UTC until 2026-07-30 07:47 PM UTC. Jul 30, 19:57 UTC Identified - We have identified the issue and a fix is being implemented. Jul 30, 19:32 UTC Update - We are continuing…
Jul 27, 18:43 UTC Resolved - 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. As part of this transition, Slack, SMS, and RSS notification methods will be deprecated and will no longer be supported on the new platform.To ensure you continue receiving system status alerts after this date, you wil…
Jul 27, 18:13 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Jul 27, 10:45 UTC Identified - Customers may be experiencing issues when attempting qualified verifications. Engineering teams have been engaged and are actively triaging this issue.
Jul 27, 16:11 UTC Investigating - We are actively investigating this issue.
Jul 23, 22:30 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Jul 23, 21:45 UTC Update - AU and JP are stable at present. Teams are continuing to investigate the issue. Jul 23, 21:07 UTC Update - We are continuing to investigate this issue. Jul 23, 20:59 UTC Investigating - We are actively inve…
Jul 22, 21:15 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 errors from 2026-07-22 05:24 PM UTC until 2026-07-22 09:15 PM UTC. Jul 22, 20:59 UTC Update - The issue has been identified and we continue our work to implement a fix. Jul 22, 20:10 UTC Identified - We…
Jul 17, 17:54 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 errors from 2026-07-17 03:55 PM UTC until 2026-07-17 05:57 PM UTC. Jul 17, 17:46 UTC Identified - We have identified the issue and a fix is being implemented. Jul 17, 17:33 UTC Investigating - We are ac…
Jul 16, 03:33 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Jul 16, 03:27 UTC Identified - We have identified the issue and a fix is being implemented. Jul 16, 03:27 UTC Investigating - We are actively investigating this issue.
Jul 15, 01:49 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Jul 14, 23:32 UTC Identified - We have identified the issue and a fix is being implemented. Jul 14, 21:41 UTC Update - We are continuing to investigate this issue. Jul 14, 20:48 UTC Investigating - We are actively investigating this…
Jul 14, 19:08 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Jul 14, 19:05 UTC Monitoring - LexisNexis has reported resolving the issue. We are continuing to monitor. Jul 14, 18:39 UTC Update - LexisNexis is continuing to investigate the issue. Jul 14, 17:44 UTC Update - LexisNexis is continui…
Jul 13, 20:19 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Jul 13, 19:55 UTC Identified - We have identified the issue and a fix is being implemented.
Jul 9, 17:22 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Jul 8, 15:50 UTC Update - 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 wil…
Jul 8, 21:47 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Jul 8, 21:46 UTC Investigating - We are actively investigating this issue.
Jul 7, 16:48 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Jul 7, 15:31 UTC 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…
Jul 5, 23:01 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 errors from 2026-07-05 21:50 UTC until 2026-07-05 22:22 UTC. Jul 5, 22:50 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jul 5, 22:35 UTC Investigating - We are actively in…