Documenso Outage History

Documenso is up right now

Documenso had 10 outages in the last 2 years totaling 27401h 13m of downtime — averaging 0.4 incidents per month.

There were 10 Documenso outages since October 20, 2024 totaling 27401h 13m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.documenso.com

Minor June 4, 2026

Temporary Suspension of Email Sending for New Free Plans

Detected by Pingoru
Jun 04, 2026, 01:12 PM UTC
Resolved
Jun 09, 2026, 08:48 AM UTC
Duration
4d 19h
Timeline · 4 updates
  1. investigating Jun 04, 2026, 01:12 PM UTC

    Due to ongoing abuse on the platform, we have temporarily disabled email sending for new free plans. You can still create signing links and share them manually. Existing plans (paid or unpaid) are not affected. We’ll share further updates as the situation evolves.

  2. identified Jun 05, 2026, 12:34 PM UTC

    We are migrating free plan email sending to a different domain.

  3. monitoring Jun 07, 2026, 09:52 AM UTC

    Free plans sending has been restored. We are monitoring for further issues.

  4. resolved Jun 09, 2026, 08:48 AM UTC

Read the full incident report →

Minor May 16, 2026

We're investigating issues with email sending

Detected by Pingoru
May 16, 2026, 12:06 AM UTC
Resolved
May 16, 2026, 12:20 AM UTC
Duration
14m
Timeline · 2 updates
  1. identified May 16, 2026, 12:06 AM UTC

    We're aware of an issue occurring when sending emails. We're working with our email provider to restore access as soon as possible.

  2. resolved May 16, 2026, 12:20 AM UTC

    Email sending has now been resolved. We will continue to work with our email provider to avoid this happening again in the future.

Read the full incident report →

Minor June 12, 2025

Monitoring Upstream Issues

Detected by Pingoru
Jun 12, 2025, 07:09 PM UTC
Resolved
Jun 13, 2025, 02:58 PM UTC
Duration
19h 48m
Timeline · 2 updates
  1. monitoring Jun 12, 2025, 07:09 PM UTC

    We’re aware of an upstream provider issue (https://status.supabase.com) No user impact. Actively monitoring.

  2. resolved Jun 13, 2025, 02:58 PM UTC

    Our upstream provider (Supabase) is reporting that all services have been restored and are operational.

Read the full incident report →

Minor March 8, 2025

Planned Maintenance

Detected by Pingoru
Mar 08, 2025, 10:16 AM UTC
Resolved
Mar 13, 2025, 04:57 PM UTC
Duration
5d 6h
Timeline · 2 updates
  1. monitoring Mar 08, 2025, 10:16 AM UTC

    We will be performing a hosting provider cutover on Sunday the 9th of March at 5:00AM UTC. We expect there to be no noticeable impact to services but you may encounter a brief second of downtime as we change our DNS records.

  2. resolved Mar 13, 2025, 04:57 PM UTC

    The maintenance was successfully completed.

Read the full incident report →

Minor December 16, 2024

Website Status

Detected by Pingoru
Dec 16, 2024, 05:16 PM UTC
Resolved
Jun 04, 2026, 01:12 PM UTC
Duration
534d 19h
Timeline · 2 updates
  1. monitoring Dec 16, 2024, 05:16 PM UTC

    Since switching to Framer, occasional false positives on downtime have been reported. We’re investigating the cause, but rest assured there are no actual issues with availability.

  2. resolved Jun 04, 2026, 01:12 PM UTC

Read the full incident report →

Minor December 9, 2024

Website False Positive

Detected by Pingoru
Dec 09, 2024, 12:20 PM UTC
Resolved
Dec 09, 2024, 12:20 PM UTC
Duration
—
Timeline · 2 updates
  1. resolved Dec 09, 2024, 12:20 PM UTC

    Since switching to Framer, occasional false positives on downtime have been reported. We’re investigating the cause, but rest assured there are no actual issues with availability.

  2. resolved Jun 04, 2026, 01:12 PM UTC

Read the full incident report →

Minor October 20, 2024

General Stability

Detected by Pingoru
Oct 20, 2024, 04:18 PM UTC
Resolved
Jun 04, 2026, 01:12 PM UTC
Duration
591d 20h
Timeline · 2 updates
  1. monitoring Oct 20, 2024, 04:18 PM UTC

    We observed minor stability issues without user impact.We are monitoring the situation.

  2. resolved Jun 04, 2026, 01:12 PM UTC

Read the full incident report →