Netlify outage: Scheduled Functions Auto-Triggering Not Executing

Affected components

• Netlify Functions

1. resolvedApr 13, 2026, 01:16 UTC

   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.

2. monitoringApr 13, 2026, 01:04 UTC

   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 closely

3. investigatingApr 13, 2026, 00:39 UTC

   Investigating an issue affecting Scheduled Functions auto-triggering. Manual “Run now” executions are succeeding, but some scheduled functions are not automatically invoking at their expected times.Beginning around April 12, 2026 at 1:00 AM UTC and are actively investigating.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Netlify's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Confluent Cloud: Elevated error rates in AWS me-south-1 and me-central-1 regionsMajor · Apr 1, 2026, 19:52 UTC

How often does Netlify have incidents?

Netlify reported 9 incidents in the last 90 days, 4 of them major or critical. A typical incident lasted 31 min. See Netlify's uptime and incident history