DocuSign Outage History

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.

DocuSign's eSignature service in NA2 and NA3 experienced an outage affecting signing workflows and document loading. The incident began on 7:12 PM UTC and was resolved by 8:52 PM UTC, lasting about 1 hour and 40 minutes. Users reported server errors, timeouts, and documents not loading during the event. The provider indicated an investigation started around Feb 5, 2025 7:08 PM UTC and issued two status updates as NA2 and NA3 services were restored.

DocuSign experienced a brief partial degradation affecting the Spreedly Core Transactional API, a third-party service used for transactional processing. The incident caused intermittent failures and degraded performance for users performing transactions through DocuSign during the window. The outage lasted 20 minutes, from 2:32 PM UTC to 2:52 PM UTC. The DocuSign status page listed the Spreedly Core Transactional API as Partially Degraded during this period and then returned to normal.

DocuSign experienced a scheduled maintenance window affecting the Third Party Services / Spreedly Core Transactional API. The maintenance lasted about 1 hour, from Jan 31, 2025 3:02 PM UTC to Jan 31, 2025 4:02 PM UTC, during which some API calls may have been unavailable or degraded. The provider issued two status updates during the incident, noting the maintenance and later confirming restoration as the service returned to normal.

DocuSign experienced a brief partial degradation affecting transactions routed through the Spreedly Core Transactional API. The disruption impacted operations relying on the third-party service, causing intermittent processing for a short period. The impact was limited to the Spreedly integration and did not indicate a broader outage across DocuSign services.

The incident began at 7:27 PM UTC and was resolved by 7:37 PM UTC. The DocuSign status page listed the component as Partially Degraded Service and noted two status updates during the event. Service returned to normal after the brief disruption.

DocuSign experienced a brief partial degradation affecting the Spreedly Core Transactional API, a critical component used for payment processing. The issue began at 7:42 PM UTC and was resolved by 7:47 PM UTC, with services returning to normal shortly after. The incident impacted the Third Party Services / Spreedly Core Transactional API component.

DocuSign experienced a partial outage affecting the eSignature Bulk Send feature, preventing some users from performing bulk sending tasks. Investigations began at Jan 17, 2025 4:24 PM UTC, with four eSignature components (NA1, NA2, NA3, NA4) listed as degraded. The incident prompted two official status updates as teams worked to diagnose the issue. The Bulk Send capability was restored by Jan 17, 2025 6:27 PM UTC and the components returned to normal, with the outage lasting a little over two hours.

Some users in the docusign.mil IL4 environment were unable to log in to the DocuSign eSignature service, affecting authentication for a subset of users. The issue impacted the eSignature / USFED component. The outage began at 5:12 PM UTC and was resolved by 5:57 PM UTC, lasting about 45 minutes. DocuSign initially stated they were investigating and later confirmed restoration, with two status updates issued during the incident.