Make Outage History

Make experienced a major incident where the dashboard was unavailable for some users across all regional components (eu1, eu2, us1 Make domains and Celonis instances). The issue was identified, a fix was implemented and monitored, and the incident was fully resolved after 40 minutes.

Make experienced a 2-hour incident where notification emails were not being sent from the EU1 zone, affecting the eu1.make.com service. The platform implemented a fix and processed all queued emails before resolving the issue.

Make experienced a major incident on the US2 zone where scenario executions were failing at an increased rate, lasting 5.3 hours starting at 17:20 CET. The engineering team identified and applied a temporary fix to stop scenarios from failing to initialize, though this caused execution delays of up to 49 minutes and some webhook rejections during remediation. The incident was fully resolved with normal operations restored and all execution delays eliminated.

AI agents on the eu2.make.com zone experienced increased error rates, causing scenarios using these modules to encounter intermittent failures and timeouts. The performance degradation affected users for 1.2 hours before being fully resolved. The issue was investigated and restored to normal operations.

Make experienced increased error rates affecting AI agents on the eu2.make.com zone, causing scenarios using AI agent modules to encounter intermittent failures and timeouts. The performance degradation impacted users for 2.1 hours before the root cause was identified and mitigated. The issue was fully resolved with normal operations restored and continued monitoring implemented.

Datastores were not appearing in the Make UI across all public and enterprise zones for 1.7 hours, though scenario executions continued running normally. The issue affected multiple Make domains including EU and US zones for both standard and Celonis enterprise instances. The problem was identified, fixed, and all Datastore content was restored to full visibility in the UI.

Make experienced delayed scenario executions on the us1.make.com zone starting at 18:45 CET, with additional delays occurring later at 21:10 CET. The issue affected automated workflow processing speeds for users on that zone. The engineering team identified and fixed the underlying problem, restoring normal scenario processing after 22.1 hours of disruption.

Make's US2 zone (us2.make.com) experienced scenario execution failures for approximately 22 hours due to service instability with an upstream third-party provider. The incident caused webhooks received between 14:36-14:51 CET to not be processed correctly, resulting in potential data loss during that window. Service was restored with some execution delays as the system processed the remaining backlog.

Make's EU1 region experienced issues with displaying module history logs, where users could access history logs but encountered infinite loading when trying to open module details in some cases. The problem was limited to the display functionality and did not affect scenario executions or any underlying data. The issue was resolved after 135 hours by identifying and fixing the root cause that prevented logs from loading properly.

Make's web application experienced loading issues across multiple zones including EU and US regions, preventing users from accessing the web interface for 31 minutes. Scenarios and hooks continued to function normally during the outage, so automated workflows were not impacted. The problem was identified and resolved, with web access restored to all affected domains.