DocuSign Outage History
DocuSign is up right nowPingoru has recorded 136 incidents for DocuSign: 133 in the last 12 months and 36 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 | 37 of 744 (5%) |
| September 2026 | 8 | 55 of 720 (8%) |
| October 2026 | 9 | 181 of 562 (32%) |
Incidents, newest first
Minor June 29, 2026 Customers may see increased latency when sending and signing and intermittent errors (Incident 5232) 3h 4m eSignature (NA1), eSignature (NA2), eSignature (NA3), eSignature (NA4) and 4 more
Started Jun 29, 2026, 03:30 PM UTC· resolved Jun 29, 2026, 06:35 PM UTC
- investigating Jun 29, 2026, 03:30 PM UTC
We are actively investigating this issue.
- investigating Jun 29, 2026, 05:05 PM UTC
We are continuing to investigate this issue.
- identified Jun 29, 2026, 05:07 PM UTC
We have identified the issue and a fix is being implemented.
- identified Jun 29, 2026, 05:16 PM UTC
The issue has been identified and we continue our work to implement a fix.
- identified Jun 29, 2026, 05:51 PM UTC
We continue to work to implement a fix for the issue.
- monitoring Jun 29, 2026, 06:23 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 29, 2026, 06:35 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 latency and intermittent errors when sending and signing from 2026-06-29 08:18 AM UTC until 2026-06-29 06:05 PM UTC.
Minor June 28, 2026 Intermittent Errors and Delays (Incident 5219) 57m CLM (NA11), CLM (NA21)
Started Jun 28, 2026, 06:49 AM UTC· resolved Jun 28, 2026, 07:47 AM UTC
- investigating Jun 28, 2026, 06:49 AM UTC
We are actively investigating this issue.
- identified Jun 28, 2026, 06:58 AM UTC
We have identified the issue and a fix is being implemented.
- resolved Jun 28, 2026, 07:47 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-06-28 04:10 UTC until 2026-06-28 06:56 AM UTC.
Minor June 26, 2026 Some customers may experience latency for any sending actions that involve conversions, generating documents and accessing tasks (Incident 5190) 2h 6m eSignature (NA2), eSignature (NA4), CLM (NA11), CLM (NA21) and 1 more
Started Jun 26, 2026, 06:06 PM UTC· resolved Jun 26, 2026, 08:13 PM UTC
- identified Jun 26, 2026, 06:06 PM UTC
We have identified the issue and a fix is being implemented.
- monitoring Jun 26, 2026, 07:02 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 26, 2026, 08:13 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 latency for any sending actions involving conversions, generating documents and accessing tasks from 2026-06-25 07:36 PM UTC until 2026-06-25 10:29 PM UTC.
Minor June 25, 2026 Platform Latency in UAT (Incident 5187) 4h 16m CLM (UAT NA11)
Started Jun 25, 2026, 08:44 AM UTC· resolved Jun 25, 2026, 01:01 PM UTC
- investigating Jun 25, 2026, 08:44 AM UTC
Customers may be experiencing latency on the platform in the UAT Environment. Engineers have been engaged and are actively triaging this issue.
- identified Jun 25, 2026, 10:12 AM UTC
We have identified the source of the issue and are preparing a fix.
- monitoring Jun 25, 2026, 10:27 AM UTC
Fix has been implemented and we are now monitoring telemetry to validate.
- resolved Jun 25, 2026, 01:01 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 issues from 2026-06-25 05:33 AM UTC until 2026-06-25 10:38 AM UTC.
Minor June 18, 2026 Users downloading archived document ZIP files may see missing official Docusign platform seals (Incident 5139) 6d 20h eSignature (DEMO), eSignature (AU), eSignature (CA), eSignature (EU) and 7 more
Started Jun 18, 2026, 10:43 PM UTC· resolved Jun 25, 2026, 07:07 PM UTC
- identified Jun 18, 2026, 10:43 PM UTC
An issue has been identified where documents downloaded via archived ZIP files with "masked fields" enabled are missing their Docusign platform seals. A fix is underway. We will provide an update upon resolution. Target Fix Date: June 23, 2026 Temporary Workaround: Download documents individually rather than as an archived ZIP file to ensure platform seals are successfully applied.
- identified Jun 24, 2026, 01:15 PM UTC
The fix is still in progress and being deployed. We will provide an update upon resolution.
- resolved Jun 25, 2026, 07:07 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 issues from 2026-06-18 03:05 PM UTC until 2026-06-25 07:05 PM UTC.
Minor June 17, 2026 Salesforce for Gen customers may be unable to generate documents (Incident 5132) 3h 57m CLM (S1.US), CLM (S2.US)
Started Jun 17, 2026, 07:28 PM UTC· resolved Jun 17, 2026, 11:26 PM UTC
- investigating Jun 17, 2026, 07:28 PM UTC
We are actively investigating this issue.
- monitoring Jun 17, 2026, 08:41 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Jun 17, 2026, 10:58 PM UTC
We continue to monitor the environment to ensure stability.
- resolved Jun 17, 2026, 11:26 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 issues from 2026-06-17 07:03 PM UTC until 2026-06-17 11:27 PM UTC.
Minor June 16, 2026 Salesforce for Gen customers are unable to generate documents (Incident-5122) 6h 37m
Started Jun 16, 2026, 04:52 PM UTC· resolved Jun 16, 2026, 11:30 PM UTC
- investigating Jun 16, 2026, 04:52 PM UTC
We are actively investigating this issue.
- investigating Jun 16, 2026, 04:54 PM UTC
We are continuing to investigate this issue.
- investigating Jun 16, 2026, 05:59 PM UTC
We continue to investigate the issue and additional resources have been engaged.
- investigating Jun 16, 2026, 06:28 PM UTC
We continue to investigate the issue and additional resources have been engaged.
- investigating Jun 16, 2026, 08:46 PM UTC
We continue to investigate the issue and additional resources have been engaged.
- identified Jun 16, 2026, 10:00 PM UTC
We have identified the issue and a fix is being implemented.
- resolved Jun 16, 2026, 11:30 PM UTC
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Salesforce for Gen customers were unable to generate documents from 2026-06-16 2:52 PM UTC until 2026-06-16 11:21 PM UTC.
Minor June 16, 2026 Customers may experience intermittent latency (Incident 5118) 8h 41m CLM (UAT NA11)
Started Jun 16, 2026, 08:37 AM UTC· resolved Jun 16, 2026, 05:18 PM UTC
- investigating Jun 16, 2026, 08:37 AM UTC
We are actively investigating this issue.
- investigating Jun 16, 2026, 10:34 AM UTC
We are continuing to investigate this issue.
- investigating Jun 16, 2026, 03:20 PM UTC
We continue to investigate the issue. Performance has improved but the issue is still under investigation.
- resolved Jun 16, 2026, 05:18 PM UTC
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
- resolved Jun 16, 2026, 05:24 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 issues from 2026-06-16 03:00 AM UTC until 2026-06-16 05:26 PM UTC.
Minor June 15, 2026 Users may experience performance latency when utilizing document conversion (Incident 5085) 1h 4m eSignature (AU), eSignature (CA), eSignature (NA1), eSignature (NA2)
Started Jun 15, 2026, 05:24 PM UTC· resolved Jun 15, 2026, 06:29 PM UTC
- identified Jun 15, 2026, 05:24 PM UTC
We are have identified the root cause and we are implementing a fix.
- resolved Jun 15, 2026, 06: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 issues from 2026-06-12 01:15 AM UTC until 2026-06-15 06:30 PM UTC.
Minor June 15, 2026 Email notifications sent from custom domains were delayed (Incident 5106) 50m eSignature (DEMO), CLM (DEMO S1), CLM (UAT NA11)
Started Jun 15, 2026, 02:00 PM UTC· resolved Jun 15, 2026, 02:51 PM UTC
- investigating Jun 15, 2026, 02:00 PM UTC
We are actively investigating the issue.
- resolved Jun 15, 2026, 02:51 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 issues from 2026-06-15 3:30 AM UTC until 2026-05-15 1:30 PM UTC.
Minor June 12, 2026 Notification failures when utilising Outlook (Incident 5087) 32m eSignature (AU), eSignature (CA), eSignature (EU), eSignature (JP1) and 4 more
Started Jun 12, 2026, 06:04 AM UTC· resolved Jun 12, 2026, 06:37 AM UTC
- investigating Jun 12, 2026, 06:04 AM UTC
Customers utilising Outlook may receive delivery notification failures when sending envelopes to signers. Engineering teams have been engaged and we are actively triaiging this issue.
- monitoring Jun 12, 2026, 06:10 AM UTC
A fix has been applied and our engineering teams are actively reviewing our telemetry to confirm this fix has mitigated the issue.
- resolved Jun 12, 2026, 06:37 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-06-12 02:52 AM UTC until 2026-06-12 05:43 AM UTC.
Notice June 11, 2026 Users may encounter errors when attempting to process envelopes (Incident 5072) 2h 4m eSignature (DEMO)
Started Jun 11, 2026, 07:45 PM UTC· resolved Jun 11, 2026, 09:50 PM UTC
- investigating Jun 11, 2026, 07:45 PM UTC
We are investigating this issue.
- resolved Jun 11, 2026, 09:50 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-06-11 06:12 PM UTC until 2026-06-11 09:28 PM UTC.
Minor June 11, 2026 Document Upload and Generation Errors (Incident 5073) 4h 17m eSignature (NA2), eSignature (NA4), CLM (NA11), CLM (NA21) and 1 more
Started Jun 11, 2026, 07:03 PM UTC· resolved Jun 11, 2026, 11:21 PM UTC
- investigating Jun 11, 2026, 07:03 PM UTC
We are actively investigating this issue.
- investigating Jun 11, 2026, 07:49 PM UTC
We are continuing to investigate this issue.
- investigating Jun 11, 2026, 08:19 PM UTC
We continue to investigate the issue and additional resources have been engaged.
- investigating Jun 11, 2026, 08:34 PM UTC
We continue to investigate the issue and additional resources have been engaged.
- investigating Jun 11, 2026, 09:52 PM UTC
We continue to investigate the issue.
- identified Jun 11, 2026, 10:05 PM UTC
We have identified the issue and a fix is being implemented.
- monitoring Jun 11, 2026, 10:13 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 11, 2026, 11:21 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-06-11 06:35 PM UTC until 2026-06-11 10:52 PM UTC.
Minor June 5, 2026 CLM: Resolved Authentication/Access Issues in EU11 (Incident 5040) – CLM (EU11)
Started Jun 05, 2026, 11:03 PM UTC· resolved Jun 05, 2026, 11:03 PM UTC
- resolved Jun 05, 2026, 11:03 PM UTC
An unexpected system dependency caused a temporary service disruption affecting a subset of accounts in the CLM EU11 environment between 21:09 UTC and 22:40 UTC on June 5, 2026. During this time, impacted users may have experienced authentication errors or issues accessing certain features. 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-06-05 21:09 UTC until 2026-06-05 22:40 UTC
Minor June 5, 2026 Customers Unable to Purchase Plans (Incident 5034) 29m
Started Jun 05, 2026, 10:02 PM UTC· resolved Jun 05, 2026, 10:32 PM UTC
- investigating Jun 05, 2026, 10:02 PM UTC
We are actively investigating this issue.
- identified Jun 05, 2026, 10:15 PM UTC
We have identified the issue and a fix is being implemented.
- monitoring Jun 05, 2026, 10:22 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 05, 2026, 10:32 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-06-05 09:05 PM UTC until 2026-06-05 10:20 PM UTC.
Minor June 4, 2026 Reports May Remain in "Exporting" Status (Incident 5020) 5h 1m eSignature (DEMO), eSignature (AU), eSignature (CA), eSignature (EU) and 5 more
Started Jun 04, 2026, 06:58 AM UTC· resolved Jun 04, 2026, 12:00 PM UTC
- identified Jun 04, 2026, 06:58 AM UTC
Customers may be experiencing issues when attempting to export reports. Our engineering teams are engaged and have identified the cause and are working on a fix for this.
- resolved Jun 04, 2026, 12:22 PM UTC
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Any organization reports that failed to complete during the incident can be manually re-created and run. Any scheduled reports will complete in the next run. Again, customers can manually create and run these sooner if required. Customers may have experienced errors from 2026-06-03 05:00 AM UTC until 2026-06-04 10:50 AM UTC.
Minor June 2, 2026 Customers dependent on deprecated TLS ciphers will experience interruption (Incident-5003) 1h 23m eSignature (AU), eSignature (CA), eSignature (EU), eSignature (NA1) and 10 more
Started Jun 02, 2026, 11:32 PM UTC· resolved Jun 03, 2026, 12:55 AM UTC
- investigating Jun 02, 2026, 11:32 PM UTC
We are currently investigating this issue.
- identified Jun 02, 2026, 11:50 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jun 02, 2026, 11:56 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 03, 2026, 12:55 AM UTC
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Some customers dependent on deprecated TLS ciphers may have experienced interruptions from 2026-06-02 10:49 PM UTC until 2026-06-03 12:49 AM UTC.
Minor May 28, 2026 Issues utilising +86 country code for sending envelopes and phone authentication (Incident 4968) 1h 37m eSignature (DEMO), eSignature (AU), eSignature (CA), eSignature (EU) and 7 more
Started May 28, 2026, 02:51 PM UTC· resolved May 28, 2026, 04:29 PM UTC
- identified May 28, 2026, 02:51 PM UTC
Customers attempting to send an envelope or use SMS/Phone Authentication for Envelopes utilising a +86 will experience errors during this process. Engineering teams have been engaged and triage is underway.
- identified May 28, 2026, 03:50 PM UTC
Engineers have identified the root cause and are executing a fix.
- resolved May 28, 2026, 04:29 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 issues from 2026-05-28 02:06 AM UTC until 2026-05-28 04:29 PM UTC.
Minor May 27, 2026 Customers may experience timeouts related to core AI features which include document summarization and extractions. (incident 4961) 1d eSignature (DEMO), eSignature (AU), eSignature (CA), eSignature (EU) and 5 more
Started May 27, 2026, 01:04 AM UTC· resolved May 28, 2026, 01:42 AM UTC
- investigating May 27, 2026, 01:04 AM UTC
We are currently investigating this issue.
- identified May 27, 2026, 02:35 AM UTC
The issue has been identified and a fix is being implemented.
- investigating May 27, 2026, 03:32 AM UTC
We are continuing to investigate this issue.
- identified May 27, 2026, 04:03 AM UTC
The issue has been identified and a fix is being implemented.
- identified May 27, 2026, 05:24 PM UTC
We are continuing to work on a fix for this issue.
- monitoring May 27, 2026, 07:30 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring May 27, 2026, 09:16 PM UTC
We are continuing to monitor for any further issues.
- monitoring May 27, 2026, 10:04 PM UTC
We are continuing to monitor for any further issues.
- monitoring May 28, 2026, 12:05 AM UTC
We are continuing to monitor for any further issues.
- resolved May 28, 2026, 01:42 AM 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 issues from 2026-05-26 06:04 PM UTC until 2026-05-28 01:44 AM UTC.
Minor May 21, 2026 Salesforce is experiencing an outage that may impact customers using the Salesforce integration (Incident-4935) 4h 41m
Started May 21, 2026, 11:12 PM UTC· resolved May 22, 2026, 03:54 AM UTC
- investigating May 21, 2026, 11:12 PM UTC
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.
- resolved May 22, 2026, 03:54 AM 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 issues using the Salesforce integration from 2026-05-21 08:00 PM UTC until 2026-05-22 01:37 AM UTC.
Minor May 19, 2026 Some customers may experience latencies sending and signing in EU (Incident-4915) 1h 36m eSignature (EU)
Started May 19, 2026, 12:59 PM UTC· resolved May 19, 2026, 02:36 PM UTC
- investigating May 19, 2026, 12:59 PM UTC
We are currently investigating the issue.
- investigating May 19, 2026, 01:30 PM UTC
We are continuing to investigate the issue.
- resolved May 19, 2026, 02:36 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 issues from 2026-05-19 12:39 PM UTC until 2026-05-19 2:33 PM UTC.
Minor May 18, 2026 Some customers may experience latencies sending and signing in NA1 and NA3 (Incident-4902) 25m eSignature (NA1), eSignature (NA3)
Started May 18, 2026, 05:55 PM UTC· resolved May 18, 2026, 06:20 PM UTC
- investigating May 18, 2026, 05:55 PM UTC
We are currently investigating this issue.
- resolved May 18, 2026, 06:20 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 experience latencies sending and signing in NA1 and NA3 from 2026-05-18 05:29 PM UTC until 2026-05-18 06:10 PM UTC.
Notice May 18, 2026 Users may experience report failures and loading delays in the EU11 and EU21 sites (incident 4896) – CLM (EU11), CLM (EU21)
Started May 18, 2026, 02:30 PM UTC· resolved May 18, 2026, 02:30 PM UTC
- resolved May 18, 2026, 02:30 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-05-18 12:00 PM UTC until 2026-05-18 01:45 PM UTC.
Minor May 14, 2026 Users may experience document report failures and loading delays in the EU11 and EU21 sites (incident 4863) 1h 17m CLM (EU11), CLM (EU21)
Started May 14, 2026, 06:45 PM UTC· resolved May 14, 2026, 08:03 PM UTC
- investigating May 14, 2026, 06:45 PM UTC
We are currently investigating this issue.
- identified May 14, 2026, 07:23 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring May 14, 2026, 07:54 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 14, 2026, 08:03 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 from 2026-05-11 10:15 PM UTC until 2026-05-14 07:58 PM UTC.
Minor May 13, 2026 Workflow Reports Experiencing Timeout Errors (Incident 4874) 2h 28m CLM (EU11), CLM (EU21)
Started May 13, 2026, 11:49 AM UTC· resolved May 13, 2026, 02:18 PM UTC
- identified May 13, 2026, 11:49 AM UTC
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.
- identified May 13, 2026, 11:50 AM UTC
We are continuing to work on a fix for this issue.
- monitoring May 13, 2026, 01:41 PM UTC
A fix has been implemented and we are observing telemetry to validate.
- resolved May 13, 2026, 02:18 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 from 2026-04-19 10:00 PM UTC until 2026-05-13 02:20 PM UTC.