Loading status…
Docusign status · SaaS · checked (1s ago)
Also searched as DocuSign, DocuSign eSignature.
We could not reach Docusign's status feed, so its current state is unconfirmed.
According to Docusign's official status page, Docusign was reporting “Status API unreachable (Unexpected token '<', "<!DOCTYPE "... is not valid JSON)” when isuptime last checked at . Over the last 30 days, Docusign's feed reported no outage in 100.00% of our checks.
isuptime cannot fix Docusign, and neither can you. These are the things that are actually worth doing until it comes back.
Everything above is read from Docusign's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Docusign in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Docusign handles electronic signature and agreement workflows — sending documents for signature, tracking them and storing the completed envelopes — often embedded into other systems through its API.
The status page separates the web application from the API and from the signing experience recipients see, and it reports per environment and region. The demo environment is separate from production, which is worth checking before assuming an outage — a failing integration test may be pointed at a sandbox that is down while production is fine.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Docusign's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Docusign was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 1s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Docusign's status endpoint.
Every incident Docusign has published in the last 12 months.
Docusign has not published a single incident in the last 12 months. That is a statement about Docusign's posting habits as much as its reliability — a status page only records what its owner decides to record.
An envelope that has not arrived is usually email delivery to the recipient rather than Docusign — check spam and any corporate filtering. Expired envelopes void themselves on a schedule set when they were sent. API integrations failing after months are frequently an expired JWT consent grant or a rotated integration key, both of which return authentication errors that read as an outage.
