Make outage history

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.

Make.com experienced a brief degraded performance affecting its website, specifically the Website / help.make.com and Website / apps.make.com components. The issue began at Jul 23, 2026 8:43 AM UTC, with users potentially encountering slower page loads or intermittent errors on the help and apps pages. The disruption appeared limited to these areas, with no broader service impact indicated at the time.

Status updates showed the affected components briefly in a degraded state before returning to normal by Jul 23, 2026 8:48 AM UTC. The incident lasted about five minutes and did not trigger further impacts on other Make services.

Users at Make.com faced a login outage starting at 2:23 PM UTC, with sign‑in failing across the platform while scenario executions and webhooks were initially reported as unaffected. The disruption spanned multiple regional gateways (us1.make.celonis.com, make.com, eu2.make.com, eu1.make.celonis.com, and related endpoints), causing broad login problems for many users. A fix was identified and applied by 2:33 PM UTC as engineers began monitoring results.

Over the following days the incident evolved to include Etsy API–related default connection issues that affected new connections and re-authorization flows in several zones. The issue was traced to the Etsy API and escalated with Etsy’s team to aid resolution. Some components briefly entered maintenance during the Etsy disruption, before recovery progressed, and by 12:08 PM UTC the affected apps and endpoints reported up again, signaling resumption of normal service for most users.

The Make.com outage began at 1:43 PM UTC with login failures affecting users across multiple regions. Early symptoms pointed to issues with default Etsy connections, with several components in EU and US regions listed as degraded and user reports mentioning login errors and related 422 responses. Importantly, scenario executions and webhooks were largely unaffected during the initial phase, while Make engineers investigated the root cause and coordinated with the Etsy team.

By 2:33 PM UTC, a fix was applied and many components began to recover, but a subsequent escalation linked to the Etsy API origin prompted ongoing maintenance in the EU2 region around 6:03 PM UTC. Over the following days, maintenance windows and monitoring continued in affected regions. The incident gradually resolved, with most components returning to up status by 12:08 PM UTC, restoring login access and Etsy-related connections for users.