DocuSign Outage History

DocuSign degraded · 1 active incident View live status →

DocuSign had 78 outages in the last 2 years totaling 79h 2m of downtime — averaging 3.2 incidents per month.

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

Source: https://status.docusign.com

Minor June 16, 2026

Salesforce for Gen customers are unable to generate documents (Incident-5122)

Detected by Pingoru
Jun 16, 2026, 04:52 PM UTC
Resolved
Jun 16, 2026, 11:30 PM UTC
Duration
6h 37m
Affected: NA11NA21EU11EU21
Timeline · 8 updates
  1. investigating Jun 16, 2026, 04:52 PM UTC

    We are actively investigating this issue.

  2. investigating Jun 16, 2026, 04:54 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jun 16, 2026, 05:59 PM UTC

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

  4. investigating Jun 16, 2026, 06:28 PM UTC

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

  5. investigating Jun 16, 2026, 08:46 PM UTC

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

  6. identified Jun 16, 2026, 10:00 PM UTC

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

  7. identified Jun 16, 2026, 10:01 PM UTC

    We are continuing to work on a fix for this issue.

  8. resolved Jun 16, 2026, 11: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 →

Notice June 16, 2026

Customers may experience intermittent latency (Incident 5118)

Detected by Pingoru
Jun 16, 2026, 08:37 AM UTC
Resolved
Jun 16, 2026, 05:18 PM UTC
Duration
8h 41m
Affected: UAT NA11
Timeline · 4 updates
  1. investigating Jun 16, 2026, 08:37 AM UTC

    We are actively investigating this issue.

  2. investigating Jun 16, 2026, 10:34 AM UTC

    We are continuing to investigate this issue.

  3. investigating Jun 16, 2026, 03:20 PM UTC

    We continue to investigate the issue. Performance has improved but the issue is still under investigation.

  4. resolved Jun 16, 2026, 05:18 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 June 15, 2026

Users may experience performance latency when utilizing the doc2pdf service (Incident 5085)

Detected by Pingoru
Jun 15, 2026, 05:24 PM UTC
Resolved
Jun 15, 2026, 06:29 PM UTC
Duration
1h 4m
Affected: NA1NA2CAAU
Timeline · 2 updates
  1. identified Jun 15, 2026, 05:24 PM UTC

    We are have identified the root cause and we are implementing a fix.

  2. resolved Jun 15, 2026, 06:29 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 15, 2026

Email notifications sent from custom domains may not be delivered (Incident 5106)

Detected by Pingoru
Jun 15, 2026, 02:00 PM UTC
Resolved
Jun 15, 2026, 02:51 PM UTC
Duration
50m
Affected: DEMOUAT NA11DEMO S1
Timeline · 2 updates
  1. investigating Jun 15, 2026, 02:00 PM UTC

    We are actively investigating the issue.

  2. resolved Jun 15, 2026, 02:51 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 12, 2026

Notification failures when utilising Outlook (Incident 5087)

Detected by Pingoru
Jun 12, 2026, 06:04 AM UTC
Resolved
Jun 12, 2026, 06:37 AM UTC
Duration
33m
Affected: NA1NA2NA3NA4CAAUEUJP1
Timeline · 3 updates
  1. investigating Jun 12, 2026, 06:04 AM UTC

    Customers utilising Outlook may receive delivery notification failures when sending envelopes to signers. Engineering teams have been engaged and we are actively triaiging this issue.

  2. monitoring Jun 12, 2026, 06:10 AM UTC

    A fix has been applied and our engineering teams are actively reviewing our telemetry to confirm this fix has mitigated the issue.

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

    We can confirm that this issue is now resolved, thank you for your patience.

Read the full incident report →

Notice June 11, 2026

Users may encounter errors when attempting to process envelopes (Incident 5072)

Detected by Pingoru
Jun 11, 2026, 07:45 PM UTC
Resolved
Jun 11, 2026, 09:50 PM UTC
Duration
2h 5m
Affected: DEMO
Timeline · 2 updates
  1. investigating Jun 11, 2026, 07:45 PM UTC

    We are investigating this issue.

  2. resolved Jun 11, 2026, 09:50 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 11, 2026

Document Upload and Generation Errors (Incident 5073)

Detected by Pingoru
Jun 11, 2026, 07:03 PM UTC
Resolved
Jun 11, 2026, 11:21 PM UTC
Duration
4h 18m
Affected: NA11NA2NA21NA4S1.US
Timeline · 8 updates
  1. investigating Jun 11, 2026, 07:03 PM UTC

    We are actively investigating this issue.

  2. investigating Jun 11, 2026, 07:49 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jun 11, 2026, 08:19 PM UTC

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

  4. investigating Jun 11, 2026, 08:34 PM UTC

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

  5. investigating Jun 11, 2026, 09:52 PM UTC

    We continue to investigate the issue.

  6. identified Jun 11, 2026, 10:05 PM UTC

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

  7. monitoring Jun 11, 2026, 10:13 PM UTC

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

  8. resolved Jun 11, 2026, 11:21 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 5, 2026

CLM: Resolved Authentication/Access Issues in EU11 (Incident 5040)

Detected by Pingoru
Jun 05, 2026, 11:03 PM UTC
Resolved
Jun 05, 2026, 11:03 PM UTC
Duration
—
Affected: EU11
Timeline · 1 update
  1. resolved Jun 05, 2026, 11:03 PM UTC

    An unexpected system dependency caused a temporary service disruption affecting a subset of accounts in the CLM EU11 environment between 21:09 UTC and 22:40 UTC on June 5, 2026. During this time, impacted users may have experienced authentication errors or issues accessing certain features. 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-06-05 21:09 UTC until 2026-06-05 22:40 UTC

Read the full incident report →

Minor June 5, 2026

Customers Unable to Purchase Plans (Incident 5034)

Detected by Pingoru
Jun 05, 2026, 10:02 PM UTC
Resolved
Jun 05, 2026, 10:32 PM UTC
Duration
29m
Timeline · 4 updates
  1. investigating Jun 05, 2026, 10:02 PM UTC

    We are actively investigating this issue.

  2. identified Jun 05, 2026, 10:15 PM UTC

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

  3. monitoring Jun 05, 2026, 10:22 PM UTC

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

  4. resolved Jun 05, 2026, 10:32 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 4, 2026

Organization Reports May Remain in "Exporting" Status (Incident 5020)

Detected by Pingoru
Jun 04, 2026, 06:58 AM UTC
Resolved
Jun 04, 2026, 12:00 PM UTC
Duration
5h 1m
Affected: NA1NA2NA3NA4CAAUEUDEMOFedRAMP
Timeline · 3 updates
  1. identified Jun 04, 2026, 06:58 AM UTC

    Customers may be experiencing issues when attempting to export reports. Our engineering teams are engaged and have identified the cause and are working on a fix for this.

  2. identified Jun 04, 2026, 09:07 AM UTC

    We are continuing to work on a fix for the issue.

  3. resolved Jun 04, 2026, 12:00 PM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Any organization reports that failed to complete during the incident can be manually re-created and run. Any scheduled reports will complete in the next run, again customers can manually create and run these sooner if required. Customers may have experienced errors from 2026-06-03 05:00 AM UTC until 2026-06-04 10:50 AM UTC.

Read the full incident report →

Minor June 2, 2026

Customers dependent on deprecated TLS ciphers will experience interruption (Incident-5003)

Detected by Pingoru
Jun 02, 2026, 11:32 PM UTC
Resolved
Jun 03, 2026, 12:55 AM UTC
Duration
1h 23m
Affected: NA1NA11NA2NA21NA3US11NA4US12EU11CAAUEU21EUUS13
Timeline · 4 updates
  1. investigating Jun 02, 2026, 11:32 PM UTC

    We are currently investigating this issue.

  2. identified Jun 02, 2026, 11:50 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jun 02, 2026, 11:56 PM UTC

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

  4. resolved Jun 03, 2026, 12:55 AM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Some customers dependent on deprecated TLS ciphers may have experienced interruptions from 2026-06-02 10:49 PM UTC until 2026-06-03 12:49 AM UTC.

Read the full incident report →

Minor May 28, 2026

Issues utilising +86 country code for sending envelopes and phone authentication (Incident 4968)

Detected by Pingoru
May 28, 2026, 02:51 PM UTC
Resolved
May 28, 2026, 04:29 PM UTC
Duration
1h 37m
Affected: NA1NA2NA3NA4CAAUEUDEMOFedRAMPUSFEDJP1
Timeline · 3 updates
  1. identified May 28, 2026, 02:51 PM UTC

    Customers attempting to send an envelope or use SMS/Phone Authentication for Envelopes utilising a +86 will experience errors during this process. Engineering teams have been engaged and triage is underway.

  2. identified May 28, 2026, 03:50 PM UTC

    Engineers have identified the root cause and are executing a fix.

  3. resolved May 28, 2026, 04:29 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 May 21, 2026

Salesforce is experiencing an outage that may impact customers using the Salesforce integration (Incident-4935)

Detected by Pingoru
May 21, 2026, 11:12 PM UTC
Resolved
May 22, 2026, 03:54 AM UTC
Duration
4h 42m
Affected: Salesforce
Timeline · 2 updates
  1. investigating May 21, 2026, 11:12 PM UTC

    Salesforce is experiencing an outage that may impact customers using the Salesforce integration. Docusign services are not experiencing any outages at this time. The issue will resolve when Salesforce resolves their outage.

  2. resolved May 22, 2026, 03:54 AM UTC

    Salesforce has resolved their incident which may have impacted customers using the Salesforce integration.

Read the full incident report →

Minor May 19, 2026

Some customers may experience latencies sending and signing in EU (Incident-4915)

Detected by Pingoru
May 19, 2026, 12:59 PM UTC
Resolved
May 19, 2026, 02:36 PM UTC
Duration
1h 36m
Affected: EU
Timeline · 3 updates
  1. investigating May 19, 2026, 12:59 PM UTC

    We are currently investigating the issue.

  2. investigating May 19, 2026, 01:30 PM UTC

    We are continuing to investigate the issue.

  3. resolved May 19, 2026, 02:36 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 May 18, 2026

Users may experience report failures and loading delays in the EU11 and EU21 sites (incident 4896)

Detected by Pingoru
May 18, 2026, 02:30 PM UTC
Resolved
May 18, 2026, 02:30 PM UTC
Duration
—
Affected: EU11EU21
Timeline · 1 update
  1. resolved May 18, 2026, 02:30 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-05-18 12:00 PM UTC until 2026-05-18 01:45 PM UTC.

Read the full incident report →

Minor May 14, 2026

Users may experience document report failures and loading delays in the EU11 and EU21 sites (incident 4863)

Detected by Pingoru
May 14, 2026, 06:45 PM UTC
Resolved
May 14, 2026, 08:03 PM UTC
Duration
1h 17m
Affected: EU11EU21
Timeline · 4 updates
  1. investigating May 14, 2026, 06:45 PM UTC

    We are currently investigating this issue.

  2. identified May 14, 2026, 07:23 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring May 14, 2026, 07:54 PM UTC

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

  4. resolved May 14, 2026, 08:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 13, 2026

Workflow Reports Experiencing Timeout Errors (Incident 4874)

Detected by Pingoru
May 13, 2026, 11:49 AM UTC
Resolved
May 13, 2026, 02:18 PM UTC
Duration
2h 28m
Affected: EU11EU21
Timeline · 4 updates
  1. identified May 13, 2026, 11:49 AM UTC

    Customers may be experiencing timeout errors with Workflow and Document Reports. Engineering teams have been engaged and the issue has been identified, a fix is currently being implemented.

  2. identified May 13, 2026, 11:50 AM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring May 13, 2026, 01:41 PM UTC

    A fix has been implemented and we are observing telemetry to validate.

  4. resolved May 13, 2026, 02:18 PM UTC

    This incident has now been resolved.

Read the full incident report →

Minor May 12, 2026

Users may experience timeouts when attempting to complete document transactions (Incident 4866)

Detected by Pingoru
May 12, 2026, 06:17 PM UTC
Resolved
May 12, 2026, 08:58 PM UTC
Duration
2h 40m
Affected: EU
Timeline · 6 updates
  1. investigating May 12, 2026, 06:17 PM UTC

    We are currently investigating this issue.

  2. identified May 12, 2026, 06:43 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified May 12, 2026, 07:33 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring May 12, 2026, 07:51 PM UTC

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

  5. monitoring May 12, 2026, 08:51 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved May 12, 2026, 08:58 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 May 12, 2026

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

Detected by Pingoru
May 12, 2026, 01:42 PM UTC
Resolved
May 12, 2026, 07:26 PM UTC
Duration
5h 44m
Affected: NA11NA21US11US12EU11EU21US13UAT NA11DEMO S1S1.USS2.USS1.EUS1.AU
Timeline · 6 updates
  1. identified May 12, 2026, 01:42 PM UTC

    We are currently investigating an issue where a subset of customers utilising a particular firewall may experience issues when attempting to switch to CLM. To restore access, please contact your IT department or security team and request that the following URL be unblocked/allowed: https://login.springcm.com Once this URL has been added to your allowlist, you should be able to log in without any further issues. Further investigation with our engineering teams is underway to fully resolve this issue.

  2. identified May 12, 2026, 02:23 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring May 12, 2026, 02:24 PM UTC

    Our engineering teams have deployed a fix and we are now monitoring to validate.

  4. identified May 12, 2026, 03:20 PM UTC

    Additional Engineering teams have been engaged to triage this issue, the current workaround is still functional: To restore access, please contact your IT department or security team and request that the following URL be unblocked/allowed: https://login.springcm.com Once this URL has been added to your allowlist, you should be able to log in without any further issues. Further investigation with our engineering teams is underway to fully resolve this issue.

  5. monitoring May 12, 2026, 03:55 PM UTC

    A fix has now been implemented and we are seeing improvements, we will continue monitoring telemetry to ensure the fix is final.

  6. resolved May 12, 2026, 07:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 12, 2026

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

Detected by Pingoru
May 12, 2026, 08:46 AM UTC
Resolved
May 12, 2026, 10:44 AM UTC
Duration
1h 58m
Affected: NA11NA21US11US12EU11EU21US13UAT NA11DEMO S1S1.USS2.USS1.EUS1.AU
Timeline · 3 updates
  1. investigating May 12, 2026, 08:46 AM UTC

    A subset of customers may be experiencing connection errors in the UI when attempting to switch to CLM. Engineering teams have been engaged and are actively triaging this issue.

  2. investigating May 12, 2026, 09:45 AM UTC

    Additional teams have been engaged to triage this issue.

  3. resolved May 12, 2026, 10:44 AM UTC

    Further investigation has confirmed that this error was the result of a third party and the impact has been resolved.

Read the full incident report →

Critical May 8, 2026

AU Site Outage (Incident 4840)

Detected by Pingoru
May 08, 2026, 03:24 AM UTC
Resolved
May 08, 2026, 03:24 AM UTC
Duration
—
Affected: AU
Timeline · 5 updates
  1. investigating May 08, 2026, 02:09 AM UTC

    We are currently investigating this issue.

  2. investigating May 08, 2026, 02:35 AM UTC

    We are continuing to investigate this issue.

  3. monitoring May 08, 2026, 03:03 AM UTC

    We have implemented a mitigation and are monitoring the results.

  4. resolved May 08, 2026, 03:24 AM UTC

    This incident has been resolved.

  5. postmortem May 08, 2026, 07:55 PM UTC

    # RCA for Docusign eSign Australia Service Disruption on May 8, 2026 # Article Title: RCA for Docusign eSign Australia Service Disruption on Month 8, 2026 ‌ # Impact Summary: Customers may have observed a service disruption from 01:45 AM UTC until 03:13AM UTC on May 8, 2026. During this time users were unable to log in, send envelopes for signature, or complete signing. ‌ # Cause: An unscheduled Microsoft Azure event triggered a service disruption. Due to the event, the databases were in an unhealthy state that necessitated manual intervention. ‌ # Resolution: Application traffic was manually re-routed to restore service. We worked with Microsoft to restore the databases to a healthy state.

Read the full incident report →