DocuSign Outage History
DocuSign is up right nowPingoru has recorded 136 incidents for DocuSign: 133 in the last 12 months and 36 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 7 | 13 of 720 (2%) |
| May 2026 | 14 | 48 of 744 (6%) |
| June 2026 | 23 | 219 of 720 (30%) |
| July 2026 | 17 | 88 of 744 (12%) |
| August 2026 | 13 | 37 of 744 (5%) |
| September 2026 | 8 | 55 of 720 (8%) |
| October 2026 | 9 | 181 of 563 (32%) |
Incidents, newest first
Minor May 12, 2026 Customers may experience issues accessing PowerForms (Incident 4870) 22m eSignature (AU), eSignature (CA), eSignature (EU), eSignature (JP1) and 4 more
Started May 12, 2026, 07:41 PM UTC· resolved May 12, 2026, 08:03 PM UTC
- investigating May 12, 2026, 07:41 PM UTC
We are currently investigating this issue.
- resolved May 12, 2026, 08:03 PM UTC
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Some customers may have experienced issues accessing PowerForms from 2026-05-12 06:10 PM UTC until 2026-05-12 07:59 PM UTC.
Minor May 12, 2026 Users may experience timeouts when attempting to complete document transactions (Incident 4866) 2h 40m eSignature (EU)
Started May 12, 2026, 06:17 PM UTC· resolved May 12, 2026, 08:58 PM UTC
- investigating May 12, 2026, 06:17 PM UTC
We are currently investigating this issue.
- identified May 12, 2026, 06:43 PM UTC
The issue has been identified and a fix is being implemented.
- identified May 12, 2026, 07:33 PM UTC
We are continuing to work on a fix for this issue.
- monitoring May 12, 2026, 07:51 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring May 12, 2026, 08:51 PM UTC
We are continuing to monitor for any further issues.
- 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. Customers may have experienced errors from 2026-05-12 05:22 PM UTC until 2026-05-12 08:59 PM UTC.
Minor May 12, 2026 Users may experience connection errors when trying to switch to CLM or utilising DocuSign edit (Incident 4862) 5h 43m CLM (DEMO S1), CLM (EU11), CLM (EU21), CLM (NA11) and 9 more
Started May 12, 2026, 01:42 PM UTC· resolved May 12, 2026, 07:26 PM UTC
- 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.
- identified May 12, 2026, 02:23 PM UTC
We are continuing to work on a fix for this issue.
- monitoring May 12, 2026, 02:24 PM UTC
Our engineering teams have deployed a fix and we are now monitoring to validate.
- 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.
- 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.
- resolved May 12, 2026, 07:26 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-12 01:29 PM UTC until 2026-05-12 04:01 PM UTC.
Minor May 12, 2026 Users may experience connection errors when trying to switch to CLM (Incident 4861) 1h 58m NA11, NA21, US11, US12 and 9 more
Started May 12, 2026, 08:46 AM UTC· resolved May 12, 2026, 10:44 AM UTC
- 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.
- investigating May 12, 2026, 09:45 AM UTC
Additional teams have been engaged to triage this issue.
- 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.
Minor May 11, 2026 Users may encounter errors that will prevent document uploading or envelope creation (Incident 4860) 46m eSignature (NA2), eSignature (NA4)
Started May 11, 2026, 11:14 PM UTC· resolved May 12, 2026, 12:01 AM UTC
- identified May 11, 2026, 11:14 PM UTC
The issue has been identified and a fix is being implemented.
- resolved May 12, 2026, 12:01 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 errors from 2026-05-11 09:21 PM UTC until 2026-05-11 11:14 PM UTC.
Major May 8, 2026 AU Site Outage (Incident 4840) 1h 15m eSignature (AU)
Started May 08, 2026, 02:09 AM UTC· resolved May 08, 2026, 03:24 AM UTC
- investigating May 08, 2026, 02:09 AM UTC
We are currently investigating this issue.
- investigating May 08, 2026, 02:35 AM UTC
We are continuing to investigate this issue.
- monitoring May 08, 2026, 03:03 AM UTC
We have implemented a mitigation and are monitoring the results.
- resolved May 08, 2026, 03:24 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 errors from 2026-05-08 01:45 AM UTC until 03:09 AM UTC
Minor April 28, 2026 Send Latency in EU (Incident 4776) 36m eSignature (EU)
Started Apr 28, 2026, 09:03 AM UTC· resolved Apr 28, 2026, 09:40 AM UTC
- 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.
- identified Apr 28, 2026, 09:24 AM UTC
Engineers have identified a root cause and are working on releasing a fix.
- monitoring Apr 28, 2026, 09:30 AM UTC
A fix has been implemented and engineers are now monitoring telemetry to validate.
- resolved Apr 28, 2026, 09:40 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 latency from 2026-04-28 08:07 AM UTC until 2026-04-28 09:46 AM UTC.
Minor April 23, 2026 Some customers are seeing errors previewing and sending envelopes via Docusign App Launcher (Incident 4752) 26m
Started Apr 23, 2026, 08:14 PM UTC· resolved Apr 23, 2026, 08:41 PM UTC
- investigating Apr 23, 2026, 08:14 PM UTC
We are currently investigating this issue.
- identified Apr 23, 2026, 08:27 PM UTC
The issue has been identified and a fix is being implemented.
- 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.
Minor April 23, 2026 Some users might experience latency when attempting to convert non-PDF documents (Incident 4750) 6h 50m eSignature (AU), eSignature (CA), eSignature (NA1), eSignature (NA2) and 2 more
Started Apr 23, 2026, 04:28 PM UTC· resolved Apr 23, 2026, 11:18 PM UTC
- investigating Apr 23, 2026, 04:28 PM UTC
We are currently investigating this issue.
- identified Apr 23, 2026, 05:07 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Apr 23, 2026, 05:31 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Apr 23, 2026, 07:18 PM UTC
We continue to monitor the environment to ensure stability.
- monitoring Apr 23, 2026, 08:02 PM UTC
We are continuing to monitor for any further issues.
- monitoring Apr 23, 2026, 09:23 PM UTC
We are continuing to monitor for any further issues.
- monitoring Apr 23, 2026, 10:34 PM UTC
We continue to monitor for stability while we investigate possible secondary factors.
- 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
Minor April 23, 2026 Customers may experience intermittent latency and errors in Navigator (Incident 4748) 7h 43m eSignature (NA2), eSignature (NA4)
Started Apr 23, 2026, 03:27 PM UTC· resolved Apr 23, 2026, 11:10 PM UTC
- investigating Apr 23, 2026, 03:27 PM UTC
We are currently investigating the issue.
- investigating Apr 23, 2026, 04:44 PM UTC
We are continuing to investigate this issue.
- investigating Apr 23, 2026, 05:40 PM UTC
More engineering teams have been engaged to triage this error and investigation is continuing.
- investigating Apr 23, 2026, 06:35 PM UTC
We are continuing to investigate this issue.
- investigating Apr 23, 2026, 07:37 PM UTC
We are continuing to investigate this issue.
- identified Apr 23, 2026, 09:21 PM UTC
The issue has been identified and a fix is being implemented.
- 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.
Major April 17, 2026 Login failures and Latency Issues with Sending and Signing Envelopes (Incident 4717) 1h 31m eSignature (CA)
Started Apr 17, 2026, 02:47 PM UTC· resolved Apr 17, 2026, 04:18 PM UTC
- 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.
- 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.
- 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.
- monitoring Apr 17, 2026, 03:57 PM UTC
We are continuing to monitor for any further issues.
- 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
Minor April 11, 2026 Intermittent Errors in UAT (Incident 4682) 55m CLM (UAT NA11)
Started Apr 11, 2026, 03:54 AM UTC· resolved Apr 11, 2026, 04:50 AM UTC
- investigating Apr 11, 2026, 03:54 AM UTC
Customers may experience intermittent errors, jobs not completing, and the inability to login to UAT.
- investigating Apr 11, 2026, 04:19 AM UTC
We are continuing to investigate this issue.
- identified Apr 11, 2026, 04:41 AM UTC
The issue has been identified and a fix is being implemented.
- 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.
Minor April 9, 2026 User Membership Group Update Delays (Incident 4672) 1h 43m eSignature (AU), eSignature (NA1)
Started Apr 09, 2026, 07:40 PM UTC· resolved Apr 09, 2026, 09:23 PM UTC
- 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.
- 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.
- identified Apr 09, 2026, 08:39 PM UTC
We are implementing a change to resolve the AU delay.
- monitoring Apr 09, 2026, 09:01 PM UTC
A fix has been implemented and we are monitoring the results.
- 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.
Minor March 27, 2026 Issues in UAT and DEMO S1 when attempting to complete tasks in task groups (Incident 4591) 10h 51m CLM (DEMO S1), CLM (UAT NA11)
Started Mar 27, 2026, 12:41 PM UTC· resolved Mar 27, 2026, 11:33 PM UTC
- 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.
- investigating Mar 27, 2026, 02:26 PM UTC
More engineering teams have been engaged to triage this error and investigation is continuing.
- 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.
- identified Mar 27, 2026, 03:42 PM UTC
Engineers are continuing to triage and develop a fix to the identified issue.
- identified Mar 27, 2026, 04:21 PM UTC
We are continuing to work on a fix for this issue.
- identified Mar 27, 2026, 05:22 PM UTC
We are continuing to work on a fix for this issue.
- identified Mar 27, 2026, 09:00 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Mar 27, 2026, 10:39 PM UTC
A fix has been implemented and we are monitoring the results.
- 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.
Notice March 18, 2026 Search Indexing Delays (Incident 4539) 8h 8m CLM (EU21)
Started Mar 18, 2026, 12:13 AM UTC· resolved Mar 18, 2026, 08:22 AM UTC
- 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.
- 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. Customers may have experienced issues from 2026-03-17 01:25 AM UTC until 2026-03-19 04:02 AM UTC.
Major March 14, 2026 CLM & Docusign Gen for Salesforce Customers may be having difficulties accessing EU sites (Incident 4517) 3d 21h CLM (EU11), CLM (EU21), CLM (US11), CLM (US12) and 1 more
Started Mar 14, 2026, 02:07 AM UTC· resolved Mar 17, 2026, 11:40 PM UTC
- investigating Mar 14, 2026, 02:07 AM UTC
We are currently investigating this issue.
- investigating Mar 14, 2026, 02:08 AM UTC
We are continuing to investigate this issue.
- investigating Mar 14, 2026, 02:27 AM UTC
We are continuing to investigate this issue.
- identified Mar 14, 2026, 02:42 AM UTC
The issue has been identified and a fix is being implemented.
- identified Mar 14, 2026, 03:11 AM UTC
We are continuing to work on a fix for this issue.
- identified Mar 14, 2026, 06:07 AM UTC
We are continuing to work on a fix for this issue.
- identified Mar 14, 2026, 09:17 AM UTC
We are continuing to work on a fix for this issue.
- identified Mar 14, 2026, 09:19 AM UTC
We are continuing to work on a fix for this issue.
- identified Mar 14, 2026, 02:44 PM UTC
We are continuing to work on a fix for this issue.
- identified Mar 14, 2026, 03:59 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Mar 14, 2026, 04:54 PM UTC
A fix has been implemented for US sites as of approximately 09:00 UTC.
- 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.
- identified Mar 14, 2026, 06:27 PM UTC
We are continuing to remediate impact to EU11 and EU21 customers.
- identified Mar 14, 2026, 08:24 PM UTC
We are continuing to work on a fix for this issue.
- identified Mar 14, 2026, 10:09 PM UTC
We are continuing to work on a fix for this issue.
- identified Mar 14, 2026, 11:11 PM UTC
We are continuing to remediate impact to EU21 customers.
- monitoring Mar 14, 2026, 11:41 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Mar 15, 2026, 04:23 AM UTC
We are continuing to monitor for any further issues.
- identified Mar 15, 2026, 08:30 AM UTC
The issue has been identified and a fix is being implemented.
- identified Mar 15, 2026, 11:40 AM UTC
We are continuing to work on a fix for this issue.
- identified Mar 15, 2026, 05:17 PM UTC
We are continuing to work on a fix for this issue.
- identified Mar 15, 2026, 08:00 PM UTC
The issue has been identified and a fix is being implemented.
- identified Mar 15, 2026, 10:31 PM UTC
We are continuing to work on a fix for this issue.
- 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.
- identified Mar 16, 2026, 12:51 AM UTC
We are continuing to work through failover steps.
- identified Mar 16, 2026, 02:47 AM UTC
We are continuing to work through failover steps.
- identified Mar 16, 2026, 03:31 AM UTC
We have identified an intermittent degradation in our EU11 environment and are working on fixing it.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- identified Mar 16, 2026, 12:49 PM UTC
We are still continuing to work through the failover steps for EU21.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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. Some CLM sites experienced a service disruption impacting some users’ ability to access the site. The impacted time windows are the following: US11: 2026-03-14 1:20 AM UTC until 2026-03-14 9:20 AM UTC US12: 2026-03-14 1:20 AM UTC until 2026-03-14 10:15 AM UTC US13: 2026-03-14 1:20 AM UTC until 2026-03-14 7:35 AM UTC EU11: 2026-03-16 8:05 PM UTC until 2026-03-16 10:45 PM UTC EU21: 2026-03-14 1:20 AM UTC until 2026-03-17 00:15 AM UTC
Minor March 12, 2026 Users may encounter errors while attempting to upload or edit documents. (Incident 4504) 3h 50m CLM (EU11), CLM (EU21), CLM (NA11), CLM (NA21) and 1 more
Started Mar 12, 2026, 06:15 PM UTC· resolved Mar 12, 2026, 10:06 PM UTC
- investigating Mar 12, 2026, 06:15 PM UTC
We are currently investigating this issue.
- identified Mar 12, 2026, 07:23 PM UTC
The issue has been identified and a fix is being implemented.
- 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
- 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
- monitoring Mar 12, 2026, 09:41 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 12, 2026, 10:06 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-03-04 03:04 PM UTC until 2026-03-12 10:06 PM UTC.
Major March 10, 2026 A subset of Insight customers may experience issues accessing the Product (Incident 4480) 8h 11m Insight (NA.C), Insight (NA.W)
Started Mar 10, 2026, 04:12 PM UTC· resolved Mar 11, 2026, 12:24 AM UTC
- investigating Mar 10, 2026, 04:12 PM UTC
We are currently investigating this issue.
- investigating Mar 10, 2026, 04:58 PM UTC
We are continuing to investigate this issue.
- investigating Mar 10, 2026, 05:28 PM UTC
We are continuing to investigate this issue.
- investigating Mar 10, 2026, 06:11 PM UTC
Incident is actively being investigated.
- identified Mar 10, 2026, 06:49 PM UTC
The issue has been identified and a fix is being implemented.
- identified Mar 10, 2026, 08:15 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Mar 10, 2026, 09:04 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Mar 10, 2026, 10:02 PM UTC
We are continuing to monitor for any further issues.
- monitoring Mar 10, 2026, 11:21 PM UTC
We are continuing to monitor for any further issues.
- 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. Customers may have experienced issues from 2026-03-10 11:00 AM UTC until 2026-03-11 00:23 AM UTC.
Minor March 6, 2026 Users may experience delays or failures when attempting to upload documents via the MuleSoft API (incident 4455) 1h 19m CLM (EU11), CLM (EU21), CLM (NA11), CLM (NA21)
Started Mar 06, 2026, 05:37 PM UTC· resolved Mar 06, 2026, 06:57 PM UTC
- identified Mar 06, 2026, 05:37 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Mar 06, 2026, 06:49 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 06, 2026, 06:57 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 (for UAT) from 2026-02-20 06:20 PM UTC until 2026-03-06 06:29 PM UTC and (for NA11, NA21, EU11, and EU21) from 2026-03-06 01:26 AM UTC until 2026-03-06 06:42 PM UTC.
Minor March 4, 2026 eSign Prod: Customers using Authorize.net to Include a One-Time Payment Request may experience issues completing envelopes (Incident 4445) 1d 2h eSignature (NA1), eSignature (NA2), eSignature (NA3), eSignature (NA4)
Started Mar 04, 2026, 06:45 PM UTC· resolved Mar 05, 2026, 08:50 PM UTC
- investigating Mar 04, 2026, 06:45 PM UTC
We are currently investigating this issue.
- investigating Mar 04, 2026, 07:26 PM UTC
We are continuing to investigate this issue.
- investigating Mar 04, 2026, 11:22 PM UTC
We are continuing to investigate this issue.
- 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.
- resolved Mar 05, 2026, 08:50 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-04 06:23 PM UTC until 2026-03-05 12:51 PM UTC.
Minor February 24, 2026 Customers may experience latency when sending and signing (Incident 4392) 1h 54m eSignature (DEMO)
Started Feb 24, 2026, 10:04 AM UTC· resolved Feb 24, 2026, 11:59 AM UTC
- investigating Feb 24, 2026, 10:04 AM UTC
We are currently investigating the issue.
- 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. Customers may have experienced issues from 2026-02-24 09:25 AM UTC until 2026-02-24 11:33 AM UTC.
Minor February 17, 2026 A Subset of Customers May Experience Intermittent Latency When Sending or Receiving (Incident-4356) 53m eSignature (NA1), eSignature (NA3)
Started Feb 17, 2026, 02:57 PM UTC· resolved Feb 17, 2026, 03:51 PM UTC
- 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.
- 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. Customers may have experienced issues from 2026-02-17 01:56 PM UTC until 2026-02-17 02:46 PM UTC.
Minor February 16, 2026 Users may experience slowness and failures during content uploads and downloads (Incident 4352) 52m CLM (EU21)
Started Feb 16, 2026, 09:26 PM UTC· resolved Feb 16, 2026, 10:19 PM UTC
- investigating Feb 16, 2026, 09:26 PM UTC
We are currently investigating this issue.
- identified Feb 16, 2026, 09:50 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Feb 16, 2026, 10:19 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-02-16 07:52 PM UTC until 2026-02-16 10:31 PM UTC.
Minor February 15, 2026 CLM Prod NA11 Customers are experiencing issues accessing their accounts and performing actions (Incident 4348) 1h 5m CLM (NA11)
Started Feb 15, 2026, 08:50 PM UTC· resolved Feb 15, 2026, 09:56 PM UTC
- investigating Feb 15, 2026, 08:50 PM UTC
We are currently investigating this issue.
- identified Feb 15, 2026, 09:45 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Feb 15, 2026, 09:56 PM UTC
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. 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.
Minor February 15, 2026 Customers may observe degradation in Demo/UAT for Navigator, Prepare, Webforms, and IAM ingestion (Incident 4346) 3h 15m eSignature (DEMO), Rooms (DEMO)
Started Feb 15, 2026, 02:10 PM UTC· resolved Feb 15, 2026, 05:26 PM UTC
- 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
- investigating Feb 15, 2026, 04:18 PM UTC
We are continuing to investigate this issue with Microsoft.
- identified Feb 15, 2026, 05:02 PM UTC
The issue has been identified and a fix is being implemented.
- identified Feb 15, 2026, 05:13 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Feb 15, 2026, 05:13 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 15, 2026, 05:26 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-02-15 09:03 AM UTC until 2026-02-15 04:59 PM UTC.