Outage recap · Make

Make outage — July 30, 2026

On July 30, 2026, Make had 2 reported incidents on Make's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Scenarios execution degraded

minor
Started
Jul 30, 3:55 AM EDT
Resolved
Jul 31, 8:35 AM EDT
Duration
28h 40m

Make's updates (4)

  1. investigating · Jul 30, 3:55 AM EDT

    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 · Jul 30, 4:54 AM EDT

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

  3. identified · Jul 30, 5:41 AM EDT

    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.

  4. resolved · Jul 31, 8:35 AM EDT

    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.

What our checks recorded

We checked Make 343 times from Make's start time to its resolution, once every five minutes. Every one of them reached Make's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 998 ms, against 916 ms over the 24 hours before. Make posted the incident at Jul 30, 3:55 AM EDT.

Updates are Make's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗

Scenario executions delayed in eu1.make.celonis.com

minor
Started
Jul 30, 6:32 AM EDT
Resolved
Jul 31, 7:51 AM EDT
Duration
25h 19m

Make's updates (4)

  1. investigating · Jul 30, 6:32 AM EDT

    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 · Jul 30, 6:32 AM EDT

    The issue has been identified.

  3. monitoring · Jul 30, 7:19 AM EDT

    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 · Jul 31, 7:51 AM EDT

    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.

What our checks recorded

We checked Make 304 times from Make's start time to its resolution, once every five minutes. Every one of them reached Make's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 998 ms, against 915 ms over the 24 hours before. Make posted the incident at Jul 30, 6:32 AM EDT.

Updates are Make's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗

AIDownCheck is not affiliated with Make. This recap summarizes incidents published on Make's official status page.