PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if DocuSign is down?

PulseWatch evaluates user reports and replay-approved automated evidence for DocuSign. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported DocuSign issues today?

As of Oct 12, 2026 15:00 UTC, 0 users had reported issues with DocuSign in the previous 24 hours.

How can I report a DocuSign outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Productivity

Is DocuSign down right now?

UnknownOfficial status last polled Sep 7, 2026 15:24 UTCdocusign.com Official status page

DocuSign e-signature service

Are you on the DocuSign team and see something inaccurate? Report it to us. We respond within one business day.

Is DocuSign down right now?

Unknown. DocuSign does not have a conclusive current status. A single-runtime HTTP reachability check succeeded; no fresh official status confirms whole-service health. No current vendor status signal: vendor status was last polled on 2026-09-07, more than 7 days ago. The most recent attempt on 2026-10-12 could not be acquired.

Status as of Oct 12, 2026 15:00 UTC

Unknown

DocuSign: status unknown

As of Oct 12, 2026 15:00 UTC

No product check is currently qualified to corroborate an incident for this service. Overall service status has not been established.

Reports 24h

Last incident

Aug 31, 2026 17:57 UTC

Trend

0/15m

Monitoring

Coverage gap

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for DocuSign.

Incident days

No recorded incident

0 min

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for DocuSign. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

0 incidents

Busiest day

0 min

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

DocuSign outage on April 29 28-minute disruption

Apr 29, 02:44 AM → Apr 29, 03:13 AM · 28 minutes · high

On April 29, 2026, DocuSign experienced a service disruption. This incident was detected through user reports indicating issues with website accessibility. The service was fully restored at 03:13 UTC.

Peak reports

in 15 min

Total reports

during the incident

Duration

28 minutes

tracked by PulseWatch

Impact

Users reported issues accessing the DocuSign website during the incident. These reports primarily indicated a 'Website down' issue type. While no specific regions were predominantly impacted, the disruption was observed by multiple users. The incident was initially identified through these user reports, which were subsequently grouped to form a single incident.

Top reported issues

Website down2

Incident timeline

Apr 29, 02:44 AM
PulseWatch detected elevated report volume (high severity)
Apr 29, 03:00 AM
Peak of 0 reports in 15 minutes (baseline 1.3)
Apr 29, 03:13 AM
Report volume returned to baseline — incident resolved

Official updates

Apr 29, 03:13 AM
Website down clustered from 2 sources across 3 signals. Suppressed 2 redundant alerts.

Reliability

Not measured

30-day uptime

n/a

90-day uptime

n/a

Not calculated: DocuSign is unknown, so there is no incident history to measure and no uptime figure is shown.

Other productivity services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.