Changes / Make / Scenarios execution degraded - eu2.make.com
Make: Major incident: Scenarios execution degraded - eu2.make.com
Summary
Make reported a major degradation on eu2.make.com that could affect scenario executions and credits, starting 2026-05-13 10:49 UTC and resolved at 2026-05-13 18:08 UTC, lasting 7 h 18 min. The vendor identified the cause of zone overload and applied mitigations, reporting the zone operational again at 14:10 UTC.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
Major incidentLabel: degradation (model (Jev), 91%)Changed Detected Source: stspg.io (opens in new tab)
What changed
Before: not present
After: Scenarios execution degraded - eu2.make.com
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-05-13 10:49 UTC
Before: not present
After: 2026-05-13 18:08 UTC
Before: not present
After: eu2.make.com, Scenario Executions - eu2.make.com, Website - eu2.make.com
Before: not present
After: 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.
Before: not present
After: Our engineers are continuing to investigate this issue with highest priority. We will provide a further update within the next hour.
Before: not present
After: We are continuing to investigate this issue.
Before: not present
After: 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
Before: not present
After: This incident has been resolved.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Scenarios execution degraded - eu2.make.com (this change) Make reported a major degradation on eu2.make.com that could affect scenario executions and credits, starting 2026-05-13 10:49 UTC and resolved at 2026-05-13 18:08 UTC, lasting 7 h 18 min. The vendor identified the cause of zone overload and applied mitigations, reporting the zone operational again at 14:10 UTC. | Major incident |