There were 244 Make outages since January 2025 which are summarized below, including incident details, duration, and resolution information.
Make not working for you?
Make not working for you?
Minor
: Make EU1 history logs display issue disrupts module details
Detected by StatusGator:
Officially acknowledged:
The Make EU1 environment experienced problems displaying history logs, impacting users trying to review module history. It remained possible to open history logs in some cases, but loading a module's detail could hang with infinite loading. Scenario executions were not affected. The incident began at and was categorized as a minor outage affecting the EU1 region.
Major
: Make.com outage hits US and EU endpoints
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(30 minutes)
Make.com web apps experienced an outage affecting six regional endpoints (us1.make.celonis.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, eu1.make.com). Users could not load the Make web app, impacting workflows across regions. The outage lasted about 30 minutes, beginning around and ending around . User reports began around , indicating issues across multiple endpoints rather than a single page.
Minor
: Make login issues cause brief EU1 zone outage
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(10 minutes)
Make experienced a brief login disruption affecting new users, localized to the EU1 zone. Most users could still sign in, but EU1 endpoints experienced a partial outage during the incident. The issue began at and affected seven components across Make's services, including make.com and regional endpoints such as us1.make.celonis.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, and eu1.make.com.
Over the next several minutes, the provider issued three status updates documenting the recovery progress. By , all affected endpoints returned to normal operation and login functionality was restored for all users. The incident lasted roughly 10 minutes and was geographically limited to the EU1 zone, with other regions operating normally.
Minor
: Make.com website briefly affected by minor outage
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(10 minutes)
Make.com experienced a short-lived minor outage that affected the Website / make.com component. The incident began at and was listed as a Minor Service Outage, potentially causing intermittent access or degraded performance for users. The issue was resolved about 10 minutes later, with status returning to normal at . The Make status page published two updates during the incident, describing the degradation and the restoration of service. The outage appeared to be isolated to the Website / make.com component.
Minor
: Make US1 delayed executions impact webhooks and scenario runs
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(1 hour and 10 minutes)
The Make.com US1 zone experienced a minor outage that caused delayed executions and webhook deliveries for two components: Responsive Webhooks (us1.make.com) and Scenario Executions (us1.make.com). Users likely observed webhook delays and slower scenario runs during the incident. The outage began at and was resolved by , lasting roughly 1 hour and 10 minutes.
Minor
: Make webhooks brief outage on us1.make.com
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(5 minutes)
Make's Responsive Webhooks on us1.make.com experienced a brief minor outage starting at and resolved by . The issue affected the Responsive Webhooks component on us1.make.com, with intermittent webhook delivery during the five-minute window before service returned to normal. The official status page labeled the incident as a Minor Service Outage for the Responsive Webhooks / us1.make.com component, and it returned to full operation shortly after the end time. The disruption was localized to this component and did not indicate broader impacts across Make services.
Minor
: Make.com website brief outage on apps.make.com
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(5 minutes)
Make.com experienced a brief outage affecting Website / apps.make.com, resulting in degraded performance and temporary access issues for about 5 minutes. The incident began at and was resolved by . The Make status page recorded a Minor Service Outage for Website / apps.make.com and issued two updates during the window before the service returned to normal, indicating the problem was isolated to this component.
Minor
: Make brief outage hits Website / apps.make.com
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(5 minutes)
Make experienced a brief minor outage affecting Website / apps.make.com. The incident began at when the component transitioned from up to warn, labeled Minor Service Outage, causing intermittent access to Make's website and apps. The issue was resolved by , with the component returning to up. The outage lasted roughly 5 minutes, and the provider issued two updates during the incident.
Minor
: Make Website / help.make.com brief outage
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(5 minutes)
The Make Website / help.make.com component experienced a brief outage affecting access to the Make help portal. The outage began at and was resolved by . The Make status page issued two updates during the incident, first listing a Minor Service Outage for the component and then confirming the service was restored about five minutes later. The incident was short and contained to this single component, with no broader impact on Make services.
Minor
: Make outage affects apps.make.com and help.make.com
Detected by StatusGator:
Officially acknowledged:
Outage ended:
(10 minutes)
The outage began at with apps.make.com entering a degraded state. At the help.make.com site also showed degraded performance while apps.make.com had already returned to normal. The two Website components affected were apps.make.com and help.make.com, and recovery was complete by . The Make status page issued multiple updates during the incident, describing a minor service outage and subsequent restoration.
Overall, the incident was brief, with services restored within minutes and no broader impact indicated beyond the two web components.