Historial de interrupciones de Make

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.

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.

We are currently investigating an issue in the zone eu2.make.com which can affect scenario executions and credits. We will provide more updates within the next hour.

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

We are continuing to investigate this issue.

Our team has identified the cause of the zone overload and applied mitigations. eu2.make.com is operational again and we are monitoring the systems

This incident has been resolved.

We've identified that Meta API is experiencing issues impacting Facebook Leads* data and payloads. Our team created a bug report and escalated this to Meta team and awaiting their confirmation & resolution of the ongoing issue. We are actively monitoring the situation and will update you as soon as we have an update or more information available.

Facebook Lead Ads API traffic is looking stable for now. We keep monitoring the situation and awaiting confirmation from Meta about situation being fully resolved

Meta has resolved the issue on their end, and API traffic has returned to normal state. Your Facebook Lead Ads scenarios should now be working as expected, and new leads from Facebook will resume flowing through without issues. If you are still experiencing issues, do not hesitate to contact our support.

We are currently experiencing problems with loading the dashboard for some users. The root cause is identified and we are currently deploying the a fix.

Fix deployed. Monitoring.

This incident has been resolved.

We are currently experiencing problems with loading the dashboard for some users. The root cause is identified and we are currently working on a fix.

We are continuing to investigate this issue.

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

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

This incident has been resolved.

We are currently investigating an issue with notification e-mails not being sent from the EU1 zone.

The fix has been implemented and we are monitoring the results. All the e-mails have been processed.

We are continuing to monitor for any further issues.

This incident has been resolved.

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.

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.

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.

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.

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.

This incident has been resolved.

We are currently investigating reports of increased error rates affecting AI agents on the eu2.make.com zone. Scenarios utilizing these modules may experience intermittent failures or timeouts. We are working to identify the root cause and will provide further updates shortly.

Issue has been resolved, everything is operational.

We are currently investigating reports of increased error rates affecting AI agents on the eu2.make.com zone. Scenarios utilizing these modules may experience intermittent failures or timeouts. We are working to identify the root cause and will provide further updates shortly.

The issue affecting AI agents on the eu2.make.com zone has been identified and mitigated. Scenarios utilizing AI agent modules are now operating normally. We will continue to monitor the platform closely to ensure continued stability.

Issue has been resolved, everything is operational.

We are currently investigating an issue where Datastores are not appearing within the Make UI across all public and enterprise zones. Please note that scenario executions remain unaffected and are running as expected.

Scenarios using datastore modules are unaffected.

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

A fix has been implemented, content of the datastores is now being displayed in the Make UI.

The issue causing Datastore content to disappear from the UI has been fixed. All Datastore contents are now visible across public and enterprise zones, and all platform features are fully operational.

We are currently investigating delayed scenario executions on the us1.make.com zone. The issue began at 18:45 CET. Our engineering team is working to restore normal processing speeds.

Update: Scenario execution delays in the us1.make.com zone have subsided, and backlogged executions are currently being processed. While system performance has returned to nominal levels, our team remains in an active investigation to determine the root cause and prevent recurrence.

We're experiencing further delays in scenario executions since 21:10 CET. We have identified the issue and our engineering team is working to restore normal processing speeds.

We have fixed the issue and the scenario processing has returned back to normal. We'll continue to monitor the situation.

This incident has been resolved.

We are experiencing problems with scenario executions on the US2 (us2.make.com) zone starting around 14:40 CET. We are currently investigating the issue.

Service recovered. The issues affecting scenario executions on us2.make.com since 14:40 CET have been restored. Scenarios execution recovered. You may experience a delay in the scenario executions. We are continuing our investigation into the root cause.

We have identified the root cause of the execution issues on the US2 (us2.make.com) zone. The disruption was linked to a service instability with one of our upstream third-party providers. While systems are back to normal, please be aware that scenario executions might be delayed as we process the remaining backlog. We are working closely with the third-party provider to ensure a permanent fix and to prevent any recurrence.

We have identified the root cause of the execution issues on the US2 (us2.make.com) zone. The disruption was linked to a service instability with one of our upstream third-party providers. As we continue to investigate the recent issue on US2 zone, our investigation has identified a specific window of possible data loss. Webhooks reaching Make between 14:36 and 14:51 CET were not processed correctly due to the service disruption.

We have successfully restored full stability to the US2 zone. Following a period of monitoring and a deep-dive investigation, we can now confirm that all systems are operating at peak performance and the execution backlog has been fully processed. The disruption was triggered by service instability within a critical infrastructure component managed by one of our upstream third-party providers. This instability directly impacted our ability to process incoming requests and execute scenarios.

This incident has been resolved.

We are investigating issues with loading module history logs in EU1 (eu1.make.com) It's possible to open history logs, but trying to open a module detail results in infinite loading in some cases. Scenario executions are not impacted.

We continue to investigate the issue. We can see the data does exist and the problem is limited to displaying it for all cases we could find.

We identified the problem that prevented logs from being loaded. We solved the issue by and will actively monitor this for the next days. No data was affected and you can now see the log details again.

Our monitoring confirmed that the issue has been resolved.