DocuSign Outage History

DocuSign is up right now

There were 21 DocuSign outages since February 3, 2026 totaling 159h 45m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.docusign.com

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 →

Minor March 27, 2026

Issues in UAT and DEMO S1 when attempting to complete tasks in task groups (Incident 4591)

Detected by Pingoru
Mar 27, 2026, 11:33 PM UTC
Resolved
Mar 27, 2026, 11:33 PM UTC
Duration
—
Affected: UAT NA11DEMO S1
Timeline · 9 updates
  1. investigating Mar 27, 2026, 12:41 PM UTC

    Due to a recently identified issue in our UAT environments, tasks may be routed incorrectly, leading to failures. Our team is actively working on identifying the root cause and mitigating it, and we will keep you updated as progress is made. Please note that any workflows and tasks on your Production environment should not be affected, and will still be executed normally.

  2. investigating Mar 27, 2026, 02:26 PM UTC

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

  3. identified Mar 27, 2026, 02:59 PM UTC

    A potential cause has been identified, engineering teams are reproducing the issue and reviewing telemetry before applying a fix.

  4. identified Mar 27, 2026, 03:42 PM UTC

    Engineers are continuing to triage and develop a fix to the identified issue.

  5. identified Mar 27, 2026, 04:21 PM UTC

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

  6. identified Mar 27, 2026, 05:22 PM UTC

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

  7. identified Mar 27, 2026, 09:00 PM UTC

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

  8. monitoring Mar 27, 2026, 10:39 PM UTC

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

  9. resolved Mar 27, 2026, 11:33 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 issues from 2026-03-27 12:32 AM UTC until 2026-03-27 11:30 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 →

Critical March 14, 2026

CLM & Docusign Gen for Salesforce Customers may be having difficulties accessing EU sites (Incident 4517)

Detected by Pingoru
Mar 14, 2026, 04:54 PM UTC
Resolved
Mar 17, 2026, 11:40 PM UTC
Duration
3d 6h
Affected: US11US12EU11EU21US13
Timeline · 45 updates
  1. investigating Mar 14, 2026, 02:07 AM UTC

    We are currently investigating this issue.

  2. investigating Mar 14, 2026, 02:08 AM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 14, 2026, 02:27 AM UTC

    We are continuing to investigate this issue.

  4. identified Mar 14, 2026, 02:42 AM UTC

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

  5. identified Mar 14, 2026, 03:11 AM UTC

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

  6. identified Mar 14, 2026, 06:07 AM UTC

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

  7. identified Mar 14, 2026, 09:17 AM UTC

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

  8. identified Mar 14, 2026, 09:19 AM UTC

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

  9. identified Mar 14, 2026, 02:44 PM UTC

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

  10. identified Mar 14, 2026, 03:59 PM UTC

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

  11. monitoring Mar 14, 2026, 04:54 PM UTC

    A fix has been implemented for US sites as of approximately 09:00 UTC.

  12. identified Mar 14, 2026, 04:58 PM UTC

    We are continuing to work on a fix for EU21 customers. EU21 customers may observe issues accessing the site. EU11 customers may see intermittent issues generating documents.

  13. identified Mar 14, 2026, 06:27 PM UTC

    We are continuing to remediate impact to EU11 and EU21 customers.

  14. identified Mar 14, 2026, 08:24 PM UTC

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

  15. identified Mar 14, 2026, 10:09 PM UTC

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

  16. identified Mar 14, 2026, 11:11 PM UTC

    We are continuing to remediate impact to EU21 customers.

  17. monitoring Mar 14, 2026, 11:41 PM UTC

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

  18. monitoring Mar 15, 2026, 04:23 AM UTC

    We are continuing to monitor for any further issues.

  19. identified Mar 15, 2026, 08:30 AM UTC

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

  20. identified Mar 15, 2026, 11:40 AM UTC

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

  21. identified Mar 15, 2026, 05:17 PM UTC

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

  22. identified Mar 15, 2026, 08:00 PM UTC

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

  23. identified Mar 15, 2026, 10:31 PM UTC

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

  24. identified Mar 15, 2026, 11:25 PM UTC

    We have identified that the recovery of EU21 will require the failover of our compute systems. This is a complex operation and will take some time. We will provide updates every 2 hours as recovery progresses.

  25. identified Mar 16, 2026, 12:51 AM UTC

    We are continuing to work through failover steps.

  26. identified Mar 16, 2026, 02:47 AM UTC

    We are continuing to work through failover steps.

  27. identified Mar 16, 2026, 03:31 AM UTC

    We have identified an intermittent degradation in our EU11 environment and are working on fixing it.

  28. identified Mar 16, 2026, 04:49 AM UTC

    We are continuing to work through the failover steps for EU21. Meanwhile, we have implemented a fix and are seeing improved stability on our EU11 environment.

  29. identified Mar 16, 2026, 06:59 AM UTC

    We are continuing to work through the failover steps for EU21. Meanwhile, we have implemented a fix and are seeing improved stability on our EU11 environment.

  30. identified Mar 16, 2026, 08:27 AM UTC

    We are continuing to work through the failover steps for EU21. We are now seeing additional impact to our EU11 site and have engaged further engineering resources to triage.

  31. identified Mar 16, 2026, 08:58 AM UTC

    We are continuing to work through the failover steps for EU21. We have identified the issue with EU11 and are now working to implement a fix to restore service.

  32. identified Mar 16, 2026, 09:32 AM UTC

    We are still continuing to work through the failover steps for EU21. Engineering teams are still triaging issues on EU11.

  33. identified Mar 16, 2026, 10:46 AM UTC

    We are still continuing to work through the failover steps for EU21. Eu11 Remains in a degraded state, additional engineering teams haven been engaged and triage is continuing.

  34. identified Mar 16, 2026, 11:03 AM UTC

    We are still continuing to work through the failover steps for EU21. EU11 is now showing signs of recovery and we are continuing to monitor the health of the site to ensure stability.

  35. identified Mar 16, 2026, 11:12 AM UTC

    We are still continuing to work through the failover steps for EU21, additional engineering resources have been engaged. EU11 is now full recovered.

  36. identified Mar 16, 2026, 12:49 PM UTC

    We are still continuing to work through the failover steps for EU21.

  37. identified Mar 16, 2026, 03:15 PM UTC

    We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.

  38. identified Mar 16, 2026, 05:19 PM UTC

    We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.

  39. identified Mar 16, 2026, 07:25 PM UTC

    We are still continuing to work through the failover steps for EU21, extensive testing is underway as part of the validation process.

  40. identified Mar 16, 2026, 10:03 PM UTC

    The failover steps for EU21 are nearing completion. A subset of customers have been enabled and we are monitoring carefully.

  41. monitoring Mar 17, 2026, 12:51 AM UTC

    A fix has been implemented and we are monitoring the results. Customers may notice some visual issues, such as custom logos not appearing. Services are functional.

  42. monitoring Mar 17, 2026, 04:36 AM UTC

    We continue to monitor the environment to ensure stability. Updates will be posted less often during monitoring unless a significant issue develops. Customers may notice some visual issues, such as custom logos not appearing. Services are functional.

  43. monitoring Mar 17, 2026, 07:40 PM UTC

    We continue to monitor the environment to ensure stability. Any company logos that were missing or outdated have been updated.

  44. resolved Mar 17, 2026, 11:40 PM UTC

    The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. An RCA is anticipated to be shared here by 2026-03-19 12:00 AM UTC

  45. postmortem Mar 18, 2026, 11:47 PM UTC

    ## RCA for CLM EU11, EU21, US11, US12, US13 Service Disruption Beginning March 14, 2026 ### Impact Summary: Some CLM sites experienced a service disruption impacting some users’ ability to access the site. The impacted time windows are noted below: * US11: 2026-03-14 1:20 AM UTC to 2026-03-14 9:20 AM UTC * US12: 2026-03-14 1:20 AM UTC to 2026-03-14 10:15 AM UTC * US13: 2026-03-14 1:20 AM UTC to 2026-03-14 7:35 AM UTC * EU11: 2026-03-16 8:05 PM UTC to 2026-03-16 10:45 PM UTC * EU21: 2026-03-14 1:20 AM UTC to 2026-03-17 00:15 AM UTC Customers in EU11 may have observed degradations across various operations from 03/14/2026 02:50 UTC to 03/14/2026 03:10 UTC, and 03/16/2026 01:25 UTC to 03/16/2026 03:55 UTC. Following initial recovery, some EU21 customers may have experienced the following issues until 2026-03-17 22:23 UTC: missing historical search results, failures in workflows involving search steps, missing or outdated company logos, and inaccurate reporting of Docusign envelope statuses. ### Cause: The issue was triggered by a planned security update applied to infrastructure supporting our application services. Once issues were identified, the update was rolled back. While the rollback completed successfully in unaffected environments, it did not fully complete in all cases, resulting in a subset of infrastructure entering a degraded or failed state. ### Resolution: In US11, US12 and US13 sites, recovery was achieved and service was restored by resetting affected clusters and restarting application services that had entered a failed state. EU11 required rebuilding a cluster to reallocate services and restore regular operations. Recovery efforts in EU21 required additional remediation steps and took longer to stabilize. Multiple parallel efforts were executed in an attempt to restore the failed clusters and we ultimately initiated a failover to alternate infrastructure to complete recovery and restore services.

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 →

Critical March 10, 2026

A subset of Insight customers may experience issues accessing the Product (Incident 4480)

Detected by Pingoru
Mar 10, 2026, 04:12 PM UTC
Resolved
Mar 11, 2026, 12:24 AM UTC
Duration
8h 11m
Affected: North America WestNorth America Central
Timeline · 10 updates
  1. investigating Mar 10, 2026, 04:12 PM UTC

    We are currently investigating this issue.

  2. investigating Mar 10, 2026, 04:58 PM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 10, 2026, 05:28 PM UTC

    We are continuing to investigate this issue.

  4. investigating Mar 10, 2026, 06:11 PM UTC

    Incident is actively being investigated.

  5. identified Mar 10, 2026, 06:49 PM UTC

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

  6. identified Mar 10, 2026, 08:15 PM UTC

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

  7. monitoring Mar 10, 2026, 09:04 PM UTC

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

  8. monitoring Mar 10, 2026, 10:02 PM UTC

    We are continuing to monitor for any further issues.

  9. monitoring Mar 10, 2026, 11:21 PM UTC

    We are continuing to monitor for any further issues.

  10. resolved Mar 11, 2026, 12:24 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 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: North America WestNorth America East
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 3, 2026

Customers may observe degradation (DIRCA-4253)

Detected by Pingoru
Feb 03, 2026, 05:41 AM UTC
Resolved
Feb 03, 2026, 05:41 AM UTC
Duration
—
Affected: NA11NA21EU11EU21
Timeline · 5 updates
  1. identified Feb 03, 2026, 03:29 AM UTC

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

  2. monitoring Feb 03, 2026, 03:48 AM UTC

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

  3. monitoring Feb 03, 2026, 05:00 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Feb 03, 2026, 05:41 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 degradation from 2026-02-02 11:04 PM UTC until 2026-02-03 05:42 AM UTC.

  5. postmortem Feb 04, 2026, 09:49 PM UTC

    **Incident Time Frame** 2026-02-02 11:04 PM UTC to 2026-02-03 05:42 AM UTC **Cause:** An operating system update was installed on CLM infrastructure, which triggered host restarts and temporarily reduced available capacity. This resulted in service disruption across multiple sites. **Impact:** Between 23:51 UTC on February 2 and 01:27 AM UTC on February 3, some CLM customers across UAT NA11, and Production NA11, NA21, EU11, and EU21 may have been unable to log in or may have encountered issues such as errors, timeouts, or partial page loads when browsing/opening documents and completing workflows. Customers in EU21 may have additionally experienced elevated latency with admin/branding and related search paths lasting until 05:42 UTC. **Resolution:** Docusign restored affected CLM systems and restarted impacted application services. In EU21, additional triage and configurations were required and have been completed to fully return services to normal operation. Service has now been restored.

Read the full incident report →

Looking to track DocuSign downtime and outages?

Pingoru polls DocuSign's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when DocuSign reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track DocuSign alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring DocuSign for free

5 free monitors · No credit card required