DocuSign Outage History

During a brief maintenance window on 4:07 PM UTC to 4:12 PM UTC, the Third Party Services / Spreedly Core Transactional API was listed as under maintenance. This period could have caused intermittent transaction processing or connectivity issues for users relying on this API. The impact appeared limited to that component and did not indicate a broader DocuSign service disruption.

DocuSign posted two status updates during the incident. The maintenance started at 4:07 PM UTC and completed by 4:12 PM UTC, with services returning to normal after the maintenance window.

DocuSign experienced degraded performance for the Spreedly Core Transactional API, impacting integrations that rely on this service. The degradation began with a warn state at Feb 17, 2026 11:57 PM UTC and persisted into the next day. Maintenance was engaged at Feb 18, 2026 3:02 PM UTC and the API returned to full operation at Feb 18, 2026 4:02 PM UTC. The incident included three official status updates and lasted roughly 16 hours and 5 minutes, from the initial warn to full restoration.

A subset of DocuSign customers experienced intermittent latency when sending or receiving eSignature jobs. The issue affected two components, eSignature / NA3 and eSignature / NA1, and engineers were actively triaging the problem. The incident began at 2:57 PM UTC. The latency persisted for about 55 minutes and the status returned to normal at 3:52 PM UTC. DocuSign issued 2 official status updates during the incident.

DocuSign reported degraded performance affecting the CLM EU21 region, with users experiencing slowness and failures during content uploads and downloads. The issue prompted an investigation, and the CLM EU21 component was downgraded to a degraded state at Feb 16, 2026 9:27 PM UTC. The outage lasted about 55 minutes, and service returned to normal by Feb 16, 2026 10:22 PM UTC as updates indicated resolution. Impact appeared limited to the CLM EU21 component, with no broader service disruption indicated.

DocuSign CLM NA11 customers experienced issues accessing their accounts and performing actions within the CLM platform. The incident began at 8:52 PM UTC and was resolved by 9:57 PM UTC, lasting about 1 hour and 5 minutes with regional impact in the CLM NA11 environment. DocuSign acknowledged the issue and published two official updates as engineers investigated, describing the incident as a degraded service for the NA11 region. The status later returned to up, fully restoring access and actions for affected users.

DocuSign reported a degradation in its Demo/UAT environment affecting Navigator, Prepare, Webforms, and IAM ingestion. DEMO/UAT users may have experienced issues with Webforms not saving, document ingestion failures, and missing ID verification or healthcare fields in Prepare, with portions of Navigator failing to load. The impact was isolated to the DEMO/UAT environment and affected two components: eSignature / DEMO and Rooms / DEMO. The incident began at 2:12 PM UTC and was resolved by 5:27 PM UTC, lasting approximately 3 hours 15 minutes. The provider issued 2 status updates during the incident.

DocuSign briefly listed a degraded state during a test incident. The status page transitioned from up to warn at 7:12 PM UTC and returned to up at 9:07 PM UTC, for a total duration of about 1 hour 55 minutes. No user-facing issues were reported, and the incident was described on the status page as a test with no further details. The service returned to normal after the final update.

DocuSign experienced a brief degraded state in the Third Party Services / Spreedly Core Transactional API, with intermittent delays for transactions routed through this API. The issue was limited to this single component and did not affect other DocuSign services. The incident began at Feb 10, 2026 2:57 PM UTC and was resolved by Feb 10, 2026 3:02 PM UTC as the status page moved from up to warn and back to up.

DocuSign experienced a brief degraded performance for the Spreedly Core Transactional API, impacting transactions processed via Spreedly and other API calls. The issue began at 3:57 PM UTC and was resolved by 5:02 PM UTC, lasting about 1 hour and 5 minutes. The DocuSign status page provided two updates during the incident, and services returned to full operation after the second update.

DocuSign experienced a brief degraded performance affecting the Spreedly Core Transactional API, a third party service used to process transactions. The degradation began at 6:17 PM UTC and was resolved at 7:57 PM UTC, lasting about 1 hour and 40 minutes. The provider issued 2 status updates during the incident, with the component moving from up to warn and back to up.