DocuSign Outage History

DocuSign is up right now

DocuSign had 105 outages in the last 2 years totaling 134h 4m of downtime — averaging 4.3 incidents per month.

There were 105 DocuSign outages since October 21, 2025 totaling 134h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.docusign.com

Minor July 31, 2026

Failures with Envelope Writeback and Status Updates (Incident 5505)

Detected by Pingoru
Jul 31, 2026, 12:45 PM UTC
Resolved
Jul 31, 2026, 06:01 PM UTC
Duration
5h 16m
Affected: NA2NA3NA4EUDEMO
Timeline · 7 updates
  1. investigating Jul 31, 2026, 12:45 PM UTC

    Customers in Europe may experience failures with envelope writeback and status update when reviewing Connect logs for DAl envelopes. Engineering teams are engaged and are actively triaging.

  2. investigating Jul 31, 2026, 03:22 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jul 31, 2026, 03:23 PM UTC

    We continue to investigate the issue and additional resources have been engaged.

  4. investigating Jul 31, 2026, 05:16 PM UTC

    We are currently investigating an issue affecting customers using the Salesforce integration across EU and NA regions. Customers may experience failures with envelope write-back and status updates, with the error: "The underlying connection was closed. An unexpected error occurred on send." Services affected: Salesforce connector (envelope write-back, status updates) Impact: Completed envelope statuses may not be reflected in Salesforce. Our engineering teams are actively investigating the root cause across multiple workstreams. We will provide updates as the investigation progresses.

  5. identified Jul 31, 2026, 05:33 PM UTC

    We have identified the issue and a fix is being implemented.

  6. identified Jul 31, 2026, 05:51 PM UTC

    The issue has been identified and we continue our work to implement a fix.

  7. resolved Jul 31, 2026, 06:01 PM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

Read the full incident report →

Minor July 30, 2026

Customers may experience errors when signing up for new accounts (Incident 5500)

Detected by Pingoru
Jul 30, 2026, 07:24 PM UTC
Resolved
Jul 30, 2026, 08:34 PM UTC
Duration
1h 9m
Affected: DEMO
Timeline · 4 updates
  1. investigating Jul 30, 2026, 07:24 PM UTC

    We are actively investigating this issue.

  2. investigating Jul 30, 2026, 07:32 PM UTC

    We are continuing to investigate this issue.

  3. identified Jul 30, 2026, 07:57 PM UTC

    We have identified the issue and a fix is being implemented.

  4. resolved Jul 30, 2026, 08:34 PM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

Read the full incident report →

Notice July 27, 2026

New Docusign Status Center: Subscribe by September 1 to Receive Updates

Detected by Pingoru
Jul 27, 2026, 06:41 PM UTC
Resolved
Jul 27, 2026, 06:43 PM UTC
Duration
2m
Affected: PRODHeadquartersDEMONorth CentralNA1NA11EU.WCustomer SupportDocusign.com HostingDEMONA2NA21PRODEast USEU.NLearning PortalSalesforceNA3US11East US 2EU.CAWS ec2-us-west-2NA4US12NA.WEU11Akamai Global Traffic ManagementCANA.NEAUSpreedly Core Transactional APINotaryEU21NA.EEUNA.CDEMOUS13FedRAMPUAT NA11USFEDJP1DEMO S1S1.USS2.USS1.EUS1.AUDEMO
Timeline · 1 update
  1. resolved Jul 27, 2026, 06:41 PM UTC

    On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. As part of this transition, Slack, SMS, and RSS notification methods will be deprecated and will no longer be supported on the new platform. To ensure you continue receiving system status alerts after this date, you will need to resubscribe on the new site using one of the available notification methods. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Read the full incident report →

Minor July 27, 2026

Qualified Verification Latency (Incident 5472)

Detected by Pingoru
Jul 27, 2026, 10:45 AM UTC
Resolved
Jul 27, 2026, 06:13 PM UTC
Duration
7h 28m
Affected: PROD
Timeline · 2 updates
  1. identified Jul 27, 2026, 10:45 AM UTC

    Customers may be experiencing issues when attempting qualified verifications. Engineering teams have been engaged and are actively triaging this issue.

  2. resolved Jul 27, 2026, 06:13 PM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

Read the full incident report →

Minor July 23, 2026

Customers in AU/JP may experience errors or delays when logging in, sending, or signing envelopes (Incident 5409)

Detected by Pingoru
Jul 23, 2026, 08:59 PM UTC
Resolved
Jul 23, 2026, 10:30 PM UTC
Duration
1h 31m
Affected: AUJP1
Timeline · 4 updates
  1. investigating Jul 23, 2026, 08:59 PM UTC

    We are actively investigating this issue.

  2. investigating Jul 23, 2026, 09:07 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jul 23, 2026, 09:45 PM UTC

    AU and JP are stable at present. Teams are continuing to investigate the issue.

  4. resolved Jul 23, 2026, 10:30 PM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

Read the full incident report →

Minor July 22, 2026

Customers may be unable to complete purchases on ecom.docusign.com (Incident 5438)

Detected by Pingoru
Jul 22, 2026, 08:04 PM UTC
Resolved
Jul 22, 2026, 09:15 PM UTC
Duration
1h 10m
Affected: NA1NA2NA3NA4
Timeline · 4 updates
  1. investigating Jul 22, 2026, 08:04 PM UTC

    We are actively investigating this issue.

  2. identified Jul 22, 2026, 08:10 PM UTC

    We have identified the issue and a fix is being implemented.

  3. identified Jul 22, 2026, 08:59 PM UTC

    The issue has been identified and we continue our work to implement a fix.

  4. resolved Jul 22, 2026, 09:15 PM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

Read the full incident report →

Minor July 17, 2026

Customers may experience errors loading PowerForms to sign envelopes (Incident 5417)

Detected by Pingoru
Jul 17, 2026, 05:33 PM UTC
Resolved
Jul 17, 2026, 05:54 PM UTC
Duration
20m
Affected: NA1NA2NA3NA4
Timeline · 3 updates
  1. investigating Jul 17, 2026, 05:33 PM UTC

    We are actively investigating this issue.

  2. identified Jul 17, 2026, 05:46 PM UTC

    We have identified the issue and a fix is being implemented.

  3. resolved Jul 17, 2026, 05:54 PM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

Read the full incident report →

Minor July 16, 2026

Customers may experience errors executing workflows and uploading documents (Incident 5386)

Detected by Pingoru
Jul 16, 2026, 03:27 AM UTC
Resolved
Jul 16, 2026, 03:33 AM UTC
Duration
6m
Affected: UAT NA11
Timeline · 3 updates
  1. investigating Jul 16, 2026, 03:27 AM UTC

    We are actively investigating this issue.

  2. identified Jul 16, 2026, 03:27 AM UTC

    We have identified the issue and a fix is being implemented.

  3. resolved Jul 16, 2026, 03:33 AM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

Read the full incident report →

Minor July 14, 2026

Some Document Generation customers are being redirected to the CLM home page (Incident 5384)

Detected by Pingoru
Jul 14, 2026, 08:48 PM UTC
Resolved
Jul 15, 2026, 01:49 AM UTC
Duration
5h 1m
Affected: NA11
Timeline · 4 updates
  1. investigating Jul 14, 2026, 08:48 PM UTC

    We are actively investigating this issue.

  2. investigating Jul 14, 2026, 09:41 PM UTC

    We are continuing to investigate this issue.

  3. identified Jul 14, 2026, 11:32 PM UTC

    We have identified the issue and a fix is being implemented.

  4. resolved Jul 15, 2026, 01:49 AM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

Read the full incident report →

Minor July 14, 2026

Some customers (including Notary customers) may not be able to authenticate via LexisNexis' Knowledge-Based Authentication, leading to failure in signing envelopes. (Incident 5383)

Detected by Pingoru
Jul 14, 2026, 05:09 PM UTC
Resolved
Jul 14, 2026, 07:08 PM UTC
Duration
1h 59m
Affected: NA1NA2NA3NA4CAAUEUDEMOJP1
Timeline · 5 updates
  1. investigating Jul 14, 2026, 05:09 PM UTC

    LexisNexis has been made aware of the issue and are currently investigating.

  2. investigating Jul 14, 2026, 05:44 PM UTC

    LexisNexis is continuing to investigate the issue.

  3. investigating Jul 14, 2026, 06:39 PM UTC

    LexisNexis is continuing to investigate the issue.

  4. monitoring Jul 14, 2026, 07:05 PM UTC

    LexisNexis has reported resolving the issue. We are continuing to monitor.

  5. resolved Jul 14, 2026, 07:08 PM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

Read the full incident report →

Minor July 13, 2026

Some customers may not able to open any CLM documents (Incident 5375)

Detected by Pingoru
Jul 13, 2026, 07:55 PM UTC
Resolved
Jul 13, 2026, 08:19 PM UTC
Duration
23m
Affected: EU11EU21
Timeline · 2 updates
  1. identified Jul 13, 2026, 07:55 PM UTC

    We have identified the issue and a fix is being implemented.

  2. resolved Jul 13, 2026, 08:19 PM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

Read the full incident report →

Minor July 8, 2026

Powerforms Intermittently Not Loading (Incident 5345)

Detected by Pingoru
Jul 08, 2026, 09:46 PM UTC
Resolved
Jul 08, 2026, 09:47 PM UTC
Duration
18s
Affected: DEMO
Timeline · 2 updates
  1. investigating Jul 08, 2026, 09:46 PM UTC

    We are actively investigating this issue.

  2. resolved Jul 08, 2026, 09:47 PM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

Read the full incident report →

Minor July 7, 2026

Intermittent Issues With Delivery of e-mail Notifications (Incident 5326)

Detected by Pingoru
Jul 07, 2026, 03:31 PM UTC
Resolved
Jul 07, 2026, 04:48 PM UTC
Duration
1h 16m
Affected: NA1NA2NA3NA4CAAUEUDEMOFedRAMPJP1
Timeline · 2 updates
  1. identified Jul 07, 2026, 03:31 PM UTC

    A subset of customers may experience intermittent failures of email notifications upon sending of envelopes. To mitigate this customers can log into their DocuSign account and access the envelope directly. Engineering teams have identified the issue and are currently working to resolve this issue.

  2. resolved Jul 07, 2026, 04:48 PM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

Read the full incident report →

Minor July 5, 2026

Intermittent Errors and Delays (Incident 5312)

Detected by Pingoru
Jul 05, 2026, 10:35 PM UTC
Resolved
Jul 05, 2026, 11:01 PM UTC
Duration
25m
Affected: NA11NA21
Timeline · 3 updates
  1. investigating Jul 05, 2026, 10:35 PM UTC

    We are actively investigating this issue.

  2. monitoring Jul 05, 2026, 10:50 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jul 05, 2026, 11:01 PM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Customers may have experienced errors from 2026-07-05 21:50 UTC until 2026-07-05 22:22 UTC.

Read the full incident report →

Minor June 30, 2026

Customers may experience latency (Incident 5259)

Detected by Pingoru
Jun 30, 2026, 11:18 AM UTC
Resolved
Jul 01, 2026, 05:25 PM UTC
Duration
1d 6h
Affected: NA11EU11EU21
Timeline · 7 updates
  1. investigating Jun 30, 2026, 11:18 AM UTC

    We are actively investigating this issue.

  2. investigating Jun 30, 2026, 12:36 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jun 30, 2026, 08:34 PM UTC

    We continue to investigate the issue and additional resources have been engaged.

  4. investigating Jun 30, 2026, 10:55 PM UTC

    We continue to investigate the issue and additional resources have been engaged.

  5. investigating Jul 01, 2026, 12:57 AM UTC

    We continue to investigate the issue and additional resources have been engaged. We will provide the next update in approximately 24 hours.

  6. identified Jul 01, 2026, 02:57 PM UTC

    We have identified the issue and a fix is being implemented.

  7. resolved Jul 01, 2026, 05:25 PM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

Read the full incident report →

Minor June 30, 2026

Some customers may experience errors with Sending and Signing (Incident 5252)

Detected by Pingoru
Jun 30, 2026, 12:25 AM UTC
Resolved
Jun 30, 2026, 12:37 AM UTC
Duration
11m
Affected: CA
Timeline · 3 updates
  1. investigating Jun 30, 2026, 12:25 AM UTC

    We are actively investigating this issue.

  2. identified Jun 30, 2026, 12:26 AM UTC

    We have identified the issue and a fix is being implemented.

  3. resolved Jun 30, 2026, 12:37 AM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

Read the full incident report →

Minor June 29, 2026

Customers may experience errors with Sending and Signing in NA3 (Incident 5247)

Detected by Pingoru
Jun 29, 2026, 09:32 PM UTC
Resolved
Jun 29, 2026, 10:00 PM UTC
Duration
27m
Affected: NA3
Timeline · 4 updates
  1. investigating Jun 29, 2026, 09:32 PM UTC

    We are actively investigating this issue.

  2. investigating Jun 29, 2026, 09:34 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Jun 29, 2026, 09:34 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jun 29, 2026, 10:00 PM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

Read the full incident report →

Minor June 28, 2026

Intermittent Errors and Delays (Incident 5219)

Detected by Pingoru
Jun 28, 2026, 06:49 AM UTC
Resolved
Jun 28, 2026, 07:47 AM UTC
Duration
58m
Affected: NA11NA21
Timeline · 3 updates
  1. investigating Jun 28, 2026, 06:49 AM UTC

    We are actively investigating this issue.

  2. identified Jun 28, 2026, 06:58 AM UTC

    We have identified the issue and a fix is being implemented.

  3. resolved Jun 28, 2026, 07:47 AM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

Read the full incident report →

Minor June 26, 2026

Some customers may experience latency for any sending actions that involve conversions, generating documents and accessing tasks (Incident 5190)

Detected by Pingoru
Jun 26, 2026, 06:06 PM UTC
Resolved
Jun 26, 2026, 08:13 PM UTC
Duration
2h 7m
Affected: NA11NA2NA21NA4S1.US
Timeline · 3 updates
  1. identified Jun 26, 2026, 06:06 PM UTC

    We have identified the issue and a fix is being implemented.

  2. monitoring Jun 26, 2026, 07:02 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 26, 2026, 08:13 PM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

Read the full incident report →

Minor June 25, 2026

Platform Latency in UAT (Incident 5187)

Detected by Pingoru
Jun 25, 2026, 08:44 AM UTC
Resolved
Jun 25, 2026, 01:01 PM UTC
Duration
4h 16m
Affected: UAT NA11
Timeline · 4 updates
  1. investigating Jun 25, 2026, 08:44 AM UTC

    Customers may be experiencing latency on the platform in the UAT Environment. Engineers have been engaged and are actively triaging this issue.

  2. identified Jun 25, 2026, 10:12 AM UTC

    We have identified the source of the issue and are preparing a fix.

  3. monitoring Jun 25, 2026, 10:27 AM UTC

    Fix has been implemented and we are now monitoring telemetry to validate.

  4. resolved Jun 25, 2026, 01:01 PM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

Read the full incident report →