Make outage history

Between 16:00–16:45 CEST, US2 Zone (us2.make.com) experienced delays in scenario executions due to high resource utilization. The root cause has been identified and the situation is now stable. All affected scenarios from this timeframe have been reactivated.

There was an issue causing delays with scenario executions on the EU1 (eu1.make.com) region between 10:45 and 11:05 CEST. The issue has been resolved, and the service is now fully operational and working normally. Thank you for your patience, and we apologize for any inconvenience this may have caused.

We are currently investigating an issue affecting the EU2 (eu2.make.com) region. Impacted Services: • Scenario Creation: Users are currently unable to savemodified scenarios. • Manual Execution: Triggering scenarios manually is currently failing. Status: Automated scenario runs are continuing as scheduled, but manual executions and new builds are not working. Our engineering team identified the issue and is working on a fix. We are actively working on a fix and will provide an update within the next 30 minutes, or as soon as more information becomes available. We apologize for the disruption to your workflows.

We are continuing to work on a fix for this issue.

The issue affecting the EU2 (eu2.make.com) region has been fully resolved, and all system operations have returned to normal.

Following a recent update, a subset of scenarios was temporarily disabled to prevent unexpected behavior. We have identified the root cause and successfully rolled back the deployment. Our team is currently in the process of systematically reactivating the impacted scenarios and verifying their performance. Impact: Users may have experienced issues triggering or running certain scenarios during this window. Full functionality is expected to be restored shortly.

The issue has been identified and a fix is being implemented.

Update: All previously impacted scenarios have now been successfully re-enabled following the release rollback. Status: System metrics are stable, and scenario execution has returned to normal. We are actively monitoring the environment to ensure continued stability before fully resolving this incident.

This incident has been resolved.

Claude Fable 5, the Claude Opus model family, and the OpenAI GPT (pro & sol) models are temporarily unavailable in Make AI Provider, Make AI Toolkit and Anthropic Claude - simple text prompt module. All other models remain fully operational while we work to restore complete functionality as quickly as possible.

Claude Fable 5, the Claude Opus model family, and the OpenAI GPT (pro & sol) models are available again in Make AI Provider, Make AI Toolkit and the Anthropic Claude - Simple Text Prompt module. All models are now fully operational. Thank you for your patience.

Some scenarios in eu1.make.celonis.com may have experienced delayed starts between 11:32 and 12:06 CEST. The situation is stable and our engineers continue to work to prevent it from from reoccurring.

The issue has been identified.

eu1.make.celonis.com remains stable and scenario executions are running as expected. We are continuing to monitor the zone closely and will provide a final update once we have confirmed stability.

Unexpected database load from another Make component caused a CPU spike that delayed scenario executions in eu1.make.celonis.com. This has been addressed and the zone is operating normally.

We are currently investigating a minor incident affecting approximately 250 scenarios to fail. Impact appears limited, and our team is actively working to confirm the full scope and root cause. We will provide an update as soon as more information is available.

Our engineers are continuing to investigate this issue with highest priority. We will provide a further update within the next hour.

We have identified the cause of the scenario execution failures affecting approximately 250 scenarios. Our team is currently re-enabling any scenarios that were disabled as a result, and is working on a fix to prevent this issue from reoccurring. We will provide a further update once the fix has been applied.

We’re reaching out to let you know that the issue affecting scenario execution has been resolved, and most of the previously disabled scenarios have been re-enabled. Remaining affected scenarios will be handled individually. System execution has stabilized and normal operations have resumed.

Between 17:29 and 17:34 CEST on 22nd of July, scenarios on the EU1 zone failed at initialization with a "Failed to verify account" error, affecting connections across all apps. Approximately 200 scenarios were automatically deactivated as a result and have since been re-enabled. We are actively working to prevent recurrence.

Hello, we are analyzing an ongoing issue impacting new connection creation & connection-re-authorization resulting in TypeError (SC424 error) on US2 zone. We are investigating root cause of this problem. We will update you asap on the progress.

The issue has been resolved at 10:00 CEST.

We are currently experiencing a problem with logging in to the make.com. Scenario executions and webhooks are not being affected. We are investigating the cause of the problem and will share updates shortly.

The issue has been identified and fix applied, we are currently monitoring the results.

This incident has been resolved.

Hello, we are analysing ongoing issue with default connection for Etsy resulting in error "invalid_target: resource indicator must be an absolute URI without a fragment.". We are investigating root cause of this problem and we have escalated this issue towards Etsy team as well to help us resolving the situation. We will update you regularly on progress. Thanks for your patience.

We want to update you on progress of ongoing issue for Etsy connection. Our investigation is showing this issue origin is coming from Etsy API and we are escalating this issue with their team. We are actively monitoring the situation and will inform you asap. Thank you for your patience

Etsy issue impacting default connection on Make is now resolved after temporary outage from Etsy side.

We are currently experiencing a problem with logging in to the make.com. Scenario executions and webhooks are not being affected. We are investigating the cause of the problem.

Our team has identified an issue and applied the fix, we are monitoring the results.

We are continuing to monitor for any further issues.

This incident has been resolved.

Hello, we are investigating ongoing issue with OAuth resulting in  "The application is disabled" for LinkedIn * connections on Make resulting in disrupted connections. We are in touch with LinkedIn team to resolve this issue as soon as we can. In the meanwhile we suggest using OpenID connection or own OAuth credentials. We will update you regularly on progress. Thanks for your patience.

We have identified root cause of the issue resulting "The application is disabled" for LinkedIn * connections on Make. We are in active cooperation with LinkedIn team in order to resolve this issue as soon as we can. We will update you regularly on progress.

Update on this issue with LinkedIn connections. We are awaiting approval from LinkedIn side in order to re-enable Make OAuth app. We will provide update when approved.

We have implemented a fix to restore LinkedIn connections. While services appear stable, we are continuing to monitor the integration closely.

Issue with LinkedIn connections was fully restored.

We identified an edge case issue in Datastore Update record module was removing data from fields that were left empty in the module configuration after scenario was edited. Our team already applied the fix and and currently investigating the issue further to confirm the impact. In case you have a suspect your data were affected please contact our support team.

Our team identified the root cause and responsible component of the previously reported issue. A bug introduced on June 29, 2026 at 12:17 PM CEST caused null field values to be converted to empty strings when a scenario was edited. Due to the same root cause the blueprints of all scenarios that were edited and saved during the affected period were incorrectly modified. Our team is still analysing the full scope of the impact — the highest confirmed impact is on the Datastore App. The fix was applied on June 30, 2026 at 3:36 PM CEST. All zones are now operating normally. [ACTION REQUIRED] Please perform a hard reload of your browser tab to prevent any further impact. If you edited and saved any scenario between June 29, 12:17 PM CEST and June 30, 3:36 PM CEST, its blueprint may have been incorrectly modified. If you notice unexpected empty fields, please revert to a version saved before June 29, 12:17 PM CEST, or if you need further assistance, please contact our support team to get the data snapshot from before the issue was introduced.

The incident has been resolved. We have informed the owners of potentially affected organizations by email that they may be affected and what actions to take if they see issues.

We are currently experiencing a problem with logging in to the make.com. Scenario executions and webhooks are not being affected. We are investigating the cause of the problem.

We are continuing to investigate this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We're currently investigating degraded performance affecting our EU regions. Users in these regions may experience slower loading of the Make web app and dashboard, and some actions may take longer than usual or occasionally time out. Executions shouldn't be affected

We've identified the source of the slowdown affecting the web app in our EU regions and applied fix - the service should be functional.

We are continuing to monitor the service closely to ensure full stability before marking the incident as resolved.

The incident is now resolved. All EU regions have returned to normal performance. Thank you for your patience.

We are currently experiencing problem with login to the make.com user interface. Scenario executions and webhooks are not being affected. We are investigating the cause of the problem.

We continue with the problem investigation.

The issue has been identified and login is now possible to all zones. We keep monitoring the system.

The incident has been resolved.

Between 15:30 and 17:27 CEST, some users might experienced an increased number of failed or invalid scenarios on zones EU1, EU2, US1, US2. This was caused by an incident on Cloudflare's side, where their API returned 500 errors affecting request routing through our infrastructure. The issue was fully resolved by 17:27 CEST once Cloudflare restored normal API operation. We apologise for the inconvenience.

Between 14:05 and 14:35 CEST (12:05 – 12:35 UTC), we experienced an issue that caused intermittent login instability across our platform. Our engineering team identified the root cause and applied a fix, restoring full access.

We are currently investigating an issue with not being able to log in to the platform. Executions are not affected.

We have identified the root cause and applied remediations. The affected zones are stable, and we are actively monitoring our systems

This incident has been resolved.