Docusign Status

Resolved: The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

For any organization reports that were stuck during this incident if it was a scheduled report the user could re-create one and if it was an export now they could re-run it.

Customers may have experienced errors from 2026-06-03 05:00 AM UTC until 2026-06-04 10:50 AM UTC.

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

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

Resolved: 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.

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

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

Investigating: We are currently investigating this issue.

Resolved: The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

For any organization reports that were stuck during this incident if it was a scheduled report the user could re-create one and if it was an export now they could re-run it.

Customers may have experienced errors from 2026-06-03 05:00 AM UTC until 2026-06-04 10:50 AM UTC.

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

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

Resolved: 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.

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

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

Investigating: We are currently investigating this issue.

Resolved: The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

For any organization reports that were stuck during this incident if it was a scheduled report the user could re-create one and if it was an export now they could re-run it.

Customers may have experienced errors from 2026-06-03 05:00 AM UTC until 2026-06-04 10:50 AM UTC.

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

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

Resolved: 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.

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

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

Investigating: We are currently investigating this issue.

Resolved: The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

For any organization reports that were stuck during this incident if it was a scheduled report the user could re-create one and if it was an export now they could re-run it.

Customers may have experienced errors from 2026-06-03 05:00 AM UTC until 2026-06-04 10:50 AM UTC.

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

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

Resolved: The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

For any organization reports that were stuck during this incident if it was a scheduled report the user could re-create one and if it was an export now they could re-run it.

Customers may have experienced errors from 2026-06-03 05:00 AM UTC until 2026-06-04 10:50 AM UTC.

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

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

Resolved: 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.

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

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

Investigating: We are currently investigating this issue.

Resolved: The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

For any organization reports that were stuck during this incident if it was a scheduled report the user could re-create one and if it was an export now they could re-run it.

Customers may have experienced errors from 2026-06-03 05:00 AM UTC until 2026-06-04 10:50 AM UTC.

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

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

Resolved: 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.

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

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

Investigating: We are currently investigating this issue.

Resolved: The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

For any organization reports that were stuck during this incident if it was a scheduled report the user could re-create one and if it was an export now they could re-run it.

Customers may have experienced errors from 2026-06-03 05:00 AM UTC until 2026-06-04 10:50 AM UTC.

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

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

Resolved: 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.

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

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

Investigating: We are currently investigating this issue.

Resolved: The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

For any organization reports that were stuck during this incident if it was a scheduled report the user could re-create one and if it was an export now they could re-run it.

Customers may have experienced errors from 2026-06-03 05:00 AM UTC until 2026-06-04 10:50 AM UTC.

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

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

Resolved: 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.

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

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

Investigating: We are currently investigating this issue.

Resolved: The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.

For any organization reports that were stuck during this incident if it was a scheduled report the user could re-create one and if it was an export now they could re-run it.

Customers may have experienced errors from 2026-06-03 05:00 AM UTC until 2026-06-04 10:50 AM UTC.

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

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

Resolved: 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

Resolved: 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.

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

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

Investigating: We are currently investigating this issue.

Resolved: 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.

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

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

Investigating: We are currently investigating this issue.

Resolved: 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.

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

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

Investigating: We are currently investigating this issue.

Resolved: 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.

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

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

Investigating: We are currently investigating this issue.

Resolved: 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.

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

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

Investigating: We are currently investigating this issue.

Resolved: 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.

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

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

Investigating: We are currently investigating this issue.

Resolved: 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.

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

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

Investigating: We are currently investigating this issue.