SourceDay Outage History

SourceDay is up right now

SourceDay had 3 outages in the last 2 years totaling 7h 19m of downtime — averaging 0.1 incidents per month.

There were 3 SourceDay outages since July 24, 2025 totaling 7h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.sourceday.com

Minor August 4, 2026

SourceDay Email Notification Delay

Detected by Pingoru
Aug 04, 2026, 04:31 PM UTC
Resolved
Aug 04, 2026, 11:51 PM UTC
Duration
7h 19m
Affected: app.sourceday.com
Timeline · 4 updates
  1. identified Aug 04, 2026, 04:31 PM UTC

    SourceDay is aware that email services are currently delayed. Our team has identified the cause and are working to resolve the issue; delayed emails will be sent when functionality is restored.

  2. identified Aug 04, 2026, 06:39 PM UTC

    We are continuing to work on a fix for this issue. In the meantime, emails are delayed, but are continuing to be sent.

  3. monitoring Aug 04, 2026, 08:48 PM UTC

    SourceDay is continuing to monitor the delays in emails. We are starting to see decreases in wait time for emails to be sent, and we will follow up again until the delays have ceased.

  4. resolved Aug 04, 2026, 11:51 PM UTC

    Email delivery is now proceeding as expected, and we are no longer seeing any significant delays. We will continue to monitor for further service disruptions

Read the full incident report →

Notice April 2, 2026

Unexpected outage during application update

Detected by Pingoru
Apr 02, 2026, 09:07 PM UTC
Resolved
Apr 30, 2025, 06:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 02, 2026, 09:07 PM UTC

    An unexpected outage occurred during a routine update to our application. The update caused several database resources to be locked, preventing access to our application. Access was restored once the update completed. No data was lost during the upgrade, and downtime was limited to 5 minutes. We apologize for the inconvenience.

Read the full incident report →

Notice July 24, 2025

Degraded performance due to heavy resource usage

Detected by Pingoru
Jul 24, 2025, 02:30 PM UTC
Resolved
Jul 24, 2025, 02:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 02, 2026, 09:15 PM UTC

    Our application experienced a temporary degradation in performance for approximately 15 minutes. This was traced to an application dependency that was updated on July 22nd, which had a memory leak causing increased system resource usage. Since that time, a patch had been created for dependency, which we applied, correcting the issue.

Read the full incident report →