DocuSign outage history

A regional disruption in DocuSign CLM NA11 prevented users from previewing documents, hindering review workflows for affected customers. The incident began at 10:07 PM UTC and persisted while teams investigated the cause and implemented mitigations. By 11:47 PM UTC the CLM NA11 component had returned to normal and document previews resumed.

Engineers identified what they believe to be the root cause and implemented mitigations to reduce impact for affected users.

Users experienced high latency when sending and signing documents on DocuSign's Signing API across North American production environments NA1 through NA4. The degraded performance began at 1:57 AM UTC and affected sign and send workflows for a broad set of customers. The incident, labeled 5741, prompted engineering to investigate recent deployments for possible mitigations, including a potential rollback.

By 2:37 AM UTC, the investigation expanded to the settings-service as teams pursued a forward fix and root-cause analysis. Latency decreased but remained degraded as of that update. Recovery followed at 3:52 AM UTC, with all eSignature NA1-NA4 components returning to normal. Engineers continued monitoring and root-cause work to prevent recurrence.

Starting at 12:22 AM UTC, DocuSign CLM experienced degradation and failures in the workflow engine and expression evaluation, impacting users of the CLM / NA21 component. DocuSign acknowledged the issue at 1:02 AM UTC and said a fix was being implemented. The service returned to normal for CLM / NA21 by 1:52 AM UTC, with updates indicating the component had returned to healthy status. Users potentially faced slowed or failed CLM processes during the incident window.

Users in DocuSign eSignature AU and JP1 regions experienced intermittent login problems and API failures beginning around 8:42 AM UTC. The DocuSign status page noted an investigation into intermittent login and API issues affecting these regions, with the affected components listed as eSignature / AU and eSignature / JP1.

By 9:27 AM UTC, the issue was resolved and the eSignature AU and JP1 components moved back to the up state. The disruption was localized to these regions and lasted roughly 45 minutes, affecting user authentication and API usage during that window.

DocuSign experienced a brief UI latency in the CLM / S1.EU component beginning at 5:37 PM UTC. Users saw slower UI responses and delays in the affected region, but the incident did not indicate a full service outage. The disruption was confined to the EU region’s CLM / S1.EU setup and resolved about five minutes later.

DocuSign’s status page noted a UI Latency Issues (Incident 5692) and that the team was investigating. The issue was cleared by 5:42 PM UTC as the CLM / S1.EU component returned to normal operation.

Users loading the DocuSign CLM UI in the S1.EU region experienced latency when interacting with the interface. The issue began at 4:07 PM UTC and persisted through the subsequent update at 4:47 PM UTC before the CLM / S1.EU component returned to normal at 5:32 PM UTC. The impact appeared isolated to the EU region, with no broader service outage reported. DocuSign communicated the situation via the status page, noting UI latency issues and ongoing investigation, and confirmed recovery once the component returned to normal.

DocuSign's eSignature service experienced slow performance and delays beginning at 11:42 PM UTC, affecting users in Australia and Canada. The degraded experience disrupted core workflows such as sending envelopes and uploading documents, with Canadian users reporting envelope errors and upload failures (examples from Vancouver and Calgary).

DocuSign's status updates show the root cause was identified and a fix was implemented, with monitoring under way. The fix took effect by 1:32 AM UTC and the service returned to normal for the AU and CA components by 1:52 AM UTC.

DocuSign reported a partial disruption in the JP1 region where customers signing documents may have experienced failures or delays when writing back signed records to Salesforce via the eSignature workflow. The issue was isolated to the JP1 scope and affected the Salesforce writeback step for users in that region. Engineering teams were actively triaging the problem and working toward a fix. Impact began at 10:12 AM UTC for the JP1 eSignature component.

Users experienced a brief degradation in DocuSign's payment processing pathway when the Spreedly Core Transactional API reported a temporary issue. The status page shows the Third Party Services / Spreedly Core Transactional API moving from up to a warning at 4:17 PM UTC and back to up by 4:37 PM UTC. During this roughly 20 minutes window, some transactions may have experienced delays or failures when routed through the gateway.

DocuSign indicated the issue as a temporary disruption in the third-party service and confirmed restoration to normal operation once the gateway stabilized.

DocuSign experienced a brief incident affecting document upload and generation across CLM/UAT NA11, CLM/DEMO S1, and the eSignature/DEMO environment. Users attempting to upload or generate documents began encountering errors starting at 11:22 PM UTC as the issue was first acknowledged and under investigation.