DocuSign Status · History · Incident #4996
RESOLVEDCustomers may see increased latency when sending and signing and intermittent errors (Incident 5232)
Minor · Started Jun 29, 2026 · 3:30 PM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
DocuSign Status · History · Incident #4996
RESOLVEDMinor · Started Jun 29, 2026 · 3:30 PM
Duration
3h 5m
Severity
Minor
Detection lead
—
User reports
—
Summary
**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.
Started
Jun 29, 2026 · 3:30 PM
Resolved
Jun 29, 2026 · 6:36 PM
Duration
3h 5m
Severity
Minor
Event timeline
Investigating
Jun 29 · 3:30 PM DocuSignWe are actively investigating this issue.
Investigating
Jun 29 · 5:05 PM DocuSignWe are continuing to investigate this issue.
Identified
Jun 29 · 5:07 PM DocuSignWe have identified the issue and a fix is being implemented.
Identified
Jun 29 · 5:16 PM DocuSignThe issue has been identified and we continue our work to implement a fix.
Identified
Jun 29 · 5:51 PM DocuSignWe continue to work to implement a fix for the issue.
Monitoring
Jun 29 · 6:23 PM DocuSignA fix has been implemented and we are monitoring the results.
Resolved
Jun 29 · 6:36 PM DocuSignThe incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Postmortem
Jun 30 · 11:02 PM DocuSign**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.
Pattern
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026