Make

Affected: eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-12 08:23 UTC

   Scenarios with the "Scenario" app (e.g. "Start a scenario", "Run a scenario" or "Return output") are throwing a validation error when the run begins. We are currently investigating the issue.

2. identified 2026-10-12 08:36 UTC

   The issue has been identified and our team is fixing it. Some scenarios may be deactivated; we'll re-enable them.

3. resolved 2026-10-12 09:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-09-23 10:30 UTC

   Scenario logs in the UI were not loading. Clicking on logs in scenario history timed out. Fetching logs via API was not impacted. All zones were affected. The issue was already fixed.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: us1.make.celonis.com, us1.make.celonis.com, us1.make.celonis.com, us1.make.celonis.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-18 12:22 UTC

   We are investigating an issue affecting the us1.make.celonis.com region. Users may experience instability with scenario executions, webhook processing, and overall platform access. Our engineering team is actively working to restore stability, and we will share another update...

2. identified 2026-09-18 12:40 UTC

   Update: We have identified the root cause of the issue and our engineering team is actively working on a resolution. Further updates will be provided as progress is made..

3. identified 2026-09-18 13:08 UTC

   Update: Investigation is still ongoing. Our team is actively analyzing the issue to determine the root cause, and we will share further details as soon as more information becomes available.

4. identified 2026-09-18 13:36 UTC

   Investigation still ongoing. We are actively working to isolate the issue and will provide another update shortly.

5. monitoring 2026-09-18 14:14 UTC

   Update: Corrective actions have been applied, and the situation has stabilized. We are actively monitoring the platform to ensure full performance and recovery. We will continue to provide updates as we observe system behavior.

6. resolved 2026-09-18 17:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com, eu1.make.com, eu1.make.com

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-09 16:11 UTC

   We are investigating an issue affecting the eu1.make.com region. Users may experience instability with scenario executions, webhook processing, and overall platform access. Our engineering team is actively working to restore stability, and we will share another update within the...

2. monitoring 2026-09-09 16:59 UTC

   Operational metrics on eu1.make.com have returned to healthy levels. While system operations have normalized, our engineering team remains in a monitoring state to verify that performance remains consistent

3. resolved 2026-09-10 10:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-09-02 14:00 UTC

   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.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com, eu1.make.com

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-08-26 09:21 UTC

   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...

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu2.make.com, eu2.make.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-08-24 11:36 UTC

   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...

2. identified 2026-08-24 11:37 UTC

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

3. resolved 2026-08-24 11:46 UTC

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

Excerpts are shortened. Read the full incident on Make's status page.

Affected: us2.make.com

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-14 11:28 UTC

   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...

2. identified 2026-08-14 11:31 UTC

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

3. monitoring 2026-08-14 11:48 UTC

   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...

4. resolved 2026-08-14 12:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com, eu1.make.com, us2.make.com, us2.make.com

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Anthropic (Claude), OpenAI.

Started during Anthropic (Claude): Elevated errors across many models.

1. identified 2026-08-04 20:43 UTC

   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...

2. resolved 2026-08-10 15:10 UTC

   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.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.celonis.com, eu1.make.celonis.com

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-30 10:32 UTC

   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.

2. identified 2026-07-30 10:32 UTC

   The issue has been identified.

3. monitoring 2026-07-30 11:19 UTC

   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.

4. resolved 2026-07-31 11:51 UTC

   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.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com, make.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-30 07:55 UTC

   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.

2. investigating 2026-07-30 08:54 UTC

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

3. identified 2026-07-30 09:41 UTC

   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...

4. resolved 2026-07-31 12:35 UTC

   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...

Excerpts are shortened. Read the full incident on Make's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-07-22 15:30 UTC

   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....

Excerpts are shortened. Read the full incident on Make's status page.

Affected: us2.make.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-19 05:58 UTC

   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.

2. resolved 2026-07-20 08:49 UTC

   The issue has been resolved at 10:00 CEST.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com, make.com

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-17 14:22 UTC

   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.

2. monitoring 2026-07-17 14:28 UTC

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

3. resolved 2026-07-17 15:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-17 13:34 UTC

   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...

2. identified 2026-07-17 15:39 UTC

   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...

3. resolved 2026-07-22 12:07 UTC

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

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com, make.com

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-17 10:20 UTC

   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.

2. monitoring 2026-07-17 10:27 UTC

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

3. monitoring 2026-07-17 10:27 UTC

   We are continuing to monitor for any further issues.

4. monitoring 2026-07-17 10:29 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-07-17 12:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-07 06:50 UTC

   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...

2. identified 2026-07-07 08:27 UTC

   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.

3. identified 2026-07-07 14:01 UTC

   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.

4. monitoring 2026-07-09 13:27 UTC

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

5. resolved 2026-07-14 13:22 UTC

   Issue with LinkedIn connections was fully restored.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-06-30 09:59 UTC

   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....

2. monitoring 2026-06-30 14:59 UTC

   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...

3. resolved 2026-06-30 20:33 UTC

   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.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com, make.com

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-29 16:22 UTC

   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.

2. investigating 2026-06-29 17:01 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-06-29 17:12 UTC

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

4. resolved 2026-06-29 18:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com, eu2.make.com, eu1.make.celonis.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-21 08:22 UTC

   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

2. identified 2026-06-21 08:36 UTC

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

3. monitoring 2026-06-21 08:37 UTC

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

4. resolved 2026-06-21 10:24 UTC

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

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com, make.com

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-19 14:08 UTC

   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.

2. investigating 2026-06-19 14:47 UTC

   We continue with the problem investigation.

3. monitoring 2026-06-19 14:50 UTC

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

4. resolved 2026-06-19 15:11 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. resolved 2026-06-12 13:30 UTC

   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...

Excerpts are shortened. Read the full incident on Make's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-05-27 12:00 UTC

   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.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com, make.com

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-22 09:57 UTC

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

2. monitoring 2026-05-22 10:23 UTC

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

3. resolved 2026-05-22 12:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu2.make.com, eu2.make.com

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-13 10:49 UTC

   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.

2. investigating 2026-05-13 12:15 UTC

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

3. investigating 2026-05-13 12:15 UTC

   We are continuing to investigate this issue.

4. monitoring 2026-05-13 14:10 UTC

   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

5. resolved 2026-05-13 18:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-05-13 08:19 UTC

   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...

2. monitoring 2026-05-13 13:27 UTC

   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

3. resolved 2026-05-14 05:59 UTC

   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...

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-20 08:52 UTC

   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.

2. investigating 2026-04-20 08:54 UTC

   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.

3. monitoring 2026-04-20 09:15 UTC

   Fix deployed. Monitoring.

4. resolved 2026-04-20 09:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-17 14:35 UTC

   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.

2. investigating 2026-04-17 14:36 UTC

   We are continuing to investigate this issue.

3. identified 2026-04-17 14:51 UTC

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

4. monitoring 2026-04-17 14:52 UTC

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

5. resolved 2026-04-17 15:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-15 15:19 UTC

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

2. monitoring 2026-04-15 15:58 UTC

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

3. monitoring 2026-04-15 17:14 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-04-15 17:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: us2.make.com

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-31 15:48 UTC

   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.

2. identified 2026-03-31 16:33 UTC

   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.

3. identified 2026-03-31 17:14 UTC

   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.

4. identified 2026-03-31 18:37 UTC

   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.

5. monitoring 2026-03-31 19:21 UTC

   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...

6. resolved 2026-03-31 21:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu2.make.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-30 14:24 UTC

   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.

2. resolved 2026-03-30 15:31 UTC

   Issue has been resolved, everything is operational.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu2.make.com, eu2.make.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-29 12:28 UTC

   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.

2. monitoring 2026-03-29 12:55 UTC

   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.

3. resolved 2026-03-29 14:30 UTC

   Issue has been resolved, everything is operational.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-25 07:11 UTC

   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.

2. investigating 2026-03-25 07:22 UTC

   Scenarios using datastore modules are unaffected.

3. identified 2026-03-25 08:02 UTC

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

4. monitoring 2026-03-25 08:28 UTC

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

5. resolved 2026-03-25 08:48 UTC

   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.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: us1.make.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-11 18:25 UTC

   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.

2. investigating 2026-03-11 18:44 UTC

   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...

3. identified 2026-03-11 20:56 UTC

   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.

4. monitoring 2026-03-11 21:54 UTC

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

5. resolved 2026-03-12 13:49 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: us2.make.com

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-03-10 13:56 UTC

   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.

2. investigating 2026-03-10 14:07 UTC

   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.

3. identified 2026-03-10 14:31 UTC

   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...

4. monitoring 2026-03-10 14:48 UTC

   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...

5. monitoring 2026-03-11 11:51 UTC

   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...

6. resolved 2026-03-11 11:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-27 19:48 UTC

   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.

2. investigating 2026-02-27 20:18 UTC

   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.

3. monitoring 2026-02-27 21:00 UTC

   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.

4. resolved 2026-03-05 10:47 UTC

   Our monitoring confirmed that the issue has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-24 10:45 UTC

   We are currently observing problem with web access on multiple zones and we are investigating the issue. Scenarios and hooks work fine and the issue doesn't have impact on them.

2. investigating 2026-02-24 10:45 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-02-24 10:49 UTC

   The problem has been found and resolved; websites are accessible again. We are currently monitoring the results.

4. resolved 2026-02-24 11:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com, make.com

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-11 12:44 UTC

   We have restored full login functionality for the majority of our zones. While most users can now log in as expected, we are still seeing a partial outage specifically affecting the EU1 zone.

2. identified 2026-02-11 12:50 UTC

   The issue affecting logins for newly added users has been fully resolved. All zones, including EU1, have returned to operating status.

3. monitoring 2026-02-11 12:51 UTC

   We are now monitoring the systems to ensure stability for all users.

4. resolved 2026-02-11 12:56 UTC

   We have confirmed that the login issues are fully resolved and all systems are performing normally.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: us1.make.com

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-27 15:46 UTC

   We are currently experiencing delayed executions on the US1 zone.

2. identified 2026-01-27 15:52 UTC

   Issue has been identified. We are currently working on a fix.

3. monitoring 2026-01-27 16:47 UTC

   The issue affecting the US1 zone has been mitigated, and all services are now fully operational. Our engineering team will continue to monitor the zone closely over the next several hours.

4. resolved 2026-01-27 17:38 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu2.make.com, eu1.make.celonis.com

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-03 05:31 UTC

   We are currently investigating reports of service unavailability affecting the two of our zones. Our engineering team is currently looking into the root cause. We will provide an update as soon as we have more information

2. investigating 2026-01-03 06:43 UTC

   The investigation is ongoing. We are still working to determine the root cause.

3. investigating 2026-01-03 06:48 UTC

   We are continuing to investigate the issue preventing users from logging in. Please be assured that while access is currently restricted, all scenarios are processing normally in the background.

4. investigating 2026-01-03 09:52 UTC

   We are still diagnosing the issue affecting user access. Please note that while logins are currently unavailable, all background scenarios are processing successfully as scheduled.

5. monitoring 2026-01-03 10:48 UTC

   We have identified the root cause of the issue affecting user access and applied a fix. We will continue to monitor to system to ensure the issue is fully resolved.

6. resolved 2026-01-03 20:51 UTC

   We can confirm that the incident is fully resolved. All the affected components are running as expected without any issues.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, make.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-19 18:02 UTC

   We are currently experiencing issues with registrations of new users. Our teams are investigating the cause of the issues. Service functionality is not being affected.

2. identified 2025-12-19 18:22 UTC

   Problem has been identified. Our engineering team is working on the fix.

3. monitoring 2025-12-19 18:39 UTC

   A fix has been implements. New users registration are working again.

4. resolved 2025-12-19 19:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com, make.com

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-19 00:17 UTC

   We are experiencing issues with login to the platform. We are investigating the issue.

2. investigating 2025-12-19 00:22 UTC

   Webhooks and scenario executions are working fine.

3. investigating 2025-12-19 00:55 UTC

   Investigation of the issue is still ongoing.

4. identified 2025-12-19 01:34 UTC

   Issue has been identified and we are currently working on a fix.

5. identified 2025-12-19 01:57 UTC

   Fix has been identified. We are currently working on recovery.

6. identified 2025-12-19 02:45 UTC

   Recovery of the service is in progress. Login to the Make interface is working on following zones: eu1.make.com us1.make.com us2.make.com eu1.make.celonis..com us1.make.celonis.com

7. identified 2025-12-19 02:48 UTC

   Login to Make interface on eu2.make.com restored

8. monitoring 2025-12-19 03:28 UTC

   Service is restored. We are currently backfilling execution logs from the window of 1:00 CET – 4:30 CET. While core functionality is unaffected, you may notice a delay in log visibility for that specific timeframe as processing continues.

9. resolved 2025-12-19 11:02 UTC

   Backfilling of missing execution logs was successfully finished. All systems are fully operational and all executions logs should be visible in the system.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com, make.com

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-12-17 18:15 UTC

   We are investigating issues related to Google SSO login. If you are facing issues logging in with SSO or social logins such as "Log in with Google", you can get immediate access by clicking "Forgot password?" to define a password and log in with your email until this is...

2. identified 2025-12-17 21:03 UTC

   Issue has been identified and we are currently working on a recovery.

3. monitoring 2025-12-17 21:54 UTC

   We had an issue associating users with their corresponding Google SSO IDs, which prevented users from signing in with Google from about 19:15 CET to 22:50 CET. We initially thought it could be a widespread issue with SSO, but concluded only Google was affected. We have now...

4. resolved 2025-12-17 22:15 UTC

   Our logs and monitoring verify that the issue is now resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com, eu1.make.com, eu1.make.com, eu1.make.com, eu2.make.com, eu2.make.com, eu2.make.com, eu2.make.com, us1.make.com, us1.make.com, us1.make.com, us1.make.com, us2.make.com, us2.make.com, us2.make.com, us2.make.com, eu1.make.celonis.com, eu1.make.celonis.com, eu1.make.celonis.com, eu1.make.celonis.com, us1.make.celonis.com, us1.make.celonis.com, us1.make.celonis.com, us1.make.celonis.com, make.com, make.com, make.com, help.make.com, apps.make.com

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-12-05 09:12 UTC

   Make services are currently not accessible from the Internet. This applies to the website, login and all Make execution zones. The ability to receive webhooks is limited. At this point, we suspect that the issue is caused by an outage at a 3rd party supplier side Cloudflare....

2. monitoring 2025-12-05 09:18 UTC

   Make is accessible again. This correlates with a status update shared by our third-party provider, Cloudflare, indicating that a fix has been implemented on their side. We are closely monitoring the system. Some of your Make scenarios may have been automatically disabled due to...

3. resolved 2025-12-05 10:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2025-11-27 15:38 UTC

   We have encountered problems with scenario executions on the EU1 (eu1.make.com) zone starting around 9:45 CET until 12:30 CET. Users may have experienced delays when attempting to execute scenarios; some scenarios might have been terminated. The issue has been identified and a...

2. resolved 2025-11-28 10:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu2.make.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-21 11:18 UTC

   We're encountering issues executing scenarios on Zone EU2. Users may experience delays and errors when attempting to execute scenarios in this zone, with the issue being noticed since 11:45 CET. We're currently investigating this issue and will update Statuspage within the next...

2. monitoring 2025-11-21 11:32 UTC

   We have resolved the issue causing delayed scenario executions in Zone EU2. The resolution was implemented at 12:20 CET. We are currently monitoring the platform to ensure full stability.

3. resolved 2025-11-21 16:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com, make.com, help.make.com, apps.make.com

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-11-18 12:14 UTC

   Website access may be intermittently affected due to an incident reported by our third-party service provider (Cloudflare).

2. identified 2025-11-18 15:38 UTC

   External applications using Cloudflare are likely also affected and you may see errors in your scenarios. We'll continue investigating the impact and will update as we have more information

3. resolved 2025-11-18 20:48 UTC

   Cloudflare communicated that they fixed their issue. We are resolving this incident as no related issue has been identified on our side.

Excerpts are shortened. Read the full incident on Make's status page.

Affected: us1.make.com, us1.make.com, us1.make.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-12 16:24 UTC

   We are currently experiencing an issue on the zone us1.make.com Login/Access to the website and scenario execution might be impacted. We are investigating the issue and will provide more updates within one hour.

2. investigating 2025-11-12 16:25 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-11-12 17:29 UTC

   A fix has been applied. Scenario executions and login functionality on us1.make.com are now returning to normal. We are continuing to monitor the zone.

4. resolved 2025-11-12 18:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Make's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-11-11 17:40 UTC

   Between 6:40pm - 6:54pm CET we experienced an infrastructure issue that affected scenario executions in the us1.make.com zone as follows: - Scenarios scheduled to run in the affected time interval were delayed by up to 18 minutes. - Scenarios that are triggered by a webhook were...

Excerpts are shortened. Read the full incident on Make's status page.

Affected: eu1.make.celonis.com, us1.make.celonis.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-11-07 19:11 UTC

   Customers on eu1.make.celonis.com and us1.make.celonis.com zones cannot access the AI Agents section in the product UI. Existing AI agents continue to run as expected. Team identified the root cause of the issue and is working on a fix.

2. identified 2025-11-07 19:49 UTC

   The fix has been completed and is getting ready to be deployed. We identified the following workarounds: 1. Affected customers can still create new AI Agents directly from a scenario canvas. In order to create a new agent, create a new scenario, add the Make AI Agents -> Run an...

3. monitoring 2025-11-07 20:16 UTC

   AI agents are now again accessible from the UI for all customers. We are monitoring the situation before the incident will be concluded.

4. resolved 2025-11-07 20:37 UTC

   We confirmed that the issues has been fully resolved.

Excerpts are shortened. Read the full incident on Make's status page.