DocuSign Outage History

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.

DocuSign experienced a brief partial degradation in the Spreedly Core Transactional API, a third-party service used for transaction processing. The issue began at 3:02 PM UTC and was resolved by 3:07 PM UTC, lasting roughly 5 minutes and affecting the Third Party Services / Spreedly Core Transactional API. Users may have encountered intermittent delays or errors when initiating transactions during the window. The incident was limited to this integration and did not appear to impact other DocuSign services. The provider issued 2 status updates during the incident.

DocuSign reported partial degradation affecting the Spreedly Core Transactional API, a third-party service used for core transactional operations. This caused intermittent delays or failures for users performing transactional actions during the incident window. The outage began at Feb 16, 2025 9:02 AM UTC and was resolved by Feb 16, 2025 10:42 AM UTC, lasting about 1 hour 40 minutes. The provider issued 2 status updates during the incident, with service returning to normal after the final update.

DocuSign NA11 UAT workflow operations within the CLM NA11 component experienced failures, causing a brief degradation in workflow functionality for users in NA11. The outage began at 8:22 PM UTC and was resolved by 8:47 PM UTC. The DocuSign status page indicated an ongoing investigation and noted that NA11 CLM was affected. The incident involved 2 official status updates before operations returned to normal. The impact was limited to the NA11 UAT workflow within CLM.