Make outage history

In the us1.make.celonis.com region, Make experienced degradation that affected scenario executions, webhook processing, and general platform access. Core components including Website, Responsive Webhooks, Scenario Executions, and Apps in us1.make.celonis.com showed degraded status as engineers investigated. The impact began at Sep 18, 2026 12:23 PM UTC and was resolved by Sep 18, 2026 2:18 PM UTC, with users experiencing instability for about two hours.

An outage in the Make EU1 region caused instability across core services, including webhook processing, scenario executions, and access to the Make platform. Impact began at Sep 9, 2026 4:15 PM UTC with the eu1.make.com components showing degraded performance; users reported failed automations and intermittent portal access. Make's status page indicated an active investigation and plans to provide an update within an hour. The issue was resolved by 5:03 PM UTC, at which point the affected components returned to normal and services were recovered. Reports from users were limited, suggesting the disruption was largely contained to the EU1 region and primarily affected automation and webhook delivery.

Make’s EU2 environment experienced a brief degradation affecting scenario saving and related execution tasks. Users reported they could not save updates to their scenarios, and execution operations in eu2.make.com were impacted. The issue appeared to start around 11:30 AM UTC with user reports, and Make flagged the degraded service at 11:38 AM UTC; this degraded state persisted for about ten minutes and was resolved by 11:48 AM UTC.

Make experienced a brief degradation of the Website / apps.make.com component, starting at 2:38 PM UTC and resolving at 2:43 PM UTC, lasting about five minutes. The status page showed the affected component briefly listed as degraded (warn) before returning to normal. The issue was localized to this component with no lasting impact.

Make's Scenarios feature in the us2.make.com region was temporarily disabled, disrupting automated workflow executions for about twenty minutes. The official status update at 11:33 AM UTC indicated that Scenarios were disabled and that a fix was being implemented for the Scenario Executions component in us2.make.com.

By 11:53 AM UTC, the status returned to normal and Scenarios were re-enabled, with updates confirming the issue had been identified and a fix deployed. The issue appeared contained to the us2 region and affected only Scenario executions during that interval.

Make experienced a partial outage affecting access to several AI models in the eu1.make.com and us2.make.com regions. The incident began when Make flagged limited availability for Claude Fable 5, the Claude Opus family, and the OpenAI GPT models (pro and sol) within Make AI Provider and Make AI Toolkit, while other models remained operational. The affected components were Scenario Executions and Apps in both eu1.make.com and us2.make.com, and engineers worked to restore full functionality.

Users in the eu1.make.celonis.com environment experienced delays in running scenario executions starting at 10:33 AM UTC. The issue also impacted the Responsive Webhooks component in the same environment, causing degraded performance for automation workflows and connected integrations. By 11:23 AM UTC, Make confirmed that approximately 250 scenarios were affected, and teams began re-enabling impacted scenarios while developing a long-term fix to prevent recurrence. The recovery progressed over the next day, with services gradually returning to normal in the eu1 environment.

The incident was actively triaged with identified causes and a planned fix, and by 12:38 PM UTC the affected components had returned to up status, indicating normal operation resumed.

Make experienced a degraded scenario execution incident starting at 7:58 AM UTC, impacting roughly 250 scenarios across multiple regions (eu1.make.com, eu2.make.com, us1.make.com, and us2.make.com) and the related Celonis endpoints (eu1.make.celonis.com, us1.make.celonis.com). Users attempting to run automations could see failures or delays as affected scenarios did not execute as expected. The Make team began investigating promptly and started re-enabling affected scenarios as they worked to confirm the scope and root cause.

At 9:43 AM UTC engineers identified the cause and prioritized a fix to prevent recurrence. Recovery progressed through the day with targeted re-enables of impacted components, including the Celonis endpoints, as updates indicated stabilization. The condition moved from degraded toward full recovery, with progress noted in subsequent updates, and the service returned to normal by 12:38 PM UTC.

Make entered a maintenance window starting at 6:03 PM UTC affecting the Website / make.com, Apps / make.com, and Scenario Executions / make.com. During this period, users would have experienced paused access to the platform's core interfaces and automation execution. The maintenance concluded when the services returned to normal at 10:03 PM UTC, after roughly four hours, with all components resuming standard operations. The Make status page reflected the transition from up to maintenance and back to up, signaling a planned but comprehensive maintenance window.

Make conducted a scheduled maintenance window on us1.make.celonis.com that affected core components including Website, Responsive Webhooks, Scenario Executions, and Apps. During the maintenance period, users may have experienced limited access or degraded functionality as these services were placed into maintenance mode. The maintenance began at 6:03 PM UTC and completed when the components returned to normal operation at 10:03 PM UTC.