Is Make Down? Scenarios Not Running
Fixed in latest version Web Updated October 21, 2026
Quick answer
If many scenarios stop at once, check status.make.com. Recent incidents (Sept 2025, Dec 2025, March, July, Aug and Oct 2026) stopped executions, left webhooks unprocessed and auto-disabled scenarios that had to be re-enabled.
Most likely fix: Check Make's status page.
Symptoms
Several scenarios fail or don't run at the same time; editor won't load or save; webhooks don't trigger.
Why it happens
- Make platform or region incident (EU1, EU2, US1, US2)
- Upstream provider outage (e.g. Cloudflare in December 2025)
- Faulty Make deployment disabling scenarios
How to fix it
Try these in order — the most common fix is first.
1. Check Make's status page
- Open status.make.com
- Find your region (shown in your Make URL, e.g. eu2.make.com)
- Subscribe to updates
2. Re-enable disabled scenarios
- After the incident, open the Scenarios list
- Filter by inactive scenarios
- Switch affected scenarios back ON
3. Replay missed webhook data
- Check the webhook's Logs for requests received during the outage
- Ask the sending app to resend events, or rerun with incomplete executions
This guide also covers
- is make down
- make.com down
- make scenarios not running
- make outage
Still not working?
If Make keeps failing, you're not alone. See every Make problem users report or the alternatives people switch to.
Other Make errors
- Make Webhook Not Triggering Scenario
- Make Webhook 'Queue Is Full' or 410 Gone Error
- Make Using Too Many Credits (Operations)
- Make Scenario Turned Off Automatically
- Make 'Invalid Refresh Token, Please Reauthorize the Connection' Error
- Make RateLimitError (429 Too Many Requests)
- Make ExecutionInterruptedError (Scenario Timeout)
- Make Google Sheets Watch New Rows Not Working
- Make BundleValidationError: Missing Value of Required Parameter
- Make DataSizeLimitExceededError