Executions on the us2.make.com not working

What to do

• Check whether you use Make us2.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 21h 55m it lasted.

  Anything that failed between 2026-03-10 13:56 UTC and 2026-03-11 11:51 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 6

1. investigatingMar 10, 2026, 1:56 PM UTC

   We are experiencing problems with scenario executions on the US2 (us2.make.com) zone starting around 14:40 CET. We are currently investigating the issue.

   provider

2. investigatingMar 10, 2026, 2:07 PM UTC

   Service recovered. The issues affecting scenario executions on us2.make.com since 14:40 CET have been restored. Scenarios execution recovered. You may experience a delay in the scenario executions. We are continuing our investigation into the root cause.

   provider

3. identifiedMar 10, 2026, 2:31 PM UTC

   We have identified the root cause of the execution issues on the US2 (us2.make.com) zone. The disruption was linked to a service instability with one of our upstream third-party providers. While systems are back to normal, please be aware that scenario executions might be delayed as we process the remaining backlog. We are working closely with the third-party provider to ensure a permanent fix and to prevent any recurrence.

   provider

4. monitoringMar 10, 2026, 2:48 PM UTC

   We have identified the root cause of the execution issues on the US2 (us2.make.com) zone. The disruption was linked to a service instability with one of our upstream third-party providers. As we continue to investigate the recent issue on US2 zone, our investigation has identified a specific window of possible data loss. Webhooks reaching Make between 14:36 and 14:51 CET were not processed correctly due to the service disruption.

   provider

5. monitoringMar 11, 2026, 11:51 AM UTC

   We have successfully restored full stability to the US2 zone. Following a period of monitoring and a deep-dive investigation, we can now confirm that all systems are operating at peak performance and the execution backlog has been fully processed. The disruption was triggered by service instability within a critical infrastructure component managed by one of our upstream third-party providers. This instability directly impacted our ability to process incoming requests and execute scenarios.

   provider

6. resolvedMar 11, 2026, 11:51 AM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.