DocuSign incident
Customers may see increased latency when sending and signing and intermittent errors (Incident 5232)
DocuSign experienced a minor incident on June 29, 2026 affecting NA1 and NA11 and 1 more component, lasting 3h 5m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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:36 PM UTC
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
- postmortem Jun 30, 2026, 11:02 PM UTC
| Article Title: | RCA for Docusign eSign & CLM Service Disruption on June 29, 2026 | |---|---| | Impact Summary: | Between 2026-06-29 08:18 AM UTC and 2026-06-29 06:05 PM UTC, some eSignature customers may have experienced latency and intermittent errors when sending and signing envelopes. Some CLM customers may have experienced degraded performance when viewing, saving, or retrieving documents. Impact was initially limited but became more pronounced as transaction volumes increased during North America business hours. | | Cause: | A staged network routing change was inadvertently applied, redirecting traffic to a secondary region. As traffic volumes increased, this placed additional demand on services responsible for storage and authorization, resulting in elevated latency and intermittent request failures. Additional investigation was required to identify the routing issue before it could be corrected. | | Resolution: | The routing change was corrected, allowing traffic to return to the intended primary region. Service configurations were also adjusted to reduce resource contention and improve service performance. |