Make.com Status: How to Check If Make Is Down Right Now (2026)
Where to find the official Make.com status page, what each component tracks, and how to diagnose scenario execution failures, connection errors, and webhook issues.
Is Make.com Down Right Now?
Check status.make.com for official real-time status. Make tracks scenario execution engine, web app, connections, webhooks, and API availability separately.
What Is Make.com?
Make.com (formerly Integromat) is a visual workflow automation platform that connects 1,500+ apps and services. It competes directly with Zapier and n8n, with a focus on complex multi-step automations (called scenarios) that can branch, loop, filter, and transform data between services.
Make is used extensively by marketing teams, agencies, and developers to automate repetitive workflows — syncing CRM data, processing form submissions, triggering notifications, and integrating APIs. When Make is down, those automations stop silently, which can cause data gaps and missed triggers that are hard to detect after the fact.
Make.com Status Page Components
The Make status page at status.make.com tracks these key service components:
Important: Make operates across multiple regions (US, EU). An incident may affect only one region. The status page breaks down incidents by region when relevant — always check the component specific to your account region.
Monitor your Make.com automations independently
Better Stack monitors your Make webhooks and scenario endpoints every 30 seconds. Know when your automation pipeline goes silent before it affects your business.
Try Better Stack Free →How to Check Make.com Status (Step by Step)
Check status.make.com
The official Make status page. Look at the Scenario Execution Engine component first — if that is degraded, your scenarios may fail silently without showing errors in the Make UI.
Go to Make Status Page →Check your scenario execution history
In Make, open the scenario and click the clock icon to view execution history. Each run shows status (success/error/incomplete), operation count, and any error messages with the exact module that failed.
Check your connection status
Go to Make → Connections and check for any connections showing an error state (red icon). Expired OAuth tokens are the most common cause of scenario failures that are not platform outages.
Check Make's Twitter / X
Make posts incident updates on @make_hq. For real-time crowdsourced reports, search "make.com down" or "make.com not working" on Twitter.
Follow @make_hq →Test your webhook manually
If a webhook-triggered scenario is not running, send a test HTTP request to the webhook URL using curl or Postman to confirm the webhook is receiving data.
curl -X POST https://hook.make.com/YOUR_WEBHOOK_ID \
-H "Content-Type: application/json" \
-d '{"test": true}'Contact Make support
If the status page shows no incident but your scenarios are still failing, contact Make support — account-specific issues or regional incidents may not show on the global status page.
Make Support →Common Make.com Issues and Causes
| Symptom | Likely Cause | First Check |
|---|---|---|
| Scenarios not running at scheduled time | Scheduler incident or scenario disabled | status.make.com → Scheduler; verify scenario is ON |
| Webhook not triggering scenario | Webhook service issue or wrong payload | status.make.com → Webhooks; test webhook manually |
| Connection error on module | OAuth token expired or revoked | Make → Connections; re-authorize the connection |
| Scenario runs but no data processed | Filter condition blocking records | Execution history → expand incomplete runs |
| Operations count at 0 all month | Plan reset or operations exhausted | Account → Usage; check operations remaining |
| Make dashboard not loading | Web app incident | status.make.com → Web Application; try different browser |
| Data store not saving values | Data Store service degradation | status.make.com → Data Stores |
| Error notifications not arriving | Email notification service issue or spam filter | status.make.com → Email Notifications; check spam folder |
Make.com vs Zapier: Status Infrastructure
Make.com
- Status: status.make.com
- Formerly Integromat (rebranded 2022)
- Operations-based pricing model
- Strong multi-step scenario branching
- EU-based company (Czech Republic)
Zapier
- Status: status.zapier.com
- Task-based pricing model
- Simpler linear Zap structure
- Larger app ecosystem (6,000+)
- US-based company (San Francisco)
See our Zapier status guide for a full breakdown of Zapier's status infrastructure.
What to Do When Make.com Is Down
Immediate Steps
- Check status.make.com and subscribe to incident updates
- Review execution history to identify which scenarios failed
- For critical workflows, trigger manually if the source app allows
- Enable Make's "Incomplete runs" feature to catch data lost during outage
- Set up error handling in scenarios to catch and log failures
Long-Term Resilience
- Enable "Incomplete runs" in all critical scenarios
- Add error handlers to all Make modules that touch external APIs
- Monitor webhook endpoints independently with Better Stack
- Consider n8n self-hosted as a backup for critical automations
- Regularly re-authorize connections before they expire silently
Monitor your Make.com webhook endpoints independently
Better Stack monitors your Make webhooks and integration endpoints every 30 seconds. Know when your automation pipeline fails before data gaps pile up.
Try Better Stack Free →Frequently Asked Questions
Where is the official Make.com status page?
Make.com's official status page is at status.make.com. It tracks real-time operational status for Make's core services: scenario execution engine, web app, connections/integrations, webhooks, and API. You can subscribe to email or SMS notifications for incident updates directly on the status page.
Why are my Make scenarios not running?
Make scenarios stop running for several reasons: (1) Platform incident — check status.make.com for the Scenario Execution Engine component, (2) Scenario errors — check the scenario's execution history in Make for specific error messages, (3) Operations quota exhausted — you may have hit your monthly operation limit; check your Make plan usage, (4) Connection authorization expired — third-party connections (Google, Slack, etc.) require re-authorization periodically, (5) Webhook not receiving triggers — test the webhook URL manually, (6) Scheduling issue — if your scenario uses a schedule trigger, verify the schedule settings. The Make execution history log is the best first-stop for diagnosing individual scenario failures.
Why is Make.com showing a connection error?
Make connection errors typically mean: (1) The third-party service (Google, Slack, HubSpot, etc.) has revoked Make's OAuth token — re-authorize the connection in Make → Connections, (2) API rate limit hit on the connected service — not a Make outage, but a limit on the destination API, (3) Make's integration module for that service has a known issue — check status.make.com under Connections/Integrations, (4) Your Make account's connection limit has been reached for your plan tier. Go to Make → Connections and check the status of the specific connection showing errors.
What is the difference between Make.com and Integromat?
Make.com and Integromat are the same product. Integromat was the original name of the workflow automation platform; the company rebranded to Make.com in 2022. If you search 'Integromat down' or 'Integromat status', the status page is the same: status.make.com. All legacy Integromat scenarios and connections migrated to the Make platform with no changes needed.
Is Make.com down for everyone or just me?
To check if Make.com is down for everyone or just you: (1) Visit status.make.com — if there's an active incident, it will show there, (2) Check Twitter/X by searching 'make.com down' for real-time reports from other users, (3) Try accessing the Make dashboard from a different browser or device, (4) Check if your specific scenario is failing or all scenarios — widespread failures suggest a platform issue; single scenario failures suggest a connection or logic error specific to your setup.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Make.com goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Make.com + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial