- Level
- confirmed
- Worst impact
- Degraded
- Components
- us1.make.com
What to do
Check whether you use Make 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 52m it lasted.
Anything that failed between 2026-01-27 15:46 UTC and 2026-01-27 17:38 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 delayed executions on the US1 zone.
provider
- identified
Issue has been identified. We are currently working on a fix.
provider
- monitoring
The issue affecting the US1 zone has been mitigated, and all services are now fully operational. Our engineering team will continue to monitor the zone closely over the next several hours.
provider
- resolved
The 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-5fade37398
Is Make still down?
No, this incident was resolved 2026-01-27 17:38 UTC. For Make's live state, see https://down.guide/make.
How long did it last?
1h 52m, from 2026-01-27 15:46 UTC to 2026-01-27 17:38 UTC, by the times Make posted.
What was affected?
Make named 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.