← Back to Docusign's check readings
We started checking Docusign on August 20, 2026, which is 66 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Docusign reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Docusign's own status page declared. Below it, any public chatter we saw about Docusign and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Docusign's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, auth (primary)
Unverified user reportsNo reports about Docusign in the last 24 hours, which is not evidence that nothing is wrong.
Docusign's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Docusign's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Docusign next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Their declared record
Docusign's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Signing and login unavailable for Docusign France customers (Incident 5945)Partial outage
Oct 21, 2026, 5:51 PM UTC to Oct 21, 2026, 5:51 PM UTC (0 min)resolved
their latest update (Oct 21, 2026, 5:51 PM UTC): The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Errors for templates, reports, envelope preparation and other features (Incident 6034)Minor incident
Oct 21, 2026, 2:31 AM UTC to Oct 21, 2026, 4:59 AM UTC (2h 27m)resolved
their latest update (Oct 21, 2026, 4:59 AM UTC): The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Customers may have experienced intermittent errors or unexpected delays when preparing envelopes, using templates, running reports, or access…
Insight Customers Impacted by OCR Processing Issue (Incident 6027)Minor incident
Oct 20, 2026, 3:38 PM UTC to Oct 20, 2026, 7:10 PM UTC (3h 32m)resolved
their latest update (Oct 20, 2026, 7:10 PM UTC): The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Some customers may have experienced delays or temporary disruptions when uploading documents and running optical character recognition (OCR) …
Customers may have experienced intermittent latency and disruption using eSign services (Incident 6014)Minor incident
Oct 19, 2026, 11:23 PM UTC to Oct 19, 2026, 11:23 PM UTC (0 min)resolved
their latest update (Oct 19, 2026, 11:23 PM UTC): Between 09:26 PM and 10:11 PM UTC, some customers may have experienced intermittent latency and disruption with eSign services. The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation from 2026-10-1…
Errors for templates, reports, envelope preparation and other features (Incident 5994)Minor incident
Oct 16, 2026, 7:13 AM UTC to Oct 16, 2026, 7:13 AM UTC (0 min)resolved
their latest update (Oct 16, 2026, 7:13 AM UTC): The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Customers may have seen errors when using and managing templates, reports, envelope preparation and other features from 2026-10-16 06:08 AM …
Errors for templates, reports, envelope preparation and other features (Incident 5932)Minor incident
Oct 8, 2026, 9:28 AM UTC to Oct 8, 2026, 4:39 PM UTC (7h 11m)resolved
their latest update (Oct 8, 2026, 4:39 PM UTC): The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Some customers may have experienced errors with templates, reports, envelope preparation and other features from 2026-10-08 08:47 AM UTC unti…
Failures to grant users access to CLM in account admin (Incident 5922)Minor incident
Oct 7, 2026, 12:18 PM UTC to Oct 7, 2026, 4:12 PM UTC (3h 53m)resolved
their latest update (Oct 7, 2026, 4:12 PM UTC): The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
CLM workflow update salesforce step latency (Incident 5893)All systems operational
Oct 2, 2026, 3:40 PM UTC to Oct 4, 2026, 6:16 PM UTC (2d 2h)resolved
their latest update (Oct 4, 2026, 6:16 PM UTC): The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Customers may have experienced errors from 2026-10-02 2:42:00 PM UTC until 2026-10-02 6:47:00 PM UTC.
Customers may experience intermittent disruption logging in and using services (Incident 5888)Minor incident
Oct 2, 2026, 2:19 PM UTC to Oct 2, 2026, 4:13 PM UTC (1h 55m)resolved
their latest update (Oct 2, 2026, 4:13 PM UTC): The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation.
Customers unable to access custom scripts following recent update (Incident 5878)All systems operational
Sep 30, 2026, 8:02 PM UTC to Oct 7, 2026, 11:19 PM UTC (7d 3h)resolved
their latest update (Oct 7, 2026, 11:19 PM UTC): The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. A small subset of customer may have been unable to use custom scripts from 2026-09-30 09:30 AM UTC until 2026-10-07 11:18 PM UTC.
Showing the 10 most recent of 171 incidents Docusign has declared in the history we hold.
These entries are Docusign's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Docusign's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.