Provider
DocusignIncident detail
Customers may see increased latency when sending and signing and intermittent errors (Incident 5232)
Timeline window
to
Outage alerts
Get alerted the next time Docusign breaks
Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update Docusign posted, oldest to newest, exactly as it appeared on their official status page.
Investigating
We are actively investigating this issue.
Investigating
We are continuing to investigate this issue.
Identified
We have identified the issue and a fix is being implemented.
Identified
The issue has been identified and we continue our work to implement a fix.
Identified
We continue to work to implement a fix for the issue.
Monitoring
A fix has been implemented and we are monitoring the results.
Resolved
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Resolved
RCA for Docusign eSign & CLM Service Disruption on June 29, 2026
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.
Keep exploring
More from Docusign
Neighboring incidents on Docusign's timeline and the rest of their record on OutageDeck.