We started checking Make on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Make reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Make's own status page declared. Below it, any public chatter we saw about Make and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Make's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, auth (primary)
Unverified user reportsNo reports about Make in the last 24 hours, which is not evidence that nothing is wrong.
Make's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Make's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Make next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
Bluesky posts35 in the last hour (prior day averaged 29.4/hour)
Mastodon posts1 in the last hour (prior day averaged 0.1/hour)
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
431
US-West
100.00%
333
Europe
100.00%
304
Asia-Pacific
100.00%
185
Their declared record
Make's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Delayed processing of incoming eventsMinor incident
Nov 2, 2026, 1:48 PM UTC to Nov 3, 2026, 8:35 AM UTC (18h 47m)resolved
their latest update (Nov 3, 2026, 8:35 AM UTC): This incident has been resolved.
Failing scenarios with "Scenario" appMinor incident
Oct 12, 2026, 8:23 AM UTC to Oct 12, 2026, 9:29 AM UTC (1h 6m)resolved
their latest update (Oct 12, 2026, 9:29 AM UTC): This incident has been resolved.
Scenario logs in UI not loadingAll systems operational
Sep 23, 2026, 10:30 AM UTC to Sep 23, 2026, 10:30 AM UTC (0 min)resolved
their latest update (Sep 23, 2026, 10:30 AM 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.
Degradation on us1.make.celonis.comPartial outage
Sep 18, 2026, 1:36 PM UTC to Sep 18, 2026, 5:32 PM UTC (3h 56m)resolved
their latest update (Sep 18, 2026, 5:32 PM UTC): This incident has been resolved.
Degradation on EU1 RegionPartial outage
Sep 9, 2026, 4:11 PM UTC to Sep 10, 2026, 10:29 AM UTC (18h 17m)resolved
their latest update (Sep 10, 2026, 10:29 AM UTC): This incident has been resolved.
Delayed scenario executions on us2.make.comMinor incident
Sep 2, 2026, 2:00 PM UTC to Sep 2, 2026, 2:00 PM UTC (0 min)resolved
their latest update (Sep 2, 2026, 2:00 PM 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.
Delay in scenario executions affecting the EU1 (eu1.make.com)Minor incident
Aug 26, 2026, 9:21 AM UTC to Aug 26, 2026, 9:21 AM UTC (0 min)resolved
their latest update (Aug 26, 2026, 9:21 AM 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 inconvenienc…
Issues with Scenario saving and Execution on EU2Minor incident
Aug 24, 2026, 11:36 AM UTC to Aug 24, 2026, 11:46 AM UTC (10 min)resolved
their latest update (Aug 24, 2026, 11:46 AM UTC): The issue affecting the EU2 (eu2.make.com) region has been fully resolved, and all system operations have returned to normal.
Scenarios disabledMinor incident
Aug 14, 2026, 11:28 AM UTC to Aug 14, 2026, 12:19 PM UTC (51 min)resolved
their latest update (Aug 14, 2026, 12:19 PM UTC): This incident has been resolved.
Limited availability of the Anthropic & OpenAI models on eu1.make.com and us2.make.comMinor incident
Aug 4, 2026, 8:43 PM UTC to Aug 10, 2026, 3:10 PM UTC (5d 18h)resolved
their latest update (Aug 10, 2026, 3:10 PM 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.
Showing the 10 most recent of 50 incidents Make has declared in the history we hold.
These entries are Make's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Make's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.