DocuSign outage history

Users experienced a brief degradation in DocuSign's payment processing pathway when the Spreedly Core Transactional API reported a temporary issue. The status page shows the Third Party Services / Spreedly Core Transactional API moving from up to a warning at 4:17 PM UTC and back to up by 4:37 PM UTC. During this roughly 20 minutes window, some transactions may have experienced delays or failures when routed through the gateway.

DocuSign indicated the issue as a temporary disruption in the third-party service and confirmed restoration to normal operation once the gateway stabilized.

DocuSign experienced a brief incident affecting document upload and generation across CLM/UAT NA11, CLM/DEMO S1, and the eSignature/DEMO environment. Users attempting to upload or generate documents began encountering errors starting at 11:22 PM UTC as the issue was first acknowledged and under investigation.

Users attempting to generate documents in DocuSign experienced latency and occasional failures, disrupting automated document workflows. The issue appeared to affect multiple DocuSign services and was centered on the CLM/NA11 region. Impact began at Aug 11, 2026 1:17 PM UTC with the status page noting Document Generation Failures or Latency as engineers triaged the incident.

Over the following hours, updates described degraded task processing across multiple services as resources were engaged and fixes attempted. An initial mitigation did not fully resolve the issue, and monitoring continued while the environment was stabilized. The CLM/NA11 component recovered and returned to normal by Aug 12, 2026 2:52 AM UTC.

An AU region login outage began around Aug 11, 2026 4:52 AM UTC, preventing some users from signing in to DocuSign's eSignature service. Sydney and Melbourne users reported sign-in failures, and the Get Started button often greyed out after clicking. The issue primarily affected the AU region, with affected users unable to access signing features for a period.

Updates to the incident show engineering teams identified a potential cause and deployed a fix by 5:02 AM UTC. By 5:47 AM UTC, additional regions including NA4, JP1, NA2, NA3, CA, EU, and NA1 reported degraded environments, while AU remained impacted. Telemetry was monitored to validate the fix. The service returned to normal by 6:52 AM UTC as all components moved back to up status, marking roughly two hours of outage duration. A noticeable volume of user reports during the event reflected the broader impact.

Users in the NA11 region experienced latency and errors across DocuSign CLM, resulting in slow responses and workflow delays. The incident began at 5:02 PM UTC and was categorized as degraded performance. After the issue was identified, engineering actions were taken to mitigate it, a fix was implemented, and monitoring continued. The NA11 component returned to normal by 6:17 PM UTC and the impact was localized to that region.

DocuSign Admin and eSignature endpoints across AU, CA, EU, JP1, NA1-NA4, and the DEMO environment experienced intermittent unavailability beginning at 8:02 PM UTC. The incident, tracked as Incident 5548, was marked as a degraded state while engineers investigated the root cause. A fix was implemented and monitoring began by 9:07 PM UTC, with services gradually returning to normal. By 9:27 PM UTC, all affected regions were reported as up, marking recovery from the disruption that lasted a little over an hour.

DocuSign CLM users experienced errors when sending and reviewing workflows in the CLM UAT NA11 and DEMO S1 environments. The incident, titled 'Workflow Send and Review Errors (Incident 5532)', began at 6:52 PM UTC and the status page indicated ongoing investigation. Engineers identified the issue and engaged additional resources as they worked to resolve it, with the affected components brought back online over the next couple of hours. The recovery culminated in CLM / UAT NA11 and CLM / DEMO S1 returning to normal by 9:12 PM UTC while monitoring continued.

DocuSign's eSign Admin Settings page experienced access issues that affected the eSignature / DEMO component. The incident began at 1:32 AM UTC and persisted while engineers investigated. Admins trying to load settings may have encountered errors or delays.

The issue was identified and a fix was implemented, with ongoing monitoring. The component returned to normal service by 4:47 AM UTC, marking the end of the incident after about three hours.

Users attempting to generate documents via DocuSign's Salesforce integration faced failures beginning at 1:42 PM UTC, impacting the eSignature / EU and CLM / EU21 components. The issue was described as document generation failures with Salesforce integration, and the status page indicated ongoing investigation as engineers worked to identify the root cause. The incident, tracked as Incident 5525, progressed through the afternoon with updates noting that a fix was being implemented.

By 4:02 PM UTC the affected components were restored to normal operation, and a fix had been implemented with monitoring in place.

Powerforms intermittently failed to load beginning around 8:07 PM UTC, affecting all eSignature North America instances (NA1-NA4). Users attempting to access Powerforms likely faced loading delays or errors while preparing and sending forms.

DocuSign's status updates show an active investigation started soon after the issue appeared. At 8:27 PM UTC a fix had been implemented and monitoring began to verify stability across the affected components.

Service began returning to normal as the NA endpoints recovered; by 8:47 PM UTC the four NA eSignature endpoints were reported up again and Powerforms loading was restored across the board.