- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Make. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2025-11-11 18:52 UTC and 2025-11-11 17:40 UTC may need a replay.Subscribe to Make's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=make works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Make 1
- resolved
Between 6:40pm - 6:54pm CET we experienced an infrastructure issue that affected scenario executions in the us1.make.com zone as follows: - Scenarios scheduled to run in the affected time interval were delayed by up to 18 minutes. - Scenarios that are triggered by a webhook were not executed. - Webhooks sent to the affected zone during the aforementioned time interval may not have been received. Most source systems that sends data to Make implement a retry mechanism and webhooks will be redelivered to Make. In addition to the above, login on the zone was also affected. The zone is now stable, and we are continuing to monitor the situation
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-738b87494f
Is Make still down?
No, this incident was resolved 2025-11-11 17:40 UTC. For Make's live state, see https://down.guide/make.
How long did it last?
0m, from 2025-11-11 18:52 UTC to 2025-11-11 17:40 UTC, by the times Make posted.
What caused it?
Make hasn't published a root cause. If it does, it shows here.
Where does this come from?
Make's official status page, https://status.make.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.