Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

DocuSign Outage History

Every past DocuSign outage tracked by IsDown, with detection times, duration, and resolution details.

There were 507 DocuSign outages since July 2022. The 111 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor May 12, 2026

May 2026: Users may experience connection errors when trying to switch to CLM or utilising DocuSign edit (Incident 4862)

Detected May 12, 2026 9:42 AM EDT · Resolved May 12, 2026 3:29 PM EDT · Duration about 6 hours

DocuSign users with certain firewall configurations experienced connection errors when trying to switch to CLM or use DocuSign edit functionality across multiple regions including North America, US, and Europe. The issue was caused by blocked access to a required URL (https://login.springcm.com), with a temporary workaround requiring users to contact their IT teams to allowlist the URL. The incident was fully resolved after 5.8 hours when engineering teams implemented a permanent fix.

Minor May 12, 2026

May 2026: Users may experience connection errors when trying to switch to CLM (Incident 4861)

Detected May 12, 2026 4:46 AM EDT · Resolved May 12, 2026 6:48 AM EDT · Duration about 2 hours

DocuSign customers experienced connection errors in the user interface when attempting to switch to CLM (Contract Lifecycle Management), affecting multiple regions including North America, US, and Europe. The issue lasted approximately 2 hours and was caused by a third-party service problem. Engineering teams resolved the incident after identifying and addressing the external dependency issue.

Major May 7, 2026

May 2026: AU Site Outage (Incident 4840)

Detected May 7, 2026 10:09 PM EDT · Resolved May 7, 2026 11:28 PM EDT · Duration about 1 hour

DocuSign's AU site experienced a major outage lasting 1.3 hours, preventing users from accessing the website and generating "Server Request Error: Could not load settings" messages. The service team implemented a mitigation and monitored the results before fully resolving the incident.

Minor April 28, 2026

April 2026: Send Latency in EU (Incident 4776)

Detected Apr 28, 2026 5:03 AM EDT · Resolved Apr 28, 2026 5:43 AM EDT · Duration 40 minutes

DocuSign experienced a 40-minute incident where EU customers encountered latency issues with Send operations. Engineers identified the root cause and implemented a fix. The issue was fully resolved with all telemetry confirming normal operations.

Minor April 23, 2026

April 2026: Some customers are seeing errors previewing and sending envelopes via Docusign App Launcher (Incident 4752)

Detected Apr 23, 2026 4:14 PM EDT · Resolved Apr 23, 2026 4:43 PM EDT · Duration 29 minutes

DocuSign customers experienced errors when previewing and sending envelopes through the DocuSign App Launcher integrated with Salesforce. The issue affected the Salesforce integration component and prevented normal envelope operations. The problem was identified and resolved within 29 minutes.

Minor April 23, 2026

April 2026: Some users might experience latency when attempting to convert non-PDF documents (Incident-4750)

Detected Apr 23, 2026 12:28 PM EDT · Resolved Apr 23, 2026 7:20 PM EDT · Duration about 7 hours

DocuSign experienced a 6.9-hour incident where some users encountered latency when attempting to convert non-PDF documents. The issue affected multiple regions including NA1, NA2, NA3, NA4, CA, and AU. A fix was implemented and the incident was resolved after extended monitoring to ensure system stability.

Major April 17, 2026

April 2026: Login failures and Latency Issues with Sending and Signing Envelopes

Detected Apr 17, 2026 10:47 AM EDT · Resolved Apr 17, 2026 12:19 PM EDT · Duration about 2 hours

DocuSign experienced a major incident affecting login functionality and causing significant latency issues with sending and signing envelopes for a subset of customers in the CA region. The engineering team identified the root cause and deployed a fix that resolved the performance issues. The incident lasted 1.5 hours before being fully resolved.