Skip to content

Outage tracker / Docusign

Is Docusign down?

I'm having a problem

Vendor reports no incidentWhat Docusign reports

Docusign reports no incident on its status page.

As of the last successful poll, 2026-11-05 15:20 UTC.

Docusign's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 3 minutes ago

Our checks of Docusign pass from all 10 regions we check.

As of Nov 5, 2026, 3:19 PM UTC, RealUptime's checks of Docusign passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 3:19 PM UTC
US-East1134 msChecks passing
US-West832 msChecks passing
Europe795 msChecks passing
Asia-Pacific1509 msChecks passing
US-Central207 msChecks passing
Canada421 msChecks passing
UK755 msChecks passing
Southeast Asia1565 msChecks passing
Australia2714 msChecks passing
South America2413 msChecks passing
their status pagetheir claim, not our reading

Docusign reports: All systems operational (“All Systems Operational”)

from Docusign's own status page, checked Sep 2, 2026, 3:11 AM UTC
Docusign's own status page shows no incident, and our checks of Docusign pass right now.

Docusign's own component breakdown, as they publish it (our last read of their page failed, so this is the previous reading)

  • AUOperational
  • EU.COperational
  • EU11Operational
  • HeadquartersOperational
  • North CentralOperational
  • PRODOperational
  • PRODOperational
  • CAOperational
  • Customer SupportOperational
  • DEMOOperational
  • DEMOOperational
  • Docusign.com HostingOperational
  • EU.NOperational
  • EU21Operational
  • East USOperational
  • EUOperational
  • EU.WOperational
  • East US 2Operational
  • Learning PortalOperational
  • NA11Operational
  • SalesforceOperational
  • AWS ec2-us-west-2Operational
  • FedRAMPOperational
  • NA.COperational
  • NA21Operational
  • Akamai Global Traffic ManagementOperational
  • JP1Operational
  • NA.EOperational
  • S1.USOperational
  • NA.NEOperational
  • NA1Operational
  • NotaryOperational
  • S2.USOperational
  • Spreedly Core Transactional APIOperational
  • NA.WOperational
  • NA2Operational
  • S1.EUOperational
  • DEMOOperational
  • NA3Operational
  • S1.AUOperational
  • NA4Operational
  • US11Operational
  • US12Operational
  • USFEDOperational
  • DEMOOperational
  • US13Operational
  • UAT NA11Operational
  • DEMO S1Operational

These are Docusign's components, named and scored by Docusign. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Docusign's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Docusign response time, by region

US-East
1.5sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 567ms2026-10-08 UTC: p95 556ms2026-10-09 UTC: p95 599ms2026-10-10 UTC: p95 548ms2026-10-11 UTC: p95 520ms2026-10-12 UTC: p95 535ms2026-10-13 UTC: p95 609ms2026-10-14 UTC: p95 490ms2026-10-15 UTC: p95 636ms2026-10-16 UTC: p95 817ms2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.6s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 903ms2026-10-23 UTC: p95 613ms2026-10-24 UTC: p95 504ms2026-10-25 UTC: p95 468ms2026-10-26 UTC: p95 1.4s2026-10-27 UTC: p95 705ms2026-10-28 UTC: p95 939ms2026-10-29 UTC: p95 983ms2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.5s
Oct 7Oct 21Nov 5
US-West
1.9sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 721ms2026-10-08 UTC: p95 661ms2026-10-09 UTC: p95 688ms2026-10-10 UTC: p95 650ms2026-10-11 UTC: p95 730ms2026-10-12 UTC: p95 653ms2026-10-13 UTC: p95 727ms2026-10-14 UTC: p95 700ms2026-10-15 UTC: p95 697ms2026-10-16 UTC: p95 673ms2026-10-17 UTC: p95 621ms2026-10-18 UTC: p95 598ms2026-10-19 UTC: p95 602ms2026-10-20 UTC: p95 669ms2026-10-21 UTC: p95 588ms2026-10-22 UTC: p95 656ms2026-10-23 UTC: p95 737ms2026-10-24 UTC: p95 607ms2026-10-25 UTC: p95 728ms2026-10-26 UTC: p95 567ms2026-10-27 UTC: p95 768ms2026-10-28 UTC: p95 775ms2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 1.7s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 880ms2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 2.5s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
Europe
986msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 827ms2026-10-08 UTC: p95 778ms2026-10-09 UTC: p95 810ms2026-10-10 UTC: p95 726ms2026-10-11 UTC: p95 747ms2026-10-12 UTC: p95 738ms2026-10-13 UTC: p95 959ms2026-10-14 UTC: p95 918ms2026-10-15 UTC: p95 979ms2026-10-16 UTC: p95 773ms2026-10-17 UTC: p95 954ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 733ms2026-10-22 UTC: p95 742ms2026-10-23 UTC: p95 706ms2026-10-24 UTC: p95 715ms2026-10-25 UTC: p95 730ms2026-10-26 UTC: p95 722ms2026-10-27 UTC: p95 790ms2026-10-28 UTC: p95 864ms2026-10-29 UTC: p95 914ms2026-10-30 UTC: p95 921ms2026-10-31 UTC: p95 982ms2026-11-01 UTC: p95 718ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 986ms
Oct 7Oct 21Nov 5
Asia-Pacific
3.2sp95 · latest
10s5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 2.0s2026-10-08 UTC: p95 2.1s2026-10-09 UTC: p95 2.0s2026-10-10 UTC: p95 2.0s2026-10-11 UTC: p95 2.0s2026-10-12 UTC: p95 2.0s2026-10-13 UTC: p95 2.1s2026-10-14 UTC: p95 2.1s2026-10-15 UTC: p95 2.2s2026-10-16 UTC: p95 2.1s2026-10-17 UTC: p95 2.2s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 2.1s2026-10-21 UTC: p95 2.6s2026-10-22 UTC: p95 2.7s2026-10-23 UTC: p95 2.7s2026-10-24 UTC: p95 3.0s2026-10-25 UTC: p95 2.9s2026-10-26 UTC: p95 3.2s2026-10-27 UTC: p95 5.1s2026-10-28 UTC: p95 3.2s2026-10-29 UTC: p95 3.6s2026-10-30 UTC: p95 3.4s2026-10-31 UTC: p95 3.4s2026-11-01 UTC: p95 1.8s2026-11-02 UTC: p95 3.0s2026-11-03 UTC: p95 2.8s2026-11-04 UTC: p95 3.7s2026-11-05 UTC: p95 3.2s
Oct 7Oct 21Nov 5
US-Central
275msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 815ms2026-10-08 UTC: p95 683ms2026-10-09 UTC: p95 704ms2026-10-10 UTC: p95 686ms2026-10-11 UTC: p95 673ms2026-10-12 UTC: p95 724ms2026-10-13 UTC: p95 785ms2026-10-14 UTC: p95 726ms2026-10-15 UTC: p95 853ms2026-10-16 UTC: p95 661ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 314ms2026-10-23 UTC: p95 761ms2026-10-24 UTC: p95 290ms2026-10-25 UTC: p95 279ms2026-10-26 UTC: p95 264ms2026-10-27 UTC: p95 769ms2026-10-28 UTC: p95 510ms2026-10-29 UTC: p95 810ms2026-10-30 UTC: p95 482ms2026-10-31 UTC: p95 468ms2026-11-01 UTC: p95 265ms2026-11-02 UTC: p95 982ms2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 967ms2026-11-05 UTC: p95 275ms
Oct 7Oct 21Nov 5
Canada
907msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 885ms2026-10-08 UTC: p95 649ms2026-10-09 UTC: p95 638ms2026-10-10 UTC: p95 780ms2026-10-11 UTC: p95 673ms2026-10-12 UTC: p95 745ms2026-10-13 UTC: p95 645ms2026-10-14 UTC: p95 740ms2026-10-15 UTC: p95 781ms2026-10-16 UTC: p95 756ms2026-10-17 UTC: p95 547ms2026-10-18 UTC: p95 457ms2026-10-19 UTC: p95 531ms2026-10-20 UTC: p95 511ms2026-10-21 UTC: p95 893ms2026-10-22 UTC: p95 960ms2026-10-23 UTC: p95 945ms2026-10-24 UTC: p95 900ms2026-10-25 UTC: p95 898ms2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 984ms2026-10-28 UTC: p95 1.3s2026-10-29 UTC: p95 1.8s2026-10-30 UTC: p95 982ms2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 946ms2026-11-02 UTC: p95 839ms2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 907ms
Oct 7Oct 21Nov 5
UK
950msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 801ms2026-10-08 UTC: p95 920ms2026-10-09 UTC: p95 933ms2026-10-10 UTC: p95 948ms2026-10-11 UTC: p95 929ms2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 782ms2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 831ms2026-10-16 UTC: p95 752ms2026-10-17 UTC: p95 694ms2026-10-18 UTC: p95 740ms2026-10-19 UTC: p95 755ms2026-10-20 UTC: p95 764ms2026-10-21 UTC: p95 679ms2026-10-22 UTC: p95 677ms2026-10-23 UTC: p95 697ms2026-10-24 UTC: p95 700ms2026-10-25 UTC: p95 758ms2026-10-26 UTC: p95 690ms2026-10-27 UTC: p95 658ms2026-10-28 UTC: p95 755ms2026-10-29 UTC: p95 795ms2026-10-30 UTC: p95 679ms2026-10-31 UTC: p95 684ms2026-11-01 UTC: p95 886ms2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 732ms2026-11-04 UTC: p95 922ms2026-11-05 UTC: p95 950ms
Oct 7Oct 21Nov 5
Southeast Asia
2.5sp95 · latest
10s5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.9s2026-10-08 UTC: p95 2.1s2026-10-09 UTC: p95 2.2s2026-10-10 UTC: p95 1.9s2026-10-11 UTC: p95 2.1s2026-10-12 UTC: p95 1.9s2026-10-13 UTC: p95 2.1s2026-10-14 UTC: p95 2.4s2026-10-15 UTC: p95 1.7s2026-10-16 UTC: p95 1.9s2026-10-17 UTC: p95 2.4s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 3.0s2026-10-22 UTC: p95 3.2s2026-10-23 UTC: p95 5.3s2026-10-24 UTC: p95 5.8s2026-10-25 UTC: p95 2.9s2026-10-26 UTC: p95 2.9s2026-10-27 UTC: p95 2.6s2026-10-28 UTC: p95 2.7s2026-10-29 UTC: p95 2.8s2026-10-30 UTC: p95 3.0s2026-10-31 UTC: p95 3.2s2026-11-01 UTC: p95 3.0s2026-11-02 UTC: p95 2.2s2026-11-03 UTC: p95 2.3s2026-11-04 UTC: p95 2.5s2026-11-05 UTC: p95 2.5s
Oct 7Oct 21Nov 5
Australia
3.0sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.7s2026-10-08 UTC: p95 2.4s2026-10-09 UTC: p95 1.9s2026-10-10 UTC: p95 2.2s2026-10-11 UTC: p95 1.9s2026-10-12 UTC: p95 1.9s2026-10-13 UTC: p95 2.3s2026-10-14 UTC: p95 2.2s2026-10-15 UTC: p95 2.0s2026-10-16 UTC: p95 2.1s2026-10-17 UTC: p95 3.0s2026-10-18 UTC: p95 2.9s2026-10-19 UTC: p95 3.3s2026-10-20 UTC: p95 3.1s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 2.2s2026-10-23 UTC: p95 2.3s2026-10-24 UTC: p95 2.0s2026-10-25 UTC: p95 1.9s2026-10-26 UTC: p95 2.0s2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 1.9s2026-10-29 UTC: p95 1.9s2026-10-30 UTC: p95 3.7s2026-10-31 UTC: p95 3.8s2026-11-01 UTC: p95 3.5s2026-11-02 UTC: p95 2.4s2026-11-03 UTC: p95 3.0s2026-11-04 UTC: p95 3.3s2026-11-05 UTC: p95 3.0s
Oct 7Oct 21Nov 5
South America
3.3sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 2.4s2026-10-08 UTC: p95 1.8s2026-10-09 UTC: p95 1.6s2026-10-10 UTC: p95 1.7s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.7s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 1.7s2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 2.1s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 6.7s2026-10-24 UTC: p95 3.0s2026-10-25 UTC: p95 2.9s2026-10-26 UTC: p95 3.1s2026-10-27 UTC: p95 2.9s2026-10-28 UTC: p95 3.2s2026-10-29 UTC: p95 3.4s2026-10-30 UTC: p95 2.8s2026-10-31 UTC: p95 2.8s2026-11-01 UTC: p95 2.5s2026-11-02 UTC: p95 2.8s2026-11-03 UTC: p95 3.4s2026-11-04 UTC: p95 3.6s2026-11-05 UTC: p95 3.3s
Oct 7Oct 21Nov 5

Check your own site while you wait on Docusign

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Docusign. It cannot diagnose Docusign's own systems.

What we measured, function by function

Docusign answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the auth row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • AuthprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Docusign reports an incident on its status page, and again when it reports it resolved.

Get an email when Docusign reports an incident

Email me when Docusign reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Docusign's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1134msstatus code: 200checked: Nov 5, 2026, 2:56 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Docusign normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 832msstatus code: 200checked: Nov 5, 2026, 3:19 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Docusign normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 207msstatus code: 200checked: Nov 5, 2026, 2:25 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Docusign normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 421msstatus code: 200checked: Nov 5, 2026, 2:23 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Docusign normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 2413msstatus code: 200checked: Nov 5, 2026, 2:27 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Docusign normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 795msstatus code: 200checked: Nov 5, 2026, 2:47 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Docusign normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 755msstatus code: 200checked: Nov 5, 2026, 2:22 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Docusign normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1509msstatus code: 200checked: Nov 5, 2026, 3:08 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Docusign normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1565msstatus code: 200checked: Nov 5, 2026, 2:36 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Docusign normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 2714msstatus code: 200checked: Nov 5, 2026, 2:40 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Docusign normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Docusign, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Docusign yet, which is not evidence that nothing is wrong.

Recent probe events

Some users may not be receiving login verification code and password reset emails (Incident 6112), 28h 24mdeclared on their status page2026-10-31
Signing and login unavailable for Docusign France customers (Incident 5945), 1mdeclared on their status page2026-10-21
Errors for templates, reports, envelope preparation and other features (Incident 6034), 2h 27mdeclared on their status page2026-10-21
Insight Customers Impacted by OCR Processing Issue (Incident 6027), 3h 32mdeclared on their status page2026-10-20
Customers may have experienced intermittent latency and disruption using eSign services (Incident 6014), 1mdeclared on their status page2026-10-19
Errors for templates, reports, envelope preparation and other features (Incident 5994), 1mdeclared on their status page2026-10-16
Errors for templates, reports, envelope preparation and other features (Incident 5932), 7h 11mdeclared on their status page2026-10-08
Failures to grant users access to CLM in account admin (Incident 5922), 3h 53mdeclared on their status page2026-10-07

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Docusign since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Docusign covering any window you pick, with our check readings and Docusign's own claim at the time, side by side.

Full check history for Docusign: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Docusign uptime by RealUptime's checksLive, from this page's own readings.
[![Docusign uptime by RealUptime's checks](https://realuptime.io/outages/docusign/badge.svg?days=30)](https://realuptime.io/outages/docusign)
<a href="https://realuptime.io/outages/docusign"><img src="https://realuptime.io/outages/docusign/badge.svg?days=30" alt="Docusign uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Docusign down?", https://realuptime.io/outages/docusign. The readings change with every check, so give the date you read them.

What we check

primaryfunctional: auth surface
https://account.docusign.com/.well-known/openid-configuration
secondary
https://health.docusign.com/status

What our check can and cannot see

A pass means the configuration document the service publishes, such as an API or sign-in description, loaded. That document is usually static or cached, so it does not show that the endpoints it describes are answering.

Host checked: account.docusign.com

RealUptime is not affiliated with Docusign; the name identifies what we checked, and nothing here speaks for Docusign's own team. We send a single web request to Docusign from 10 regions on our own schedule and time the response. We do not see inside Docusign's systems, do not use an account or real transaction, and are not the same signal Docusign's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Docusign is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.