# Make: Executions on the us2.make.com not working

- Impact (vendor’s label): none
- Status: resolved
- Started: 2026-03-10 13:56 UTC · Resolved: 2026-03-11 11:51 UTC · Duration: 22 h
- Updates: 6 · Affected components: Scenario Executions - us2.make.com, us2.make.com
- [Vendor status page: https://stspg.io/vmy39mtnswc3](https://stspg.io/vmy39mtnswc3)
- [Company: Make](https://rewindex.com/company/make.md)

## Timeline of updates

- **investigating** 2026-03-10 13:56 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.
- **investigating** 2026-03-10 14:07 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.
- **identified** 2026-03-10 14:31 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.
- **monitoring** 2026-03-10 14:48 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.
- **monitoring** 2026-03-11 11:51 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.
- **resolved** 2026-03-11 11:51 UTC: This incident has been resolved.


---
Canonical: https://rewindex.com/company/make/incidents/d4rf4b977c1s · Markdown: https://rewindex.com/company/make/incidents/d4rf4b977c1s.md · JSON: https://rewindex.com/api/v1/companies/make/incidents/d4rf4b977c1s · Generated 2026-10-18T09:35:11.614Z