[ROOT CAUSE ANALYSIS]

[RESOLVED June 23, 2021, 09:45 CDT] The DocuSign CLM Technology team has declared this incident resolved.  The last detected latency related to this incident occurred on 6/17/2021.  The DocuSign Technology team will provide an official Root Cause Analysis of this incident within 48 hours.  Thank you for your patience and we apologize for the inconvenience.

[UPDATED June 22, 2021, 09:45 CDT] The DocuSign CLM Technology team has seen some improvement in the performance issue but cannot declare resolved until our 3rd party vendor has given clearance.  The team will continue to monitor the incident through the day until resolution is declared.

[UPDATED June 21, 2021, 10:00 CDT] The DocuSign CLM Technology team has seen some improvement in the performance issue but cannot declare resolved until our 3rd party vendor has given clearance.  The team will continue to monitor the incident through the day until resolution is declared.

[UPDATED June 18, 2021, 17:20 CDT] The DocuSign CLM Technology team has seen some improvement in the performance issue but cannot declare resolved until our 3rd party vendor has given clearance.  The team will continue to monitor the incident through the weekend until resolution is declared.

[UPDATED June 18, 2021, 08:10 CDT] The DocuSign CLM Technology team has seen some improvement in the performance issue but cannot declare resolved until our 3rd party vendor has given clearance.  The team will continue to monitor the incident through the day until resolution is declared.

[UPDATED June 17, 2021, 17:00 CDT] The DocuSign CLM Technology team has seen some improvement in the performance issue but cannot declare resolved until our 3rd party vendor has given clearance.  The team will continue to monitor the incident through the evening until resolution is declared.

[UPDATED June 17, 2021, 08:30 CDT] The DocuSign CLM Technology team has seen some improvement in the performance issue but cannot declare resolved until our 3rd party vendor has given clearance.  The team will continue to monitor the incident through the day until resolution is declared.

[UPDATED June 16, 2021, 16:30 CDT ] The DocuSign CLM Technology team has seen some improvement in the performance issue but cannot declare resolved until our 3rd party vendor has given clearance.  The team will continue to monitor the incident through the evening until resolution is declared.

[UPDATED June 16, 2021 13:20 CDT] The DocuSign CLM Technology team has seen some improvement in the performance issue but cannot declare resolved until our 3rd party vendor has given clearance.  The team will continue to monitor the incident through the day until resolution is declared.

[UPDATED June 16, 2021 06:40 CDT] The DocuSign CLM Technology team has seen some improvement in the performance issue but cannot declare resolved until our 3rd party vendor has given clearance.  The team will continue to monitor the incident through the morning until resolution is declared.

Please check the status of trust.springcm.com for updates regarding this issue.

[UPDATED June 15, 2021 20:15 CDT] The DocuSign CLM Technology team has seen an improvement in the performance issue but cannot declare resolved until our 3rd party vendor has given clearance.  The team will continue to monitor the incident through the night until resolution is declared.

Please check the status of trust.springcm.com for updates regarding this issue.

[UPDATED June 15, 2021 16:30 CDT] The DocuSign CLM Technology team has isolated the performance issue and is working with our 3rd party vendor on which the incident it occurring.  During this time customers with accounts on our NA11 Production and UAT instances may experience intermittent latency issues as well as the potential for encountering page errors while navigating the site.  

Please check the status of trust.springcm.com frequently for updates regarding this issue.

[POSTED Jun 15, 2021 15:03 CDT] The DocuSign CLM Technology team is working to isolate a performance degradation issue, on the application tier of the NA11 instance.

[RESOLVED Mar 5 10:05 CT] The DocuSign/SpringCM Technology team has resolved the performance degradation issue on the NA21 instance.  The issue began at 3/4/2021 8:32:24 PM UTC and ended at 3/5/2021 3:53:58 PM UTC.  A Root Cause Analysis will be posted here as soon as it's available.  

We apologize for any inconvenience this incident has had on customers.

[UPDATE Mar 5, 2021 09:30 CT] The DocuSign/SpringCM Technology team has isolated the performance degradation issue on the NA21 instance and is currently validating potential resolution paths.

[ROOT CAUSE ANALYSIS]

[UPDATE: Jan 11, 2021 15:10 CT] The DocuSign / SpringCM Technology teams continue to investigate the Root Cause Analysis of this issue.  Regrettably, we are unable to offer a full RCA at this time.  We anticipate being able to offer a full RCA within the next 48 hours.

[RESOLVED: Jan 7, 2021 20:02 CT] The DocuSign / SpringCM Technology teams have resolved the performance degradation issue on the Production and UAT NA11 instances.  

The team will begin identifying the cause of the issue and will post a Root Cause Analysis on this trust post within 48 hours.  We apologize for the impact this issue has caused customers on the NA11 Production and UAT instances. 

Please contact Technical Support if you have any questions or concerns regarding impacted workflows.

[UPDATED: Jan 7, 2021 18:00 CT] The DocuSign/SpringCM Technology teams have isolated the performance degradation issue on the Production and UAT NA11 instances.  They are currently working to resolve the issue.

Please check the status of trust.springcm.com frequently for updates regarding this issue.

[POSTED: Jan 7, 2021 16:45 CT] The DocuSign/SpringCM Technology teams are working to fix a performance degradation issue on the application tier on the NA11 (Production and UAT) instances. During this time, customers may experience latency in certain workflow steps, some resulting in timeouts.

[RESOLVED May 16, 2020 05:47 CDT] -The DocuSign CLM/SpringCM Technology team has resolved the service availability issue on the EU11/EU21 instances. The problem began at 00:00 CDT and was resolved at 05:47 CDT.

The intermittent slowness in UAT has been reduced but is not currently completely resolved.  Please check the status of trust.springcm.com frequently for updates regarding this issue.

[RESOLVED Apr 19, 2020 15:57 CDT - The SpringCM Technology team has resolved the performance degradation issue on the UAT instance.  The issue began on Apr 17 at 08:42 CDT and resolved on Apr 19 at 15:05 CDT.

We will provide a Root Cause Analysis here within a few days.  We apologize for any inconvenience. 

[UPDATED Apr 19, 2020 15:00 CDT] - The SpringCM Technology team continues to work on resolving the performance degradation issue on the application on the UAT instance. We apologize for the inconvenience and will continue to update Trust with more information as we get closer to resolution.

[UPDATED Apr 17, 2020 16:50 CDT] - The SpringCM Technology team continues to work on resolving the performance degradation issue on the application on the UAT instance.  We anticipate improvement throughout the weekend as work continues.  We apologize for the inconvenience and will continue to update Trust with more information as we get closer to resolution.

Please check the status of trust.springcm.com frequently for updates regarding this issue.

[POSTED Apr 17, 2020 09:03] The SpringCM Technology team is working to resolve a performance degradation issue on the application on the UAT instance.

[RESOLVED] Jan 16, 2020 16:47 CST] The SpringCM Technology team resolved the performance degradation issue on the backend of the NA11 instance.  The issue lasted from approximately 1/15/20 at 02:04 to 14:00 CST.  We apologize for the inconvenience.

[POSTED Jan 15, 2020 08:24 CST] The SpringCM Technology team is working to resolve a performance degradation issue on the backend of the NA11 instance.