Isitreallydown?
// Incident Post-MortemDRN-5DB0552E

Netlify outage on April 13, 2026

Minor severityResolved45 minPaaS
Started · UTC
Apr 13, 01:16 AM
30d ago
Resolved · UTC
Apr 13, 02:01 AM
30d ago
Duration
45 min
End-to-end
Peak confidence
25.00
0 snapshots
// What happened

Apr 13, 01:16 UTCResolved - This incident has been resolved. A fix was deployed for the issue affecting Scheduled Functions auto-triggering, and scheduled invocations have recovered. During the incident, manual executions continued to work, but some scheduled runs did not trigger automatically as expected.Apr 13, 01:04 UTCMonitoring - We implemented a fix for the issue affecting Scheduled Functions auto-triggering and are seeing signs of recovery. Manual executions were unaffected during the incident, and scheduled invocations now appear to be resuming. We are continuing to monitor closelyApr

Deterministic readout · awaiting AI summary pass

// Timeline
  1. Incident detected

    Minor confidence crossed the incident threshold for Scheduled Functions Auto-Triggering Not Executing.

  2. Marked resolved

    The incident was closed after 45 min of observed impact.

// Signals by source0 sources

No per-source signal payloads were preserved in this incident's snapshot window.

// Aggregate evidence

Confidence scoring

25.00

The incident reached 25.00 peak confidence across available stored status snapshots.

User reports

0 / 15m

No elevated user-report volume was preserved in the incident window snapshots.

Status samples

0 affected

The incident row exists, but the bounded snapshot window does not include affected status samples.

Recovery signal

Resolved

Recovery was recorded at Mon, Apr 13, 2026, 02:01 AM UTC.

// User impact

Netlify users likely saw failed connections, degraded availability, or session instability for this PaaS service. The incident reached Minor severity and lasted 45 min. The stored report window does not show a preserved user-report spike.