Affected components
Update timeline
- investigating Mar 31, 2026, 03:48 PM UTC
We are currently observing the increased number of failing scenario executions on the us2.make.com zone. The issue began at 17:20 CET. Our engineering team is working on investigating this issue.
- identified Mar 31, 2026, 04:33 PM UTC
We identified the root cause of the incident and applied a temporary fix. Scenarios are no longer failing to initialize. We continue with the investigation.
- identified Mar 31, 2026, 05:14 PM UTC
As a side effect of the remediation, scheduled executions have been delayed by approximately 10 minutes. Some incoming webhook requests may have been rejected. We are now processing the execution queue and the processing capacity of the zone is returning to normal state.
- identified Mar 31, 2026, 06:37 PM UTC
The scenario queue processing has been stabilized. We are still experiencing a minor delay in scenario executions of approximately 8 minutes compared to the scheduled execution times. We continue implementing a permanent solution.
- monitoring Mar 31, 2026, 07:21 PM UTC
The scenario queue has been fully processed and the zone is now operating under normal conditions. During the course of the incident, some scenario executions have been delayed for up to 49 minutes from their scheduled execution time. All scenarios are now being executed without delays. We are switching the incident status to Monitoring. We apologize for any inconvenience caused.
- resolved Mar 31, 2026, 09:02 PM UTC
This incident has been resolved.
Looking to track Make downtime and outages?
Pingoru polls Make's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Make reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Make alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required