Datvero automation observatory · status.make.com
No. Make's status page reports all systems operational for Make: Scenario Executions, Responsive Webhooks, Apps and 2 other components (checked November 6, 2026, 18:00 UTC; this page refreshes every 15 minutes).
Read from Make's official status API at November 6, 2026, 18:00 UTC. Datvero republishes what Make states; it is not an independent uptime measurement.
From March 29 to November 6, 2026, status.make.com lists 33 incidents: 0 critical, 15 major, 14 minor and 4 with no impact (the vendor's own classification). Median time from first post to resolution, impact incidents only: 2 h. Longest: “LinkedIn* app connections results in "The application is disabled"” (July 7, 2026), 7.3 days. In the last 30 days: 2 incidents, 0 of them major or critical.
| Posted (UTC) | Incident | Impact | Components | Duration |
|---|---|---|---|---|
| Nov 2, 13:48 | Delayed processing of incoming events | minor | eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com | 18.8 h |
| Oct 12, 08:23 | Failing scenarios with "Scenario" app | minor | eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com | 1.1 h |
| Sep 23, 10:30 | Scenario logs in UI not loading | none | 1 min | |
| Sep 18, 12:22 | Degradation on us1.make.celonis.com | major | us1.make.celonis.com, us1.make.celonis.com, us1.make.celonis.com, us1.make.celonis.com | 5.2 h |
| Sep 9, 16:11 | Degradation on EU1 Region | major | eu1.make.com, eu1.make.com, eu1.make.com | 18.3 h |
| Sep 2, 14:00 | Delayed scenario executions on us2.make.com | minor | 1 min | |
| Aug 26, 09:21 | Delay in scenario executions affecting the EU1 (eu1.make.com) | minor | eu1.make.com, eu1.make.com | 1 min |
| Aug 24, 11:36 | Issues with Scenario saving and Execution on EU2 | minor | eu2.make.com, eu2.make.com | 10 min |
| Aug 14, 11:28 | Scenarios disabled | minor | us2.make.com | 51 min |
| Aug 4, 20:43 | Limited availability of the Anthropic & OpenAI models on eu1.make.com and us2.make.com | minor | eu1.make.com, eu1.make.com, us2.make.com, us2.make.com | 5.8 days |
| Jul 30, 10:32 | Scenario executions delayed in eu1.make.celonis.com | minor | eu1.make.celonis.com, eu1.make.celonis.com | 25.3 h |
| Jul 30, 07:55 | Scenarios execution degraded | minor | eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com, make.com | 28.7 h |
| Jul 22, 15:30 | EU1 - Scenarios failing at initialization with "Failed to verify account" error | major | 1 min | |
| Jul 19, 05:58 | US2 - New connection & connection re-authorization resulting in error (SC424) | major | us2.make.com | 26.9 h |
| Jul 17, 14:22 | Login to make.com doesn't work | major | eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com, make.com | 48 min |
Retry with a growing delay, send failures to an error workflow, and get alerted when runs stop succeeding. In n8n, every node has a Retry On Fail setting; Make has Break error handlers that retry incomplete executions; Zapier can replay failed runs with Autoreplay. Datvero watches the runs of your n8n, Make and Zapier workflows and alerts you when they fail, whatever the cause.
No. Make's status page reports all systems operational for Make: Scenario Executions, Responsive Webhooks, Apps and 2 other components (checked November 6, 2026, 18:00 UTC; this page refreshes every 15 minutes).
From March 29 to November 6, 2026, status.make.com lists 33 incidents: 0 critical, 15 major, 14 minor and 4 with no impact (the vendor's own classification). Median time from first post to resolution, impact incidents only: 2 h. Longest: “LinkedIn* app connections results in "The application is disabled"” (July 7, 2026), 7.3 days. In the last 30 days: 2 incidents, 0 of them major or critical.
Make publishes it at https://status.make.com/. This page republishes its public feed every 15 minutes with timestamps. Datvero is not affiliated with Make.
The status page lists what Make has declared. If it is green and you still see errors, read the error code, retry with a growing delay, and check whether the problem is specific to your account, your region or one integration. A green page does not prove that every request to Make succeeds.
Retry with a growing delay, send failures to an error workflow, and get alerted when runs stop succeeding. In n8n, every node has a Retry On Fail setting; Make has Break error handlers that retry incomplete executions; Zapier can replay failed runs with Autoreplay. Datvero watches the runs of your n8n, Make and Zapier workflows and alerts you when they fail, whatever the cause.
Method: Make's public status API (status.make.com/api/v2) is read every 15 minutes by Datvero's collector, which keeps each incident with its official timestamps since August 16, 2026. Durations run from the first post to the resolved post. Machine readable copy: services.json. Official source: https://status.make.com/.
Statuses, incident names and texts belong to Make. Datvero is not affiliated with Make. A green status page does not mean every workflow that calls Make succeeds.