Skip to content

Outage tracker / Docusign

Is Docusign down?

I'm having a problem

Operationalchecked 16 minutes ago

We reached Docusign from all 10 regions we check.

As of Oct 5, 2026, 7:59 PM UTC, Docusign answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured Docusign (since Aug 20, 2026).

our independent probeslive · checked Oct 5, 2026, 7:59 PM UTC
US-East430 msOperational
US-West452 msOperational
Europe177 msOperational
Asia-Pacific1742 msOperational
US-Central410 msOperational
Canada426 msOperational
UK340 msOperational
Southeast Asia1549 msOperational
Australia1378 msOperational
South America782 msOperational
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
Our probes and Docusign's own status page agree: both show Docusign as reachable 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
584msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 504ms2026-09-07 UTC: p95 520ms2026-09-08 UTC: p95 539ms2026-09-09 UTC: p95 528ms2026-09-10 UTC: p95 511ms2026-09-11 UTC: p95 491ms2026-09-12 UTC: p95 504ms2026-09-13 UTC: p95 544ms2026-09-14 UTC: p95 490ms2026-09-15 UTC: p95 469ms2026-09-16 UTC: p95 523ms2026-09-17 UTC: p95 656ms2026-09-18 UTC: p95 624ms2026-09-19 UTC: p95 525ms2026-09-20 UTC: p95 581ms2026-09-21 UTC: p95 612ms2026-09-22 UTC: p95 593ms2026-09-23 UTC: p95 604ms2026-09-24 UTC: p95 618ms2026-09-25 UTC: p95 671ms2026-09-26 UTC: p95 607ms2026-09-27 UTC: p95 558ms2026-09-28 UTC: p95 565ms2026-09-29 UTC: p95 629ms2026-09-30 UTC: p95 576ms2026-10-01 UTC: p95 637ms2026-10-02 UTC: p95 558ms2026-10-03 UTC: p95 636ms2026-10-04 UTC: p95 595ms2026-10-05 UTC: p95 584ms
Sep 6Sep 20Oct 5
US-West
610msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 748ms2026-09-07 UTC: p95 813ms2026-09-08 UTC: p95 820ms2026-09-09 UTC: p95 558ms2026-09-10 UTC: p95 523ms2026-09-11 UTC: p95 562ms2026-09-12 UTC: p95 535ms2026-09-13 UTC: p95 483ms2026-09-14 UTC: p95 610ms2026-09-15 UTC: p95 771ms2026-09-16 UTC: p95 644ms2026-09-17 UTC: p95 793ms2026-09-18 UTC: p95 705ms2026-09-19 UTC: p95 612ms2026-09-20 UTC: p95 596ms2026-09-21 UTC: p95 798ms2026-09-22 UTC: p95 727ms2026-09-23 UTC: p95 725ms2026-09-24 UTC: p95 757ms2026-09-25 UTC: p95 791ms2026-09-26 UTC: p95 707ms2026-09-27 UTC: p95 627ms2026-09-28 UTC: p95 673ms2026-09-29 UTC: p95 656ms2026-09-30 UTC: p95 634ms2026-10-01 UTC: p95 643ms2026-10-02 UTC: p95 703ms2026-10-03 UTC: p95 714ms2026-10-04 UTC: p95 579ms2026-10-05 UTC: p95 610ms
Sep 6Sep 20Oct 5
Europe
821msp95 · 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-09-06 UTC: p95 777ms2026-09-07 UTC: p95 770ms2026-09-08 UTC: p95 786ms2026-09-09 UTC: p95 775ms2026-09-10 UTC: p95 836ms2026-09-11 UTC: p95 808ms2026-09-12 UTC: p95 803ms2026-09-13 UTC: p95 732ms2026-09-14 UTC: p95 814ms2026-09-15 UTC: p95 836ms2026-09-16 UTC: p95 774ms2026-09-17 UTC: p95 828ms2026-09-18 UTC: p95 789ms2026-09-19 UTC: p95 781ms2026-09-20 UTC: p95 796ms2026-09-21 UTC: p95 803ms2026-09-22 UTC: p95 814ms2026-09-23 UTC: p95 737ms2026-09-24 UTC: p95 818ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 890ms2026-09-27 UTC: p95 838ms2026-09-28 UTC: p95 842ms2026-09-29 UTC: p95 836ms2026-09-30 UTC: p95 743ms2026-10-01 UTC: p95 741ms2026-10-02 UTC: p95 721ms2026-10-03 UTC: p95 1.0s2026-10-04 UTC: p95 787ms2026-10-05 UTC: p95 821ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.9sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.8s2026-09-07 UTC: p95 2.0s2026-09-08 UTC: p95 2.1s2026-09-09 UTC: p95 2s2026-09-10 UTC: p95 2.1s2026-09-11 UTC: p95 2.0s2026-09-12 UTC: p95 2.2s2026-09-13 UTC: p95 2.0s2026-09-14 UTC: p95 1.9s2026-09-15 UTC: p95 1.9s2026-09-16 UTC: p95 1.9s2026-09-17 UTC: p95 1.9s2026-09-18 UTC: p95 1.9s2026-09-19 UTC: p95 1.9s2026-09-20 UTC: p95 1.9s2026-09-21 UTC: p95 1.9s2026-09-22 UTC: p95 2.1s2026-09-23 UTC: p95 2.0s2026-09-24 UTC: p95 2.0s2026-09-25 UTC: p95 1.9s2026-09-26 UTC: p95 1.8s2026-09-27 UTC: p95 1.8s2026-09-28 UTC: p95 1.8s2026-09-29 UTC: p95 1.8s2026-09-30 UTC: p95 2.0s2026-10-01 UTC: p95 1.7s2026-10-02 UTC: p95 1.8s2026-10-03 UTC: p95 2.0s2026-10-04 UTC: p95 1.9s2026-10-05 UTC: p95 1.9s
Sep 6Sep 20Oct 5
US-Central
750msp95 · 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-09-06 UTC: p95 784ms2026-09-07 UTC: p95 713ms2026-09-08 UTC: p95 803ms2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 733ms2026-09-11 UTC: p95 911ms2026-09-12 UTC: p95 799ms2026-09-13 UTC: p95 897ms2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 936ms2026-09-16 UTC: p95 538ms2026-09-17 UTC: p95 588ms2026-09-18 UTC: p95 772ms2026-09-19 UTC: p95 553ms2026-09-20 UTC: p95 748ms2026-09-21 UTC: p95 576ms2026-09-22 UTC: p95 753ms2026-09-23 UTC: p95 970ms2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 721ms2026-09-26 UTC: p95 728ms2026-09-27 UTC: p95 746ms2026-09-28 UTC: p95 763ms2026-09-29 UTC: p95 843ms2026-09-30 UTC: p95 742ms2026-10-01 UTC: p95 669ms2026-10-02 UTC: p95 850ms2026-10-03 UTC: p95 674ms2026-10-04 UTC: p95 730ms2026-10-05 UTC: p95 750ms
Sep 6Sep 20Oct 5
Canada
811msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 659ms2026-09-07 UTC: p95 617ms2026-09-08 UTC: p95 609ms2026-09-09 UTC: p95 713ms2026-09-10 UTC: p95 623ms2026-09-11 UTC: p95 677ms2026-09-12 UTC: p95 613ms2026-09-13 UTC: p95 761ms2026-09-14 UTC: p95 640ms2026-09-15 UTC: p95 675ms2026-09-16 UTC: p95 455ms2026-09-17 UTC: p95 870ms2026-09-18 UTC: p95 464ms2026-09-19 UTC: p95 601ms2026-09-20 UTC: p95 545ms2026-09-21 UTC: p95 830ms2026-09-22 UTC: p95 602ms2026-09-23 UTC: p95 575ms2026-09-24 UTC: p95 663ms2026-09-25 UTC: p95 635ms2026-09-26 UTC: p95 711ms2026-09-27 UTC: p95 586ms2026-09-28 UTC: p95 861ms2026-09-29 UTC: p95 727ms2026-09-30 UTC: p95 683ms2026-10-01 UTC: p95 698ms2026-10-02 UTC: p95 958ms2026-10-03 UTC: p95 994ms2026-10-04 UTC: p95 726ms2026-10-05 UTC: p95 811ms
Sep 6Sep 20Oct 5
UK
874msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 644ms2026-09-07 UTC: p95 669ms2026-09-08 UTC: p95 669ms2026-09-09 UTC: p95 628ms2026-09-10 UTC: p95 715ms2026-09-11 UTC: p95 730ms2026-09-12 UTC: p95 690ms2026-09-13 UTC: p95 704ms2026-09-14 UTC: p95 753ms2026-09-15 UTC: p95 721ms2026-09-16 UTC: p95 707ms2026-09-17 UTC: p95 692ms2026-09-18 UTC: p95 700ms2026-09-19 UTC: p95 671ms2026-09-20 UTC: p95 722ms2026-09-21 UTC: p95 812ms2026-09-22 UTC: p95 802ms2026-09-23 UTC: p95 735ms2026-09-24 UTC: p95 742ms2026-09-25 UTC: p95 867ms2026-09-26 UTC: p95 878ms2026-09-27 UTC: p95 957ms2026-09-28 UTC: p95 870ms2026-09-29 UTC: p95 799ms2026-09-30 UTC: p95 720ms2026-10-01 UTC: p95 796ms2026-10-02 UTC: p95 887ms2026-10-03 UTC: p95 818ms2026-10-04 UTC: p95 854ms2026-10-05 UTC: p95 874ms
Sep 6Sep 20Oct 5
Southeast Asia
2.1sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.8s2026-09-07 UTC: p95 1.6s2026-09-08 UTC: p95 1.7s2026-09-09 UTC: p95 1.7s2026-09-10 UTC: p95 1.9s2026-09-11 UTC: p95 2.0s2026-09-12 UTC: p95 1.9s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.6s2026-09-15 UTC: p95 1.5s2026-09-16 UTC: p95 1.8s2026-09-17 UTC: p95 1.9s2026-09-18 UTC: p95 2.3s2026-09-19 UTC: p95 1.8s2026-09-20 UTC: p95 1.9s2026-09-21 UTC: p95 2.4s2026-09-22 UTC: p95 2.0s2026-09-23 UTC: p95 2.3s2026-09-24 UTC: p95 2.5s2026-09-25 UTC: p95 2.4s2026-09-26 UTC: p95 1.9s2026-09-27 UTC: p95 1.9s2026-09-28 UTC: p95 1.7s2026-09-29 UTC: p95 1.8s2026-09-30 UTC: p95 2.1s2026-10-01 UTC: p95 1.9s2026-10-02 UTC: p95 1.9s2026-10-03 UTC: p95 2.0s2026-10-04 UTC: p95 1.9s2026-10-05 UTC: p95 2.1s
Sep 6Sep 20Oct 5
Australia
2.1sp95 · 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-09-06 UTC: p95 2.1s2026-09-07 UTC: p95 2.1s2026-09-08 UTC: p95 2.3s2026-09-09 UTC: p95 2.2s2026-09-10 UTC: p95 2.2s2026-09-11 UTC: p95 2.3s2026-09-12 UTC: p95 2.0s2026-09-13 UTC: p95 2.4s2026-09-14 UTC: p95 1.9s2026-09-15 UTC: p95 2.5s2026-09-16 UTC: p95 2.4s2026-09-17 UTC: p95 2.0s2026-09-18 UTC: p95 2.5s2026-09-19 UTC: p95 1.9s2026-09-20 UTC: p95 2.3s2026-09-21 UTC: p95 2.1s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 2.1s2026-09-24 UTC: p95 1.7s2026-09-25 UTC: p95 2.3s2026-09-26 UTC: p95 2.5s2026-09-27 UTC: p95 2.6s2026-09-28 UTC: p95 2.0s2026-09-29 UTC: p95 2.3s2026-09-30 UTC: p95 2.8s2026-10-01 UTC: p95 2.3s2026-10-02 UTC: p95 2.1s2026-10-03 UTC: p95 2.3s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 2.1s
Sep 6Sep 20Oct 5
South America
1.3sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.4s2026-09-07 UTC: p95 1.6s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 1.7s2026-09-10 UTC: p95 1.5s2026-09-11 UTC: p95 1.7s2026-09-12 UTC: p95 1.6s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.5s2026-09-15 UTC: p95 1.8s2026-09-16 UTC: p95 1.7s2026-09-17 UTC: p95 1.4s2026-09-18 UTC: p95 1.6s2026-09-19 UTC: p95 1.3s2026-09-20 UTC: p95 1.7s2026-09-21 UTC: p95 1.7s2026-09-22 UTC: p95 1.7s2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.7s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.7s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.6s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.7s2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 1.3s
Sep 6Sep 20Oct 5

Is it Docusign, or is it you?

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: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • AuthprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see Docusign go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Docusign, and again when they can reach it again. That is our own measurement from ten regions, not Docusign's status page. No account, no card.

Delivery channel

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

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 we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 430msstatus code: 200checked: Oct 5, 2026, 7:57 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
      Operationallatency: 452msstatus code: 200checked: Oct 5, 2026, 7:48 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
      Operationallatency: 410msstatus code: 200checked: Oct 5, 2026, 7:21 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
      Operationallatency: 426msstatus code: 200checked: Oct 5, 2026, 7:29 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
    Operationallatency: 782msstatus code: 200checked: Oct 5, 2026, 7:57 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 177msstatus code: 200checked: Oct 5, 2026, 7:59 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
      Operationallatency: 340msstatus code: 200checked: Oct 5, 2026, 7:24 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 1742msstatus code: 200checked: Oct 5, 2026, 7:50 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
      Operationallatency: 1549msstatus code: 200checked: Oct 5, 2026, 7:53 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
      Operationallatency: 1378msstatus code: 200checked: Oct 5, 2026, 7:57 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 outages

UI Latency Issues (Incident 5692), 1h 23mdeclared on their status page2026-08-31
Slow performance and delays for Agreement Manager, CLM, and eSign (Incident 5674), 2h 10mdeclared on their status page2026-08-27
New Docusign Status Center: Subscribe by September 1 to Receive Updates, 1mdeclared on their status page2026-08-27
Issues in JP1 with Salesforce Writeback (Incident 5648), 6h 9mdeclared on their status page2026-08-24
Document Upload and Generation Errors (Incident 5595), 40mdeclared on their status page2026-08-12
Degraded Task Processing and Latency across multiple services (Incident 5576), 13h 35mdeclared on their status page2026-08-11
Login Issues in AU region (Incident 5572), 2h 1mdeclared on their status page2026-08-11
Latency and Errors Across NA11 (Incident 5558), 1h 14mdeclared on their status page2026-08-07

measured 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 measurements and Docusign's own claim at the time, side by side.

Full availability history for Docusign: 90-day availability by region, month-by-month uptime, and every incident 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

Put this badge in your README

Docusign uptime measured by RealUptimeLive, from this page's own readings.
[![Docusign uptime measured by RealUptime](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 measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Docusign's SLA implies, from our measurement

At or above your target

We measured none of downtime for Docusign over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Docusign's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: auth surface
https://account.docusign.com/.well-known/openid-configuration
secondary
https://status.docusign.com/
RealUptime is not affiliated with Docusign; the name identifies what we measured, 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 clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.