Is Make Down? How to Tell and What to Do

Is Make Down? How to Tell and What to Do

Make (formerly Integromat) is the automation backbone for thousands of businesses — connecting CRMs, support tools, eCommerce platforms, and internal databases through visual workflow scenarios. When Make goes down, those scenarios stop executing silently. Webhook triggers miss events, scheduled scenarios skip runs, and data that was supposed to flow between apps simply disappears into a gap.

The fastest way to know: Statusfield monitors Make continuously and alerts you within minutes. Without monitoring, you find out about a Make outage hours later when you notice a Slack notification that should have fired didn't — or when a customer reports their order wasn't processed.

---

Common Signs of a Make Outage

Symptom	What's likely happening
Scenarios not executing on schedule	Scheduler is degraded
Webhooks not triggering scenarios	Webhook ingestion layer is down
Scenario runs showing as "failed" in history	Execution engine is erroring
Make dashboard not loading	Web application is degraded
Operations count not updating	Metrics pipeline is affected
Module connections returning errors	Integration API layer is degraded
Data not flowing between connected apps	Execution or routing is failing

---

How to Confirm It's Make, Not Your Scenario

1. Check your scenario run history

In the Make dashboard, look at the run history for your most active scenarios. If multiple unrelated scenarios all stopped executing at the same time, the issue is with Make's infrastructure — not a misconfiguration in your scenario logic.

2. Send a test webhook

If you have a webhook-triggered scenario, send a test event manually (using a tool like Postman or curl). If Make's webhook URL doesn't respond or shows a connection error, the ingestion layer is down.

3. Manually trigger a simple scenario

Pick a minimal test scenario with one or two modules and trigger it manually. If it fails immediately with a generic execution error, the core execution engine is degraded — not something specific to your complex workflows.

4. Check connection status for a core module

Open any module in your scenario editor and check its connection status. If connections that were working yesterday are now showing as invalid or timing out, it's likely Make's integration layer — not your OAuth tokens.

---

The Problem With Vendor Status Pages

Make's status page is updated by their team when incidents are confirmed — but the pipeline between "something is broken" and "we've confirmed an incident" can easily be 20-40 minutes. During that gap, your scheduled scenarios are silently skipping and webhooks are quietly dropping.

The most dangerous failure is the invisible one: no errors surface in your monitoring because Make never received the webhook or never attempted the scheduled run — the event is simply lost.

Statusfield detects Make degradations the moment they start — before the status page acknowledges the incident. Track Make's live status at statusfield.com/services/make.

---

What to Do During a Make Outage

Immediate (first 5 minutes)

1. Identify the failure mode — check whether scheduled scenarios, webhook-triggered scenarios, or both are affected. Schedulers and webhook ingestion are separate systems.
2. Check your run history — note the exact time runs stopped. This is the timestamp you'll need to identify which data is in the gap.
3. Enable error handlers on critical scenarios — if you haven't already, add error-handler routes to your most important scenarios so that when Make recovers, you can see exactly which operations failed.
4. Identify fallback processes — for critical workflows (like order processing or lead routing), determine if there's a manual fallback you can run while Make is down.

Communication (first 15 minutes)

• Alert any teams that depend on Make-driven automations (sales ops, support ops, finance) so they can run manual processes if needed.
• If Make triggers customer-facing actions (order confirmations, onboarding emails, support ticket routing), notify the relevant customer-facing teams.
• Hold off on campaigns that rely on Make automations to execute follow-up sequences — queuing more events during an outage creates a larger backlog to reconcile.

Recovery

• After Make recovers, check for missed scheduled runs — Make may have skipped runs during the outage window rather than executing them retroactively.
• Replay any webhooks that were lost during the outage. For services that support webhook replay (Stripe, GitHub, etc.), use their dashboards to re-send events from the outage window.
• Audit your operations count to identify the gap in executions, and manually process any business-critical data that didn't flow through during the outage.
• Re-test your most critical scenarios end-to-end before trusting them fully — outages can occasionally leave integration connections in a broken state even after the platform recovers.

---

Make Components and What Each Outage Looks Like

Component	Impact when degraded
Scenario scheduler	Scheduled scenarios don't execute; runs are silently skipped
Webhook ingestion	Incoming webhook events are dropped; triggers never fire
Execution engine	Scenarios fail immediately or mid-run; operations are logged as errors
Integration API layer	Module connections time out or return auth errors
Web application	Dashboard doesn't load; can't edit or monitor scenarios
Operations / metrics pipeline	Run history and operation counts don't update in real time

A webhook ingestion failure is the most dangerous outage type for Make — events are silently dropped rather than queued, which means data loss rather than just delay. Execution engine failures are more visible (failed runs appear in history) but still require manual reconciliation.

---

Monitor Make Before Your Next Scenario Stops Silently

Statusfield monitors Make and 1,700+ other services continuously. When something degrades, you get alerted — not after you notice a Slack message that should have fired didn't, or a customer reports missing an automated email.

Start monitoring free — view plans.

---

FAQ

Is Make down right now?

Statusfield monitors Make continuously and will alert you before a scenario silently stops or a webhook starts dropping events. Check Statusfield for real-time status on the scheduler, webhook ingestion, and execution engine.

Why aren't my Make scenarios executing?

If scheduled and webhook-triggered scenarios both stopped at the same time across multiple workflows, the issue is on Make's infrastructure — not your scenario logic. Monitor with Statusfield to catch it before data starts disappearing into the gap.

How do I get alerted when Make goes down?

Statusfield monitors Make continuously and fires alerts the moment it detects a degradation. Start monitoring free — no credit card required.