DocuSign Outage History

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 3:22 PM UTC and was resolved by 3:27 PM UTC. 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 May 14, 2025 1:46 PM UTC and the issue was first flagged as degraded at May 14, 2025 2:02 PM UTC. The problem affected Rooms in East US and East US 2, causing partial disruption for users during the window. The service was restored by May 14, 2025 3:02 PM UTC 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 1:47 PM UTC and concluding at 1:57 PM UTC. 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 7:46 PM UTC with the status page updating to a warning at 7:47 PM UTC as engineers investigated, and was resolved by 8:12 PM UTC 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 4:52 PM UTC with a status update indicating joining rooms could be impacted, and was resolved by 5:57 PM UTC 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 12:17 PM UTC.

DocuSign experienced partial degradation across eSignature, Rooms, and CLM beginning May 6, 2025 12:47 AM UTC 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 May 6, 2025 8:17 PM UTC 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 May 12, 2025 10:07 AM UTC several core eSignature regions had returned to normal, though other areas remained degraded for a time. The incident lasted several days, from May 6, 2025 12:47 AM UTC to May 12, 2025 10:07 AM UTC for the affected components.

DocuSign experienced a brief partial outage affecting the Spreedly Core Transactional API used for processing transactions. The outage began at 9:22 PM UTC and was resolved by 9:27 PM UTC, lasting about 5 minutes. During the incident, the Spreedly Core Transactional API was listed as Partially Degraded, and DocuSign issued two status updates before full recovery.

DocuSign's eSignature service experienced degraded navigation across multiple regions (NA1, NA2, NA3, EU, and CA) starting at Apr 25, 2025 9:57 PM UTC and was resolved by Apr 25, 2025 11:12 PM UTC, lasting about 1 hour 15 minutes. The incident affected five regional components and was followed by two status updates from DocuSign's status page as investigators worked to restore full access.

Users may have encountered difficulties navigating the DocuSign site during the outage.

DocuSign eSignature experienced latency and navigation errors across multiple regions, impacting North America, Europe, Australia, and Canada. Users attempting to sign documents or load signing pages faced slow performance and, in some cases, blank screens. The incident began at Apr 24, 2025 2:52 PM UTC and affected seven eSignature components (NA1, NA2, NA3, NA4, EU, AU, CA). The provider issued multiple updates as the issue was investigated.

The service returned to normal after a series of updates, with the final restoration noted by Apr 24, 2025 5:12 PM UTC. The incident lasted roughly 2 hours and 20 minutes, during which users could experience intermittent delays and navigation problems when working with documents.