DocuSign incident
Errors accessing the sending web application (Incident 5334)
DocuSign experienced a minor incident on July 7, 2026 affecting NA1 and NA2 and 1 more component, lasting 1d 20h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 07, 2026, 08:55 PM UTC
A small subset of customers may see errors accessing the sending web application. We are actively investigating the underlying cause.
- investigating Jul 07, 2026, 09:37 PM UTC
We are continuing to investigate this issue.
- investigating Jul 07, 2026, 10:01 PM UTC
We continue to investigate the issue and additional resources have been engaged.
- investigating Jul 07, 2026, 10:26 PM UTC
We continue to investigate the issue and additional resources have been engaged.
- investigating Jul 07, 2026, 11:54 PM UTC
We continue to investigate and have engaged external vendor resources
- investigating Jul 08, 2026, 12:10 AM UTC
We are continuing to investigate the web cache issue. A small subset of customers may see an error when accessing the send web application page. Completely emptying the browser cache and trying again is a viable fix. Updates will be posted when there is a significant update.
- investigating Jul 08, 2026, 03:39 AM UTC
We continue to investigate with our CDN partner to determine why a very small group of end users are seeing errors. Disabling browser cache completely or completely emptying browser cache and trying again will unblock users. Please contact docusign support if you need assistance. An update will be provided when a significant update is available.
- investigating Jul 08, 2026, 03:50 PM UTC
We continue to investigate with our CDN partner to determine why a very small group of end users are seeing errors. Disabling browser cache completely or completely emptying browser cache and trying again will unblock users. Please contact docusign support if you need assistance. An update will be provided when a significant update is available.
- resolved Jul 09, 2026, 05:22 PM UTC
The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.