DocuSign Outage History

DocuSign is up right now

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

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

Source: https://status.docusign.com

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 →

Minor April 28, 2026

Send Latency in EU (Incident 4776)

Detected by Pingoru
Apr 28, 2026, 09:03 AM UTC
Resolved
Apr 28, 2026, 09:40 AM UTC
Duration
37m
Affected: EU
Timeline · 4 updates
  1. investigating Apr 28, 2026, 09:03 AM UTC

    A subset of customers in EU may experience latency with Send operations. Engineering teams have been engaged and are actively triaging.

  2. identified Apr 28, 2026, 09:24 AM UTC

    Engineers have identified a root cause and are working on releasing a fix.

  3. monitoring Apr 28, 2026, 09:30 AM UTC

    A fix has been implemented and engineers are now monitoring telemetry to validate.

  4. resolved Apr 28, 2026, 09:40 AM UTC

    All telemetry is now reporting that this issue has been resolved.

Read the full incident report →

Minor April 23, 2026

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

Detected by Pingoru
Apr 23, 2026, 08:41 PM UTC
Resolved
Apr 23, 2026, 08:41 PM UTC
Duration
—
Affected: Salesforce
Timeline · 3 updates
  1. investigating Apr 23, 2026, 08:14 PM UTC

    We are currently investigating this issue.

  2. identified Apr 23, 2026, 08:27 PM UTC

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

  3. resolved Apr 23, 2026, 08:41 PM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Customers utilizing the Docusign App Launcher in Salesforce may have seen errors from 2026-04-23 04:40 PM UTC until 2026-04-23 08:35 PM UTC.

Read the full incident report →

Minor April 23, 2026

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

Detected by Pingoru
Apr 23, 2026, 04:28 PM UTC
Resolved
Apr 23, 2026, 11:18 PM UTC
Duration
6h 50m
Affected: NA1NA2NA3NA4CAAU
Timeline · 8 updates
  1. investigating Apr 23, 2026, 04:28 PM UTC

    We are currently investigating this issue.

  2. identified Apr 23, 2026, 05:07 PM UTC

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

  3. monitoring Apr 23, 2026, 05:31 PM UTC

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

  4. monitoring Apr 23, 2026, 07:18 PM UTC

    We continue to monitor the environment to ensure stability.

  5. monitoring Apr 23, 2026, 08:02 PM UTC

    We are continuing to monitor for any further issues.

  6. monitoring Apr 23, 2026, 09:23 PM UTC

    We are continuing to monitor for any further issues.

  7. monitoring Apr 23, 2026, 10:34 PM UTC

    We continue to monitor for stability while we investigate possible secondary factors.

  8. resolved Apr 23, 2026, 11:18 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 latency from 2026-04-23 02:53 PM UTC until 2026-04-23 08:09 PM UTC

Read the full incident report →

Minor April 23, 2026

Customers may experience intermittent latency and errors in Navigator (Incident 4748)

Detected by Pingoru
Apr 23, 2026, 03:27 PM UTC
Resolved
Apr 23, 2026, 11:10 PM UTC
Duration
7h 43m
Affected: NA2NA4
Timeline · 7 updates
  1. investigating Apr 23, 2026, 03:27 PM UTC

    We are currently investigating the issue.

  2. investigating Apr 23, 2026, 04:44 PM UTC

    We are continuing to investigate this issue.

  3. investigating Apr 23, 2026, 05:40 PM UTC

    More engineering teams have been engaged to triage this error and investigation is continuing.

  4. investigating Apr 23, 2026, 06:35 PM UTC

    We are continuing to investigate this issue.

  5. investigating Apr 23, 2026, 07:37 PM UTC

    We are continuing to investigate this issue.

  6. identified Apr 23, 2026, 09:21 PM UTC

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

  7. resolved Apr 23, 2026, 11:10 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 intermittent latency and errors in Navigator from 2026-04-23 12:57 PM UTC until 2026-04-23 11:12 PM UTC.

Read the full incident report →

Major April 17, 2026

Login failures and Latency Issues with Sending and Signing Envelopes (Incident 4717)

Detected by Pingoru
Apr 17, 2026, 02:47 PM UTC
Resolved
Apr 17, 2026, 04:18 PM UTC
Duration
1h 31m
Affected: CA
Timeline · 6 updates
  1. investigating Apr 17, 2026, 02:47 PM UTC

    We are currently investigating a spike in latency for send and sign services which may affect a subset of customers. We have engaged our engineering teams and are actively triaging this issue.

  2. identified Apr 17, 2026, 02:53 PM UTC

    Our engineering teams have identified the root cause of this issue and are in the process of deploying a fix.

  3. monitoring Apr 17, 2026, 03:12 PM UTC

    Internal testing is showing the implemented fix has resolved the impact, we are continuing to monitor to ensure the issue is fully mitigated.

  4. monitoring Apr 17, 2026, 03:57 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Apr 17, 2026, 04:18 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 login failures and latency issues with Sending and Signing from 2026-04-17 02:08 PM UTC until 2026-04-17 03:09 PM UTC

  6. postmortem Apr 21, 2026, 10:01 PM UTC

    # RCA for Docusign eSign Canada Service Disruption on April 17, 2026 ‌ ## Impact Summary: eSignature customers in Canada may have experienced latency and failures in sending, signing, and intermittent login errors on April 17, 2026 from 07:08 am PT to 08:10 am PT. ‌ ## Cause: A backend configuration change was made to increase the number of storage replication partners to improve performance and redundancy. This led to an increased volume of data-syncing activity, preventing the storage system from processing normal requests. ‌ ## Resolution: The configuration change was rolled back, removing the additional storage replication partners. Normal processing resumed, and the backlog of activity was completed. The additional replication partners will be added in the future more slowly, during slow traffic times, and closely monitored.

Read the full incident report →

Minor April 11, 2026

Intermittent Errors in UAT (Incident 4682)

Detected by Pingoru
Apr 11, 2026, 03:54 AM UTC
Resolved
Apr 11, 2026, 04:50 AM UTC
Duration
55m
Affected: UAT NA11
Timeline · 4 updates
  1. investigating Apr 11, 2026, 03:54 AM UTC

    Customers may experience intermittent errors, jobs not completing, and the inability to login to UAT.

  2. investigating Apr 11, 2026, 04:19 AM UTC

    We are continuing to investigate this issue.

  3. identified Apr 11, 2026, 04:41 AM UTC

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

  4. resolved Apr 11, 2026, 04:50 AM 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 intermittent errors, jobs not completing, and the inability to login to UAT from 2026-04-11 01:32 AM UTC April 11 until 2026-04-11 04:53 AM UTC.

Read the full incident report →

Minor April 9, 2026

User Membership Group Update Delays (Incident 4672)

Detected by Pingoru
Apr 09, 2026, 07:40 PM UTC
Resolved
Apr 09, 2026, 09:23 PM UTC
Duration
1h 43m
Affected: NA1AU
Timeline · 5 updates
  1. identified Apr 09, 2026, 07:40 PM UTC

    Changes to user membership groups is significantly delayed. We are making changes to reduce or remove the delay.

  2. identified Apr 09, 2026, 07:56 PM UTC

    NA1 is now back to normal operational expectations. We are working to resolve the issue in AU now.

  3. identified Apr 09, 2026, 08:39 PM UTC

    We are implementing a change to resolve the AU delay.

  4. monitoring Apr 09, 2026, 09:01 PM UTC

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

  5. resolved Apr 09, 2026, 09:23 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 delays from 2026-04-09 04:24 AM UTC until 2026-04-09 09:22 PM UTC.

Read the full incident report →

Notice March 18, 2026

Search Indexing Delays (Incident 4539)

Detected by Pingoru
Mar 18, 2026, 12:13 AM UTC
Resolved
Mar 18, 2026, 08:22 AM UTC
Duration
8h 8m
Affected: EU21
Timeline · 2 updates
  1. identified Mar 18, 2026, 12:13 AM UTC

    As a continuation of incident 4517, a subset of customers may experience incomplete search results for historical documents older than one year. A fix is currently underway, and full resolution is anticipated by Wednesday, March 18, 2026 at 11:00 AM UTC.

  2. resolved Mar 18, 2026, 08:22 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 March 12, 2026

Users may encounter errors while attempting to upload or edit documents. (Incident 4504)

Detected by Pingoru
Mar 12, 2026, 08:23 PM UTC
Resolved
Mar 12, 2026, 10:06 PM UTC
Duration
1h 43m
Affected: NA11NA21EU11EU21UAT NA11
Timeline · 6 updates
  1. investigating Mar 12, 2026, 06:15 PM UTC

    We are currently investigating this issue.

  2. identified Mar 12, 2026, 07:23 PM UTC

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

  3. identified Mar 12, 2026, 08:23 PM UTC

    We are continuing to work on a fix for this issue. We estimate the fix will be deployed by 22:30 UTC

  4. identified Mar 12, 2026, 08:49 PM UTC

    We are continuing to work on a fix for this issue. We estimate the fix will be deployed by 22:30 UTC

  5. monitoring Mar 12, 2026, 09:41 PM UTC

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

  6. resolved Mar 12, 2026, 10:24 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 March 6, 2026

Users may experience delays or failures when attempting to upload documents via the MuleSoft API (incident 4455)

Detected by Pingoru
Mar 06, 2026, 05:37 PM UTC
Resolved
Mar 06, 2026, 06:57 PM UTC
Duration
1h 20m
Affected: NA11NA21EU11EU21
Timeline · 3 updates
  1. identified Mar 06, 2026, 05:37 PM UTC

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

  2. monitoring Mar 06, 2026, 06:49 PM UTC

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

  3. resolved Mar 06, 2026, 07:07 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 March 4, 2026

eSign Prod: Customers using Authorize.net to Include a One-Time Payment Request may experience issues completing envelopes (Incident 4445)

Detected by Pingoru
Mar 04, 2026, 06:45 PM UTC
Resolved
Mar 05, 2026, 08:50 PM UTC
Duration
1d 2h
Affected: NA1NA2NA3NA4
Timeline · 5 updates
  1. investigating Mar 04, 2026, 06:45 PM UTC

    We are currently investigating this issue.

  2. investigating Mar 04, 2026, 07:26 PM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 04, 2026, 11:22 PM UTC

    We are continuing to investigate this issue.

  4. investigating Mar 05, 2026, 04:41 PM UTC

    Our team is working closely with the payment gateway to resolve the issue. We are monitoring the situation and will post an update here as soon as we receive one.

  5. resolved Mar 05, 2026, 08:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 24, 2026

Customers may experience latency when sending and signing (Incident 4392)

Detected by Pingoru
Feb 24, 2026, 10:04 AM UTC
Resolved
Feb 24, 2026, 11:59 AM UTC
Duration
1h 54m
Affected: DEMO
Timeline · 2 updates
  1. investigating Feb 24, 2026, 10:04 AM UTC

    We are currently investigating the issue.

  2. resolved Feb 24, 2026, 11:59 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 February 17, 2026

A Subset of Customers May Experience Intermittent Latency When Sending or Receiving (Incident-4356)

Detected by Pingoru
Feb 17, 2026, 02:57 PM UTC
Resolved
Feb 17, 2026, 03:51 PM UTC
Duration
54m
Affected: NA1NA3
Timeline · 2 updates
  1. investigating Feb 17, 2026, 02:57 PM UTC

    A subset of customers may be experiencing intermittent latency on executing send and receive jobs. Our engineering teams are engaged on this and are actively triaging.

  2. resolved Feb 17, 2026, 03: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 February 16, 2026

Users may experience slowness and failures during content uploads and downloads (Incident 4352)

Detected by Pingoru
Feb 16, 2026, 09:26 PM UTC
Resolved
Feb 16, 2026, 10:19 PM UTC
Duration
53m
Affected: EU21
Timeline · 3 updates
  1. investigating Feb 16, 2026, 09:26 PM UTC

    We are currently investigating this issue.

  2. identified Feb 16, 2026, 09:50 PM UTC

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

  3. resolved Feb 16, 2026, 10:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 15, 2026

CLM Prod NA11 Customers are experiencing issues accessing their accounts and performing actions (Incident 4348)

Detected by Pingoru
Feb 15, 2026, 08:50 PM UTC
Resolved
Feb 15, 2026, 09:56 PM UTC
Duration
1h 6m
Affected: NA11
Timeline · 3 updates
  1. investigating Feb 15, 2026, 08:50 PM UTC

    We are currently investigating this issue.

  2. identified Feb 15, 2026, 09:45 PM UTC

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

  3. resolved Feb 15, 2026, 09:56 PM UTC

    This incident has been resolved. Some customers may have experienced errors or delays with login, browsing, generating, or previewing documents from 2026-02-15 07:47 PM UTC until 2026-02-15 09:57 PM UTC.

Read the full incident report →

Minor February 15, 2026

Customers may observe degradation in Demo/UAT for Navigator, Prepare, Webforms, and IAM ingestion (Incident 4346)

Detected by Pingoru
Feb 15, 2026, 02:10 PM UTC
Resolved
Feb 15, 2026, 05:26 PM UTC
Duration
3h 16m
Affected: DEMODEMO
Timeline · 6 updates
  1. investigating Feb 15, 2026, 02:10 PM UTC

    Some DEMO/UAT customers may experience issues with several functionalities including but not limited to: - Webforms fail to save - Document ingestion failure - ID verification fields and healthcare fields not available in prepare - Parts of Navigator failure to load

  2. investigating Feb 15, 2026, 04:18 PM UTC

    We are continuing to investigate this issue with Microsoft.

  3. identified Feb 15, 2026, 05:02 PM UTC

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

  4. identified Feb 15, 2026, 05:13 PM UTC

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

  5. monitoring Feb 15, 2026, 05:13 PM UTC

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

  6. resolved Feb 15, 2026, 05:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 3, 2026

A Subset of Customers May Experience Issues Accessing Insight Product (Incident 4256)

Detected by Pingoru
Feb 03, 2026, 02:01 PM UTC
Resolved
Feb 03, 2026, 10:05 PM UTC
Duration
8h 4m
Affected: NA.WNA.E
Timeline · 5 updates
  1. identified Feb 03, 2026, 02:01 PM UTC

    A subset of customers may still be experiencing issues with accessing their Insight product after the maintenance window. Our engineering teams are actively engaged and in progress of remediation.

  2. identified Feb 03, 2026, 03:29 PM UTC

    Our engineering teams are continuing efforts to restore functionality to affected customers.

  3. identified Feb 03, 2026, 05:25 PM UTC

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

  4. identified Feb 03, 2026, 07:27 PM UTC

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

  5. resolved Feb 03, 2026, 10:05 PM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. A subset of customers may have experienced issues accessing Insight product from 2026-02-03 12:55 AM UTC until 2026-02-03 10:04 PM UTC.

Read the full incident report →

Minor February 2, 2026

Customers may experience latency when attempting to load the admin console (DIRCA-4249)

Detected by Pingoru
Feb 02, 2026, 04:15 PM UTC
Resolved
Feb 02, 2026, 05:07 PM UTC
Duration
52m
Affected: NA1NA2NA3NA4EU
Timeline · 3 updates
  1. investigating Feb 02, 2026, 04:15 PM UTC

    We are currently investigating the issue.

  2. monitoring Feb 02, 2026, 04:27 PM UTC

    Performance has improved and we are monitoring.

  3. resolved Feb 02, 2026, 05:07 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 January 30, 2026

Failures Sending SMS Notifications to Japan Recipients (DIRCA-4145)

Detected by Pingoru
Jan 30, 2026, 06:56 PM UTC
Resolved
Jan 15, 2026, 01:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jan 30, 2026, 06:56 PM UTC

    Some customers experienced a failure to deliver SMS notifications to Japanese cell phone recipients due to a telecom outage. Customers may have experienced errors from 2026-01-15 12:42:18 AM UTC to 2026-1-16 11:16:00 AM UTC.

Read the full incident report →

Minor January 29, 2026

Users may experience issues with tabs being automatically deleted during envelope creation (DIRCA-4228)

Detected by Pingoru
Jan 29, 2026, 04:53 PM UTC
Resolved
Jan 29, 2026, 05:19 PM UTC
Duration
26m
Affected: NA1NA2NA3NA4CAAUEUDEMOFedRAMPUSFEDJP1
Timeline · 4 updates
  1. identified Jan 29, 2026, 04:53 PM UTC

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

  2. identified Jan 29, 2026, 04:59 PM UTC

    Temporary Workaround Customers can switch back to the old User Interface by following these steps: Go to Admin Select Sending Settings Disable “New Sending Experience” Save changes

  3. monitoring Jan 29, 2026, 05:17 PM UTC

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

  4. resolved Jan 29, 2026, 05:19 PM UTC

    Clients should no longer experience issues with tabs being automatically deleted during envelope creation. If issues persist, clients are advised to log out and log back in.

Read the full incident report →