Is Make.com Down Right Now?
Make.com (formerly Integromat) status guide — check scenario execution, webhooks, and automation pipeline health. Troubleshooting when Make workflows stop running.
📡 Monitor your APIs — know when they go down before your users do
Better Stack checks uptime every 30 seconds with instant Slack, email & SMS alerts. Free tier available.
Affiliate link — we may earn a commission at no extra cost to you
Check Make.com Status
Make.com Services & Components
Make.com is a distributed platform — individual services can degrade independently. Identify which component is affected:
Runs all Make scenarios on schedule or trigger
Receives and processes incoming webhook triggers
Visual scenario builder and management interface
OAuth connections to third-party apps
Make's built-in database for scenario data persistence
REST API for programmatic scenario management
Cron-based scheduling for timed scenarios
Team workspaces, roles, and billing management
Troubleshooting: Scenario Not Running
1. Check status.make.com for incidents
Always start here. Status.make.com shows real-time health for all Make subsystems. If there's an active incident affecting scenario execution or webhooks, individual debugging won't help — wait for the incident to resolve.
2. Check scenario execution logs
Open your scenario → click the "Execution history" tab. Each execution shows status (success/warning/error) with detailed logs per module. Error messages like "401 Unauthorized" indicate authentication issues; "429 Too Many Requests" means rate limiting from the connected app.
3. Verify scenario is active
Scenarios must be turned on (active toggle) to run automatically. Go to your scenarios list — active scenarios show a green toggle. Scheduling-based scenarios also need a valid schedule set. If using a webhook trigger, the scenario must be active to receive data.
4. Re-authorize module connections
Module connections expire. Click into the failing module → click the connection dropdown → choose "Add a connection" or re-authorize the existing one. Google, Slack, and HubSpot connections are most prone to expiration after password changes or security policy updates.
5. Check operations usage
Go to Account → Usage to check remaining operations. On the free plan (1,000 ops/month), a busy scenario can exhaust the limit quickly. Make pauses scenarios when the limit is reached. Consider upgrading or optimizing high-frequency scenarios to reduce operation counts.
Understanding Make.com Operations vs Zapier Tasks
Key Difference: How Usage Is Counted
Zapier counts tasks — each successful action step in a Zap uses 1 task. Filters and branching don't count. Make counts operations — every module execution counts, including triggers, filters, and error handlers. A 5-module scenario consumes 5 operations per run regardless of which branch executes.
This means Make is much cheaper at scale for complex workflows (Zapier would count each action separately at a higher per-task price), but you need to account for all module executions when estimating Make costs.
Recent Make.com Outage History
Webhook processing delays in EU region — webhooks received but not processed for ~90 minutes. Scenarios with webhook triggers queued. Eventually processed once the incident resolved.
Scenario scheduling degradation — scheduled scenarios ran late or not at all for ~3 hours. Webhook-triggered scenarios were unaffected. Root cause: scheduler service outage.
Google Workspace module authentication failures. Google changed their OAuth token format; Make required an emergency update. Affected all Google Sheets, Gmail, and Drive module connections.
Make Editor inaccessible for ~45 minutes due to a deployment gone wrong. Existing active scenarios continued running; only the UI was down.
For full incident history, visit status.make.com.
Frequently Asked Questions
Is Make.com down right now?
Check the official Make.com status page at status.make.com for real-time system status. This page shows health for Scenario Execution, Webhooks, the Make Editor, API endpoints, and data stores. Signs Make.com is down: scenarios are not executing, the Make app fails to load, incoming webhooks are not triggering scenarios, or you see "Service Unavailable" errors. You can also subscribe to status updates on the status page for email/SMS outage alerts.
Why is my Make.com scenario not running?
Make.com scenario failures have several common causes: (1) Operations limit reached — Make's free plan includes 1,000 operations/month; check your usage in Account → Usage, (2) Module authentication expired — re-connect the app module in Make, (3) Third-party app outage — the app connected to your scenario may be down (check that app's own status page), (4) Scenario is paused or turned off — check the scenario status toggle, (5) Webhook URL changed — if you cloned or recreated a scenario, the webhook URL is different, (6) Make.com platform incident — check status.make.com.
Why is my Make.com webhook not receiving data?
Make.com webhook issues are most often caused by: (1) Wrong URL in the sending app — copy the webhook URL fresh from the Make scenario trigger module, (2) Scenario is inactive — the webhook only captures data when the scenario is active (turned on), (3) Make.com webhook service is degraded — check status.make.com, (4) IP restrictions — if your sending app restricts outbound IPs, ensure Make.com's IP ranges are allowlisted, (5) Content-Type mismatch — Make webhooks expect JSON by default; ensure the sending app sends Content-Type: application/json.
How is Make.com different from Zapier?
Make.com (formerly Integromat) differs from Zapier in several key ways: Make uses a visual canvas with routers, iterators, and aggregators for complex logic — Zapier uses a simpler linear Zap builder. Make charges by operations (each module execution), while Zapier charges by tasks (each action). Make is significantly cheaper at high volumes: 10,000 operations/month costs ~$9 on Make vs $49+ on Zapier. Make has better error handling with custom retry logic and detailed execution logs. Zapier has more app integrations (7,000+ vs 1,500+) and is easier for non-technical users.
What is the Make.com operations limit?
Make.com operations are the unit of measurement for usage. Each module execution in a scenario consumes one operation. A simple 3-step scenario consumes 3 operations per run. Plans: Free = 1,000 ops/month, Core = 10,000 ops/month ($9), Pro = 10,000 ops/month ($16, with advanced features), Teams = 10,000 ops/month ($29). Additional operations can be purchased. Operations reset monthly on your billing date. If you hit the limit, scenarios pause until the next billing cycle.