Outage recap · Make

Make outage — March 10, 2026

On March 10, 2026, Make had a reported incident on Make's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Executions on the us2.make.com not working

none
Started
Mar 10, 9:56 AM EDT
Resolved
Mar 11, 7:51 AM EDT
Duration
21h 55m

Make's updates (6)

  1. investigating · Mar 10, 9:56 AM EDT

    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.

  2. investigating · Mar 10, 10:07 AM EDT

    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.

  3. identified · Mar 10, 10:31 AM EDT

    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.

  4. monitoring · Mar 10, 10:48 AM EDT

    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.

  5. monitoring · Mar 11, 7:51 AM EDT

    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.

  6. resolved · Mar 11, 7:51 AM EDT

    This incident has been resolved.

Updates are Make's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗

AIDownCheck is not affiliated with Make. This recap summarizes incidents published on Make's official status page.