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…
Jul 1, 17:25 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Jul 1, 14:57 UTC Identified - We have identified the issue and a fix is being implemented. Jul 1, 00:57 UTC Update - We continue to investigate the issue and additional resources have been engaged. We will provide the next update in a…
Jun 30, 20:53 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. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US
Jun 30, 00:37 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Jun 30, 00:26 UTC Identified - We have identified the issue and a fix is being implemented. Jun 30, 00:25 UTC Investigating - We are actively investigating this issue.
Jun 29, 22:00 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Jun 29, 21:34 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 29, 21:34 UTC Update - We are continuing to investigate this issue. Jun 29, 21:32 UTC Investigating - We are actively investigating this…
Jun 29, 18:36 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Jun 29, 18:23 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 29, 17:51 UTC Update - We continue to work to implement a fix for the issue. Jun 29, 17:16 UTC Update - The issue has been identified an…
Jun 29, 17:29 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Jun 29, 17:06 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 29, 16:47 UTC Update - We continue to investigate the issue and additional resources have been engaged. Jun 29, 16:10 UTC Update - We ar…
Jun 28, 07:47 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Jun 28, 06:58 UTC Identified - We have identified the issue and a fix is being implemented. Jun 28, 06:49 UTC Investigating - We are actively investigating this issue.
Jun 26, 20:13 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Jun 26, 19:02 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 26, 18:06 UTC Identified - We have identified the issue and a fix is being implemented.
Jun 25, 22:29 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Jun 25, 20:57 UTC Identified - We have identified the issue and a fix is being implemented. Jun 25, 20:36 UTC Update - We are continuing to investigate this issue. Jun 25, 20:12 UTC Investigating - We are actively investigating this…
Jun 25, 19:07 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Jun 24, 13:15 UTC Update - The fix is still in progress and being deployed. We will provide an update upon resolution. Jun 18, 22:43 UTC Identified - An issue has been identified where documents downloaded via archived ZIP files with…
Jun 25, 13:01 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Jun 25, 10:27 UTC Monitoring - Fix has been implemented and we are now monitoring telemetry to validate. Jun 25, 10:12 UTC Identified - We have identified the source of the issue and are preparing a fix. Jun 25, 08:44 UTC Investigati…
Jun 17, 23:26 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Jun 17, 22:58 UTC Update - We continue to monitor the environment to ensure stability. Jun 17, 20:41 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 17, 19:28 UTC Investigating - We are actively inv…
Jun 16, 23:30 UTC Resolved - The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Jun 16, 22:01 UTC Update - We are continuing to work on a fix for this issue. Jun 16, 22:00 UTC Identified - We have identified the issue and a fix is being implemented. Jun 16, 20:46 UTC Update - We continue to investigate the issue…