DocuSign Outage History
Daily provider-status observations and published incident history for DocuSign.
DocuSign is operational. Verified . Official provider source.
Looking for an update now? Check the current status, or follow DocuSign for future changes.
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
| Month | Issue-free days | Days Tracked | Days with issues |
|---|---|---|---|
| September 2026 | 83.3% | 24 | 4 |
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 78 Days)
Incident History
Users may experience performance latency when utilizing document conversion (Incident 5085)
View incident details and source
Notice published:
Provider resolved: . The notice publication date does not establish the outage start.
Email notifications sent from custom domains were delayed (Incident 5106)
View incident details and source
Notice published:
Provider resolved: . The notice publication date does not establish the outage start.
Notification failures when utilising Outlook (Incident 5087)
View incident details and source
Notice published:
Provider resolved: . The notice publication date does not establish the outage start.
Document Upload and Generation Errors (Incident 5073)
View incident details and source
Notice published:
Provider resolved: . The notice publication date does not establish the outage start.
CLM: Resolved Authentication/Access Issues in EU11 (Incident 5040)
View incident details and source
Notice published:
Provider resolved: . The notice publication date does not establish the outage start.
Customers Unable to Purchase Plans (Incident 5034)
View incident details and source
Notice published:
Provider resolved: . The notice publication date does not establish the outage start.
Reports May Remain in "Exporting" Status (Incident 5020)
View incident details and source
Notice published:
Provider resolved: . The notice publication date does not establish the outage start.
Customers dependent on deprecated TLS ciphers will experience interruption (Incident-5003)
View incident details and source
Notice published:
Provider resolved: . The notice publication date does not establish the outage start.
Issues utilising +86 country code for sending envelopes and phone authentication (Incident 4968)
View incident details and source
Notice published:
Provider resolved: . The notice publication date does not establish the outage start.
Customers may experience timeouts related to core AI features which include document summarization and extractions. (incident 4961)
View incident details and source
Notice published:
Provider resolved: . The notice publication date does not establish the outage start.
Legacy Incident Archive
69 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.