# Executions on the us2.make.com not working

- Provider: [Make](https://down.guide/make)
- Level: confirmed
- Impact: Degraded
- lasted 21h 55m
- started 2026-03-10 13:56 UTC
- us2.make.com
- id: DWN-cb15bd13f2
- Official page: https://stspg.io/vmy39mtnswc3

## Updates from Make
### 2026-03-10 13:56 UTC: investigating
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.

### 2026-03-10 14:07 UTC: investigating
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.

### 2026-03-10 14:31 UTC: identified
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.

### 2026-03-10 14:48 UTC: monitoring
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.

### 2026-03-11 11:51 UTC: monitoring
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.

### 2026-03-11 11:51 UTC: resolved
This incident has been resolved.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).