lagcheck can I play right now?

Is Docusign down right now?

Checked 3 minutes ago

No — Docusign is working normally
Valorant, Twilio, Cloudflare, Amazon Web Services and 2 more are all reporting problems at the same time. Cloudflare, Amazon Web Services, Elastic Cloud and Replicate are infrastructure a lot of what we watch runs on. We cannot tell from here whether that is the cause — we are reading status pages, not tracing dependencies — but it is worth ruling out before you blame your own line.
If you are having trouble anyway, the problem is more likely to be between you and Docusign than at Docusign itself. Two things worth checking, in order: your connection under load — a line that idles at 20 ms can jump to 300 ms while something uploads, which drops you from sessions and looks exactly like a server fault — and whether the people you play with see the same thing, since a service can be healthy in your region and unwell in theirs. Run a connection check.

The last 48 hours

3 separate problems in the last 48 hours, most recently 10 hours ago. That's unusual for Docusign.

Longer record

94.17%Clear of trouble, 31 days
8Problems seen
36h 38mLongest
10 hoursLast problem
Clear of trouble, each day, last 31 days

This longer record is here so the 48-hour picture above can mean something — without it we could tell you a problem happened, but not whether that is normal for Docusign.

Something was impaired on 5.83% of our checks over that window. That is how often Docusign was reporting a problem somewhere, which is not the same as how often it was unreachable. The longest outage we have on record ran 36h 38m.

Day by day

The last 30 days of Docusign, one row each.

DayClearUpChecksStartedLongest ended
2026-11-11 so far today 99.39% 99.39% 165 1 8 min
2026-11-10 86.36% 100% 286 2 2h 9m
2026-11-09 100% 100% 287 none —
2026-11-08 100% 100% 287 none —
2026-11-07 100% 100% 287 none —
2026-11-06 84.03% 98.61% 288 1 3h 55m
2026-11-05 92.31% 94.41% 286 1 1h 51m
2026-11-04 100% 100% 287 none —
2026-11-03 100% 100% 286 none —
2026-11-02 89.2% 100% 287 none 28h 28m
2026-11-01 0% 100% 287 none —
2026-10-31 92.68% 100% 287 1 —
2026-10-30 100% 100% 287 none —
2026-10-29 100% 100% 287 none —
2026-10-28 100% 100% 287 none —
2026-10-27 100% 100% 287 none —
2026-10-26 100% 100% 287 none —
2026-10-25 100% 100% 287 none —
2026-10-24 100% 100% 287 none —
2026-10-23 100% 100% 287 none —
2026-10-22 100% 100% 286 none —
2026-10-21 89.9% 100% 287 1 2h 29m
2026-10-20 85.37% 100% 287 1 3h 33m
2026-10-19 100% 100% 287 none —
2026-10-18 100% 100% 285 none —
2026-10-17 100% 100% 288 none —
2026-10-16 100% 100% 286 none —
2026-10-15 100% 100% 287 none —
2026-10-14 100% 100% 287 none —
2026-10-13 100% 100% 281 none —

Clear is the share of checks that found nothing wrong at all; Up is the share that found Docusign actually reachable — a vendor reporting one impaired component scores zero on the first and a hundred on the second, and both are true. Started counts outages that began that day and Longest ended the longest that finished on it, so a problem running across midnight is counted once, on the day it began, and measured on the day it stopped.

Rows recorded before 8 August 2026 do not carry a check count — the figure was kept and the denominator was not — so their percentages are shown without one rather than with a number borrowed from somewhere else. Rows before 9 August 2026 have no Up figure either: until then we recorded only whether something was wrong, not whether it was down, and the two are different questions.

Outage history

StartedLastedSeverityWhat happened
2026-11-11 03:47 UTC 8 min down Maintenance for Insight (Seal) customers on November 28, 2026 at 02:00 UTC (Maint 6207)
2026-11-10 09:26 UTC 2h 9m having problems Document Preview Unavailable on NA11 (Incident 6194)
2026-11-10 03:04 UTC 1h 11m having problems CLM queued processing delays (Incident 6191)
2026-11-06 18:25 UTC 3h 55m down Docusign Connect to Salesforce Status Updates in USFED (Incident 6165)
2026-11-05 16:18 UTC 1h 51m down Settings Service Unavailable in US Regions (Incident 6153)
2026-10-31 22:12 UTC 28h 28m having problems Some users may not be receiving login verification code and password reset emails (Incident 6112)
2026-10-21 02:31 UTC 2h 29m having problems Errors for templates, reports, envelope preparation and other features (Incident 6034)
2026-10-20 15:38 UTC 3h 33m having problems Insight Customers Impacted by OCR Processing Issue (Incident 6027)
2026-10-08 09:28 UTC 7h 13m having problems Errors for templates, reports, envelope preparation and other features (Incident 5932)
2026-10-07 12:18 UTC 3h 57m having problems Failures to grant users access to CLM in account admin (Incident 5923)
2026-10-02 14:19 UTC 4h 47m having problems Customers may experience intermittent disruption logging in and using services (Incident 5888)
2026-09-30 20:02 UTC 3h 9m having problems Customers unable to access custom scripts following recent update (Incident 5878)
2026-09-28 18:08 UTC 36h 38m having problems Email Delivery Failures impacting customers (Incident 5861)
2026-09-09 22:06 UTC 1h 39m having problems Users unable to preview documents (Incident 5749)
2026-09-09 01:52 UTC 1h 58m having problems High latency affecting send and sign across production environments (Incident 5741)
2026-09-07 00:18 UTC 1h 33m having problems CLM workflow and expression evaluation degradation and failures (Incident 5734)
2026-08-31 16:06 UTC 1h 23m having problems UI Latency Issues (Incident 5692)
2026-08-27 23:39 UTC 2h 11m having problems Slow performance and delays (Incident 5674)
2026-08-12 23:21 UTC 44 min having problems Document Upload and Generation Errors (Incident 5595)

When the status page says green and you still can't play

Status pages report the vendor's view of their own service, and they lag real outages — often by many minutes, sometimes by hours, because a human usually has to confirm before anything is posted. They also can't see the two things most likely to be wrong at your end.

The first is your own connection under load. A line that idles at 20 ms can jump to 300 ms the moment something starts uploading, which drops you from sessions and looks exactly like a server fault. Your plan speed says nothing about this; it's called bufferbloat and almost nobody measures it.

The second is where everyone else in your group is. A service can be healthy in your region and unwell in theirs, and if one person is hosting, their problem is everyone's problem.

Playing with people elsewhere

Docusign being fine where you are does not mean it is fine for everyone in your group. The live dashboard resolves status against each person's own region, and will tell you which of your friends is in an affected area — plus who has the connection to host, which is usually a different question from who has the fastest plan.

Other services we watch

Worth a look when more than one thing feels broken at once: if several are genuinely down together, the fault is usually something they share rather than anything at your end. We are not claiming these particular services fail together — the live dashboard says when they actually do.