- Level
- confirmed
- Worst impact
- Partial outage
- Components
- us1.make.com, us1.make.com, us1.make.com
- Down Index
- 31of 100
What to do
Check whether you use Make us1.make.com, us1.make.com, us1.make.com. 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 1h 54m it lasted.
Anything that failed between 2025-11-12 16:24 UTC and 2025-11-12 18:18 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 4
- investigating
We are currently experiencing an issue on the zone us1.make.com Login/Access to the website and scenario execution might be impacted. We are investigating the issue and will provide more updates within one hour.
provider
- investigating
We are continuing to investigate this issue.
provider
- monitoring
A fix has been applied. Scenario executions and login functionality on us1.make.com are now returning to normal. We are continuing to monitor the zone.
provider
- resolved
This incident has been resolved.
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-0e3db6d9ef
Is Make still down?
No, this incident was resolved 2025-11-12 18:18 UTC. For Make's live state, see https://down.guide/make.
How long did it last?
1h 54m, from 2025-11-12 16:24 UTC to 2025-11-12 18:18 UTC, by the times Make posted.
What was affected?
Make named us1.make.com, us1.make.com, us1.make.com.
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.