Docusign Status

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

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

Identified: We have identified the issue and a fix is being implemented.

Investigating: We are actively investigating this issue.

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Postmortem: RCA for Docusign eSign & CLM Service Disruption on June 29, 2026
Between 2026-06-29 08:18 AM UTC and 2026-06-29 06:05 PM UTC, some eSignature customers may have experienced latency and intermittent errors when sending and signing envelopes.  Some CLM customers may have experienced degraded performance when viewing, saving, or retrieving documents. Impact was initially limited but became more pronounced as transaction volumes increased during North America business hours.
Cause:
A staged network routing change was inadvertently applied, redirecting traffic to a secondary region. As traffic volumes increased, this placed additional demand on services responsible for storage and authorization, resulting in elevated latency and intermittent request failures. Additional investigation was required to identify the routing issue before it could be corrected.
Resolution:
The routing change was corrected, allowing traffic to return to the intended primary region. Service configurations were also adjusted to reduce resource contention and improve service performance.

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

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

Identified: We continue to work to implement a fix for the issue.

Identified: The issue has been identified and we continue our work to implement a fix.

Identified: We have identified the issue and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are actively investigating this issue.

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Postmortem: RCA for Docusign eSign & CLM Service Disruption on June 29, 2026
Between 2026-06-29 08:18 AM UTC and 2026-06-29 06:05 PM UTC, some eSignature customers may have experienced latency and intermittent errors when sending and signing envelopes.  Some CLM customers may have experienced degraded performance when viewing, saving, or retrieving documents. Impact was initially limited but became more pronounced as transaction volumes increased during North America business hours.
Cause:
A staged network routing change was inadvertently applied, redirecting traffic to a secondary region. As traffic volumes increased, this placed additional demand on services responsible for storage and authorization, resulting in elevated latency and intermittent request failures. Additional investigation was required to identify the routing issue before it could be corrected.
Resolution:
The routing change was corrected, allowing traffic to return to the intended primary region. Service configurations were also adjusted to reduce resource contention and improve service performance.

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

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

Identified: We continue to work to implement a fix for the issue.

Identified: The issue has been identified and we continue our work to implement a fix.

Identified: We have identified the issue and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are actively investigating this issue.

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

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

Investigating: We are continuing to investigate this issue.

Investigating: We are actively investigating this issue.

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Postmortem: RCA for Docusign eSign & CLM Service Disruption on June 29, 2026
Between 2026-06-29 08:18 AM UTC and 2026-06-29 06:05 PM UTC, some eSignature customers may have experienced latency and intermittent errors when sending and signing envelopes.  Some CLM customers may have experienced degraded performance when viewing, saving, or retrieving documents. Impact was initially limited but became more pronounced as transaction volumes increased during North America business hours.
Cause:
A staged network routing change was inadvertently applied, redirecting traffic to a secondary region. As traffic volumes increased, this placed additional demand on services responsible for storage and authorization, resulting in elevated latency and intermittent request failures. Additional investigation was required to identify the routing issue before it could be corrected.
Resolution:
The routing change was corrected, allowing traffic to return to the intended primary region. Service configurations were also adjusted to reduce resource contention and improve service performance.

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

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

Identified: We continue to work to implement a fix for the issue.

Identified: The issue has been identified and we continue our work to implement a fix.

Identified: We have identified the issue and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are actively investigating this issue.

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Postmortem: RCA for Docusign eSign & CLM Service Disruption on June 29, 2026
Between 2026-06-29 08:18 AM UTC and 2026-06-29 06:05 PM UTC, some eSignature customers may have experienced latency and intermittent errors when sending and signing envelopes.  Some CLM customers may have experienced degraded performance when viewing, saving, or retrieving documents. Impact was initially limited but became more pronounced as transaction volumes increased during North America business hours.
Cause:
A staged network routing change was inadvertently applied, redirecting traffic to a secondary region. As traffic volumes increased, this placed additional demand on services responsible for storage and authorization, resulting in elevated latency and intermittent request failures. Additional investigation was required to identify the routing issue before it could be corrected.
Resolution:
The routing change was corrected, allowing traffic to return to the intended primary region. Service configurations were also adjusted to reduce resource contention and improve service performance.

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

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

Identified: We continue to work to implement a fix for the issue.

Identified: The issue has been identified and we continue our work to implement a fix.

Identified: We have identified the issue and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are actively investigating this issue.

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

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

Identified: We have identified the issue and a fix is being implemented.

Investigating: We continue to investigate the issue and additional resources have been engaged. We will provide the next update in approximately 24 hours.

Investigating: We continue to investigate the issue and additional resources have been engaged.

Investigating: We continue to investigate the issue and additional resources have been engaged.

Investigating: We are continuing to investigate this issue.

Investigating: We are actively investigating this issue.

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

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

Identified: We have identified the issue and a fix is being implemented.

Investigating: We continue to investigate the issue and additional resources have been engaged. We will provide the next update in approximately 24 hours.

Investigating: We continue to investigate the issue and additional resources have been engaged.

Investigating: We continue to investigate the issue and additional resources have been engaged.

Investigating: We are continuing to investigate this issue.

Investigating: We are actively investigating this issue.

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

Identified: We have identified the issue and a fix is being implemented.

Investigating: We are actively investigating this issue.

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

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

Identified: We have identified the issue and a fix is being implemented.

Investigating: We continue to investigate the issue and additional resources have been engaged. We will provide the next update in approximately 24 hours.

Investigating: We continue to investigate the issue and additional resources have been engaged.

Investigating: We continue to investigate the issue and additional resources have been engaged.

Investigating: We are continuing to investigate this issue.

Investigating: We are actively investigating this issue.

Postmortem: RCA for Docusign eSign & CLM Service Disruption on June 29, 2026
Between 2026-06-29 08:18 AM UTC and 2026-06-29 06:05 PM UTC, some eSignature customers may have experienced latency and intermittent errors when sending and signing envelopes.  Some CLM customers may have experienced degraded performance when viewing, saving, or retrieving documents. Impact was initially limited but became more pronounced as transaction volumes increased during North America business hours.
Cause:
A staged network routing change was inadvertently applied, redirecting traffic to a secondary region. As traffic volumes increased, this placed additional demand on services responsible for storage and authorization, resulting in elevated latency and intermittent request failures. Additional investigation was required to identify the routing issue before it could be corrected.
Resolution:
The routing change was corrected, allowing traffic to return to the intended primary region. Service configurations were also adjusted to reduce resource contention and improve service performance.

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

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

Identified: We continue to work to implement a fix for the issue.

Identified: The issue has been identified and we continue our work to implement a fix.

Identified: We have identified the issue and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are actively investigating this issue.

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

Identified: We have identified the issue and a fix is being implemented.

Investigating: We are actively investigating this issue.

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Postmortem: RCA for Docusign eSign & CLM Service Disruption on June 29, 2026
Between 2026-06-29 08:18 AM UTC and 2026-06-29 06:05 PM UTC, some eSignature customers may have experienced latency and intermittent errors when sending and signing envelopes.  Some CLM customers may have experienced degraded performance when viewing, saving, or retrieving documents. Impact was initially limited but became more pronounced as transaction volumes increased during North America business hours.
Cause:
A staged network routing change was inadvertently applied, redirecting traffic to a secondary region. As traffic volumes increased, this placed additional demand on services responsible for storage and authorization, resulting in elevated latency and intermittent request failures. Additional investigation was required to identify the routing issue before it could be corrected.
Resolution:
The routing change was corrected, allowing traffic to return to the intended primary region. Service configurations were also adjusted to reduce resource contention and improve service performance.

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

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

Identified: We continue to work to implement a fix for the issue.

Identified: The issue has been identified and we continue our work to implement a fix.

Identified: We have identified the issue and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are actively investigating this issue.

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

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

Investigating: We continue to investigate the issue and additional resources have been engaged.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating issues with both report and search on S1 prod. Engineering teams have been engaged and are actively triaging.

Investigating: We are currently investigating issues with both report and search on S1 prod. Engineering teams have been engaged and are actively triaging.

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Postmortem: RCA for Docusign eSign & CLM Service Disruption on June 29, 2026
Between 2026-06-29 08:18 AM UTC and 2026-06-29 06:05 PM UTC, some eSignature customers may have experienced latency and intermittent errors when sending and signing envelopes.  Some CLM customers may have experienced degraded performance when viewing, saving, or retrieving documents. Impact was initially limited but became more pronounced as transaction volumes increased during North America business hours.
Cause:
A staged network routing change was inadvertently applied, redirecting traffic to a secondary region. As traffic volumes increased, this placed additional demand on services responsible for storage and authorization, resulting in elevated latency and intermittent request failures. Additional investigation was required to identify the routing issue before it could be corrected.
Resolution:
The routing change was corrected, allowing traffic to return to the intended primary region. Service configurations were also adjusted to reduce resource contention and improve service performance.

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

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

Identified: We continue to work to implement a fix for the issue.

Identified: The issue has been identified and we continue our work to implement a fix.

Identified: We have identified the issue and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are actively investigating this issue.

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Postmortem: RCA for Docusign eSign & CLM Service Disruption on June 29, 2026
Between 2026-06-29 08:18 AM UTC and 2026-06-29 06:05 PM UTC, some eSignature customers may have experienced latency and intermittent errors when sending and signing envelopes.  Some CLM customers may have experienced degraded performance when viewing, saving, or retrieving documents. Impact was initially limited but became more pronounced as transaction volumes increased during North America business hours.
Cause:
A staged network routing change was inadvertently applied, redirecting traffic to a secondary region. As traffic volumes increased, this placed additional demand on services responsible for storage and authorization, resulting in elevated latency and intermittent request failures. Additional investigation was required to identify the routing issue before it could be corrected.
Resolution:
The routing change was corrected, allowing traffic to return to the intended primary region. Service configurations were also adjusted to reduce resource contention and improve service performance.

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

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

Identified: We continue to work to implement a fix for the issue.

Identified: The issue has been identified and we continue our work to implement a fix.

Identified: We have identified the issue and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are actively investigating this issue.

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US

Resolved: On September 1, this site will be replaced by health.docusign.com/status. To continue getting notifications, you'll need to resubscribe on the new site. View detailed instructions at https://support.docusign.com/s/articles/System-Status-Alerts?language=en_US