SignWell Outage History

SignWell is up right now

SignWell had 5 outages in the last 2 years totaling 20h 2m of downtime — averaging 0.2 incidents per month.

There were 5 SignWell outages since October 20, 2025 totaling 20h 2m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.signwell.com

Major July 23, 2026

Investigating — Digital signature certification delayed

Detected by Pingoru
Jul 23, 2026, 04:11 PM UTC
Resolved
Jul 23, 2026, 06:54 PM UTC
Duration
2h 42m
Affected: Docsketch Service
Timeline · 5 updates
  1. investigating Jul 23, 2026, 04:11 PM UTC

    A third-party provider involved in applying digital certificates to completed documents is currently experiencing an outage. Documents can still be sent, signed, and completed normally. We're currently investigating.

  2. identified Jul 23, 2026, 04:39 PM UTC

    We've confirmed the issue is caused by an upstream certificate problem with a third-party digital certification provider. We are applying changes to restore document completion. Documents are completing as usual. Embedded digital certificate remains delayed. All other functionality is unaffected.

  3. identified Jul 23, 2026, 05:11 PM UTC

    The upstream issue with the third-party provider has been resolved. Documents continue to be processed and digital signing is operating normally again. We're monitoring to confirm stable operation and verifying that no documents with embedded digital certificates are delayed.

  4. monitoring Jul 23, 2026, 06:11 PM UTC

    We continue to monitor operations and are verifying that no previously completed documents with embedded digital certificates are delayed.

  5. resolved Jul 23, 2026, 06:54 PM UTC

    This incident is resolved. The upstream issue with the third-party provider has been fixed, and digital signing is operating normally. All previously delayed documents have been signed with their embedded digital certificates. Thank you for your patience.

Read the full incident report →

Minor June 4, 2026

Email Sending Delays

Detected by Pingoru
Jun 04, 2026, 10:44 PM UTC
Resolved
Jun 05, 2026, 12:54 AM UTC
Duration
2h 10m
Affected: Docsketch Service
Timeline · 6 updates
  1. investigating Jun 04, 2026, 10:44 PM UTC

    We're currently experiencing email sending delays due to an issue with our third-party email provider. Emails may take longer than usual to arrive. We're actively monitoring the situation and will post an update as soon as we have more information.

  2. identified Jun 04, 2026, 11:03 PM UTC

    Update: We've identified an upstream issue with our email provider. We're working on rerouting notifications through an alternate path to restore normal delivery.

  3. monitoring Jun 04, 2026, 11:28 PM UTC

    Update: We've successfully switched email routing and notifications are being delivered we're continuing to monitor delivery to confirm everything remains stable.

  4. monitoring Jun 04, 2026, 11:46 PM UTC

    Update: Our primary email provider is recovering. Documents that weren't re-sent are now being processed and will be delivered shortly. We're continuing to monitor until all queued emails have gone out.

  5. monitoring Jun 05, 2026, 12:40 AM UTC

    Resolved: The backlog of queued messages has been fully sent and email delivery has returned to normal from our main email provider. System performance is back to its expected state. We'll continue monitoring for a while longer to confirm everything remains optimal. Thank you for your patience while we worked through this issue.

  6. resolved Jun 05, 2026, 12:54 AM UTC

    Resolved: This incident has been fully resolved. Our email provider has confirmed recovery on their end, the backlog of queued messages has been delivered, and email sending has returned to normal performance. We've verified delivery is stable after an extended monitoring period. Thank you for your patience while we worked through this issue.

Read the full incident report →

Minor March 30, 2026

Document Generation API

Detected by Pingoru
Mar 30, 2026, 07:41 PM UTC
Resolved
Mar 30, 2026, 08:09 PM UTC
Duration
28m
Affected: Docsketch Service
Timeline · 4 updates
  1. investigating Mar 30, 2026, 07:41 PM UTC

    We are currently investigating reports of errors affecting document generation for custom customers via the API. Some API requests may be failing or returning unexpected errors during this time.

  2. investigating Mar 30, 2026, 08:03 PM UTC

    We are continuing to investigate this issue.

  3. identified Mar 30, 2026, 08:07 PM UTC

    We have identified the cause of this issue. A WAF (Web Application Firewall) rule was incorrectly blocking API requests for some customers.

  4. resolved Mar 30, 2026, 08:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 18, 2025

Network interruptions

Detected by Pingoru
Nov 18, 2025, 12:14 PM UTC
Resolved
Nov 18, 2025, 06:33 PM UTC
Duration
6h 18m
Affected: Docsketch Service
Timeline · 7 updates
  1. investigating Nov 18, 2025, 12:14 PM UTC

    We're experiencing a service interruption due to a widespread third-party outage. Our team is monitoring the situation and will update you as it's resolved.

  2. identified Nov 18, 2025, 12:21 PM UTC

    Our services may be slow or unavailable due to an ongoing outage with one of our third-party providers. We'll update this page as the situation improves.

  3. identified Nov 18, 2025, 01:18 PM UTC

    Our services continue to be slow or unavailable due to an ongoing outage with one of our third-party providers. We're actively working on a fix.

  4. monitoring Nov 18, 2025, 02:46 PM UTC

    Our third-party provider is seeing traffic recovery and we're monitoring our services closely. We'll continue to provide updates as the situation develops.

  5. monitoring Nov 18, 2025, 03:03 PM UTC

    Our third-party provider has resolved their issues and traffic is returning to normal. Our systems are handling the load as expected. We continue to monitor closely.

  6. monitoring Nov 18, 2025, 04:26 PM UTC

    Our third-party provider has fixed their issues and traffic is returning to normal. We're continuing to accept traffic and process signatures as usual. We're monitoring both our systems and the provider's updates closely.

  7. resolved Nov 18, 2025, 06:33 PM UTC

    Our third-party provider has resolved their network issues and our services are operating normally. We're accepting traffic and processing signatures as usual. This incident is now closed.

Read the full incident report →

Notice October 20, 2025

Service Notice: AWS Outage Affecting Integrations and Support

Detected by Pingoru
Oct 20, 2025, 04:38 PM UTC
Resolved
Oct 21, 2025, 01:01 AM UTC
Duration
8h 23m
Affected: Docsketch Service
Timeline · 4 updates
  1. identified Oct 20, 2025, 04:38 PM UTC

    We're currently affected by a major outage from AWS. Core SignWell signing features remain operational, but you may experience slower performance with some integrations and third-party connections. Our Helpdesk provider is also affected, so support response times may be delayed. We'll post updates as services recover.

  2. monitoring Oct 20, 2025, 05:15 PM UTC

    Our Helpdesk provider is recovering and we've begun processing pending tickets and requests. Core SignWell signing features remain operational. Some integrations may still experience slower performance as AWS services continue to stabilize.

  3. monitoring Oct 20, 2025, 08:22 PM UTC

    Support tickets are being processed normally. We're monitoring AWS recovery to ensure third-party integrations are fully restored, as they may rely on the affected region. SignWell's core services have remained available throughout the incident. We're continuing to monitor and confirm all upstream services are fully recovered with no risk of the outage impacting other AWS regions.

  4. resolved Oct 21, 2025, 01:01 AM UTC

    AWS has given the all-clear on their status page and affected third-party services have recovered. Support tickets are being processed normally and all SignWell services remained available throughout the incident. This incident is now closed.

Read the full incident report →