DocuSign incident

Users may experience connection errors when trying to switch to CLM or utilising DocuSign edit (Incident 4862)

Minor Resolved View vendor source →

DocuSign experienced a minor incident on May 12, 2026 affecting NA11 and NA21 and 1 more component, lasting 5h 44m. The incident has been resolved; the full update timeline is below.

Started
May 12, 2026, 01:42 PM UTC
Resolved
May 12, 2026, 07:26 PM UTC
Duration
5h 44m
Detected by Pingoru
May 12, 2026, 01:42 PM UTC

Affected components

NA11NA21US11US12EU11EU21US13UAT NA11DEMO S1S1.US

Update timeline

  1. identified May 12, 2026, 01:42 PM UTC

    We are currently investigating an issue where a subset of customers utilising a particular firewall may experience issues when attempting to switch to CLM. To restore access, please contact your IT department or security team and request that the following URL be unblocked/allowed: https://login.springcm.com Once this URL has been added to your allowlist, you should be able to log in without any further issues. Further investigation with our engineering teams is underway to fully resolve this issue.

  2. identified May 12, 2026, 02:23 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring May 12, 2026, 02:24 PM UTC

    Our engineering teams have deployed a fix and we are now monitoring to validate.

  4. identified May 12, 2026, 03:20 PM UTC

    Additional Engineering teams have been engaged to triage this issue, the current workaround is still functional: To restore access, please contact your IT department or security team and request that the following URL be unblocked/allowed: https://login.springcm.com Once this URL has been added to your allowlist, you should be able to log in without any further issues. Further investigation with our engineering teams is underway to fully resolve this issue.

  5. monitoring May 12, 2026, 03:55 PM UTC

    A fix has now been implemented and we are seeing improvements, we will continue monitoring telemetry to ensure the fix is final.

  6. resolved May 12, 2026, 07:26 PM UTC

    This incident has been resolved.