New! Check service status instantly with our Chrome extension
There were 140 DocuSign outages since January 2025 which are summarized below, including incident details, duration, and resolution information.
DocuSign not working for you?
DocuSign not working for you?
DocuSign EU IAM Navigator and eSignature experienced latency and intermittent errors when users attempted to use AI features, impacting customers in the EU region. Users may have seen slower responses or failures during AI-enabled tasks.
DocuSign CLM experienced an issue during Salesforce document generation that caused incorrect redirects, impacting seven CLM components across NA21, US12, EU11, EU21, US13, US11, and NA11. Users attempting to generate documents from Salesforce were redirected to unintended pages, hindering document creation for affected users. The incident began with an investigation around , escalated to a degraded state at , and persisted until when status returned to up. The provider issued 2 status updates during the incident.
DocuSign's Australia (AU) eSignature service experienced latency and navigation errors in the AU PROD environment, causing degraded site navigation for users in Australia. The degraded state began during an investigation at , the AU eSignature component was flagged as degraded at , and service returned to normal by after roughly 1 hour and 50 minutes. The incident appears isolated to the AU region, and the AU eSignature component had two status updates issued during the event.
A brief partial degradation affected the Spreedly Core Transactional API, used by DocuSign for transactional processing. Users may have experienced intermittent issues during the incident as the Third Party Services / Spreedly Core Transactional API was degraded. DocuSign's status page indicated Partially Degraded Service during the event.
The outage began at and was resolved by . The service posted two official updates as the issue was investigated and then resolved.
DocuSign Rooms experienced a brief outage affecting validation of NAR forms and envelope creation, with users seeing an 'Error calling 3rd party' message (DIRCA-2597). Investigation began at and the issue was first flagged as degraded at . The problem affected Rooms in East US and East US 2, causing partial disruption for users during the window. The service was restored by following two status updates from DocuSign.
DocuSign Rooms experienced a brief outage affecting validation of NAR forms and envelope creation for users in East US and East US 2 regions. Users attempting to validate NAR forms or create envelopes saw an error message 'Error calling 3rd party' per the status page. The incident lasted about 10 minutes, beginning at and concluding at . DocuSign issued status updates indicating investigation and subsequent restoration, with both impacted Rooms components returning to the up state. The impact was localized to the two East US Rooms components with no wider disruption reported.
DocuSign experienced a brief login issue in the CLM UAT NA11 environment, causing some users to encounter login errors. The incident began around with the status page updating to a warning at as engineers investigated, and was resolved by when the component returned to normal operation. The CLM / UAT NA11 component was affected, and two status updates were issued during the incident. The outage lasted roughly 25 minutes with effects limited to authentication in the CLM UAT NA11 environment.
DocuSign Rooms Prod experienced a brief outage that prevented some users from joining rooms in the East US regions (Rooms / East US and Rooms / East US 2). The issue began at with a status update indicating joining rooms could be impacted, and was resolved by after the engineering team investigated and the services were restored. The incident involved two affected components and was addressed through two official status updates before full recovery.
DocuSign’s eSignature Demo environment experienced a partial outage that prevented some users from uploading documents when using Firefox or Safari. The issue was first acknowledged when the eSignature / DEMO component moved to a degraded state and an investigation began. The incident appeared browser-specific and limited to the Demo experience. DocuSign issued two status updates during the event, noting that users could encounter upload problems and later confirming the service had returned to normal. The outage lasted about 1 hour and 20 minutes, with the component returning to full operation by .
DocuSign experienced partial degradation across eSignature, Rooms, and CLM beginning as Admin users reported issues with granting 'Edit on behalf of' and 'Send on behalf of' permissions in eSignature across multiple regions. A separate issue affected Rooms, where form tag values were not persisting when added to envelopes. The status page documented ongoing investigations and progress as teams identified root causes and implemented fixes, with a fix being implemented by and subsequent updates outlining improvements.
Over the next several days, latency and errors emerged in CLM NA11 and in signing operations for DSF Prod EU. The degradation affected 13 components across eSignature (NA4, CA, JP, AU, NA1-NA3, EU), Rooms (East US, East US 2, DEMO), CLM NA11, and EU TSP. Status updates were issued repeatedly as investigations continued and fixes were rolled out. User reports were limited. By several core eSignature regions had returned to normal, though other areas remained degraded for a time. The incident lasted several days, from to for the affected components.
Looking for more DocuSign outage stats?
Get real-time insights and historical data on DocuSign outages.
