DocuSign Outage History

DocuSign experienced a partial outage due to issues with the Spreedly Core Transactional API, causing degraded transaction processing for workflows that rely on this integration. The incident began at Mar 15, 2025 6:17 AM UTC and was resolved by Mar 15, 2025 7:37 AM UTC, lasting about 1 hour 20 minutes. The service status page reported Partially Degraded Service during the outage, with two official updates before full restoration.

DocuSign CLM EU11 experienced a brief SFTP-related disruption affecting users in the EU11 region. SFTP operations could return errors during the incident. The issue began at Mar 14, 2025 8:12 PM UTC and was resolved by Mar 14, 2025 8:52 PM UTC, lasting roughly 40 minutes. The CLM EU11 component moved from an operational state to degraded and back as engineers investigated and resolved the problem.

Status updates: The provider issued two official updates during the incident, describing an ongoing investigation and the subsequent resolution. The outage appears to be regional to CLM EU11 and did not indicate wider impact beyond that region.

DocuSign's eSignature service in the NA2 region experienced an outage that prevented users from completing eSign actions. The incident began when the NA2 eSignature component went down, with the status showing Investigating at Mar 12, 2025 3:04 PM UTC and the outage confirmed at Mar 12, 2025 3:07 PM UTC. The issue was regional to NA2 and lasted about 1 hour and 55 minutes, with restoration observed at Mar 12, 2025 5:02 PM UTC. The provider issued two status updates during the incident and the disruption did not appear to be global, affecting only the NA2 component.

During a brief incident, some DocuSign eSignature users experienced duplicate notifications in the IDV for the QES flow. The issue affected eight components across NA1, NA2, NA3, NA4, AU, CA, EU, and JP, potentially delivering the same alert more than once. The incident began on 10:32 AM UTC and was resolved by 11:22 AM UTC. DocuSign issued two status updates during the incident, and status returned to normal once the issue was resolved.

The incident affected DocuSign CLM NA11 reporting, where some users saw a spinning wheel or the error message Something went wrong when generating or viewing reports. The eSign Demo environment also experienced latency. Issues began at 3:02 PM UTC and were resolved by 6:52 PM UTC, lasting roughly 3 hours and 50 minutes. The problems impacted two components: CLM / NA11 and eSignature / DEMO. DocuSign issued four status updates during the incident as investigations and remediation progressed. CLM NA11 returned to normal by 6:32 PM UTC and the eSignature / DEMO environment by 6:52 PM UTC.

DocuSign eSignature experienced degraded performance affecting Navigator AI Extractions across six regional components: NA4, NA1, NA2, CA, NA3, and AU. Users attempting AI-driven extractions encountered errors beginning at Feb 27, 2025 9:17 PM UTC and lasting until Feb 28, 2025 4:17 AM UTC (roughly seven hours). The DocuSign status page documented an initial investigation and subsequently indicated the affected components were degraded before services were restored. The provider issued two status updates during the incident.

DocuSign CLM production experienced degraded performance due to Smart Rules running inconsistently, causing some scheduled executions to be skipped. This impacted CLM production regions across NA11, NA21, US11, US12, US13, EU11, EU21, and the UAT environment, with users potentially seeing delays or incomplete automated workflows tied to CLM Smart Rules.

The outage began at 6:52 PM UTC and was resolved by 7:32 PM UTC, lasting roughly 40 minutes. DocuSign issued two updates during the incident, including Feb 27, 2025 7:07 PM UTC noting ongoing remediation and later confirmation that the affected components had returned to normal.

DocuSign experienced a regional incident affecting the eSignature NA1, NA2, NA3, and NA4 components, with some users unable to publish webforms. The issue began at Feb 26, 2025 2:12 AM UTC and was resolved by Feb 26, 2025 4:02 AM UTC, lasting roughly 1 hour and 50 minutes.

The provider issued two status updates during the incident and restored all affected components to normal by the end of the incident at Feb 26, 2025 4:02 AM UTC.

DocuSign's eSignature web interface experienced latency and errors, impacting signing and document workflows for users. Four eSignature components (NA1, NA2, NA3, NA4) were listed as degraded during the incident. The issue began at Feb 24, 2025 8:42 PM UTC when the status page flagged degraded performance and an investigation; users reported issues earlier around 20:00 UTC. The outage affected users attempting to sign or manage documents on the eSignature web platform.

DocuSign's CLM service experienced degraded performance for a short period affecting CLM / NA11 during a UAT-focused incident around 6:22 PM UTC to 7:07 PM UTC. Users relying on AI Assisted Review may have encountered delays in processing during this time. The incident began with engineers investigating at 6:22 PM UTC, the public status was set to a degraded state at 6:27 PM UTC, and full service was restored by 7:07 PM UTC. The outage lasted approximately 40 minutes and affected the CLM / NA11 component. DocuSign issued two status updates during the incident to communicate investigation and resolution.

The issue appears to have been isolated to CLM / NA11, with no regional pattern indicated. No user reports were noted during this period. The incident prompted investigation and restoration steps as documented in the official updates.