Is Make (Integromat) down?
Updated Oct 08, 2026 16:36 UTC. StatusBird re-checks Make (Integromat)'s status page every 2 minutes.
- Current state
- Operational
- Changed
- Sep 18, 2026 14:15 UTC
- Held for
- 20 days 2 hours
Make (Integromat) is currently operational as of Oct 08, 2026 16:36 UTC, with no outage reported on its official status page. StatusBird reads Make (Integromat)'s status page every 2 minutes and, on the Pro plan, alerts subscribers by SMS, email, Slack, Teams or Discord within that cycle; the free email alert on this page covers major and critical outages with no account.
Get alerted when Make (Integromat) goes down
Free email alert. No account required.
Make (Integromat) uptime and incident history
30-day uptime, from checks every 2 minutes.
Over the past 90 days StatusBird recorded 0 major or critical Make (Integromat) incidents totalling 0 minutes of downtime, for 100.00% availability and a A+ reliability grade, across 64,656 independent checks. Full history: Make (Integromat) reliability report.
Make (Integromat)'s 90-day uptime of 100.00% is above the Automation category average of 99.96% across the 3 services StatusBird monitors in that category.
Make (Integromat) risk in the next 24 hours
StatusBird's stack risk model puts the chance of any Make (Integromat) degradation in the next 24 hours at 23% (elevated) and the chance of a major or critical outage at 0% (normal). It is scored every 10 minutes from four inputs: how often Make (Integromat) has had an episode over the last 180 days, whether it has had one in the last 24 hours or 7 days, how often its degradations turn into major outages, and whether the infrastructure it runs on is having trouble right now.
- 48 degraded-or-worse episodes in the last 180 days
- no major outages in the last 180 days
Scored Oct 08, 2026 16:36 UTC, and rescored every 10 minutes. Method: how StatusBird measures and scores.
How do I get notified when Make (Integromat) has an outage?
Three options, from free to full coverage. Plan details are as published on StatusBird's pricing page and status.make.com as of October 08, 2026.
- Free email alert on this page. The form above emails you when Make (Integromat) enters a major or critical outage and again when it recovers. No account, no card.
- A StatusBird account. The free plan monitors 1 service with a live dashboard and a day-after incident digest. Pro ($29/month) checks all 84 services every 2 minutes and alerts by SMS, email, Slack, Teams or Discord, with quiet hours and per-service thresholds; Business is $49/month and Agency $99/month. Create a free account.
- Make (Integromat)'s own status page. status.make.com offers the subscription options on status.make.com, where available. It is the official record and worth subscribing to alongside any monitor; it updates when Make (Integromat) confirms an incident.
Full guide: Best downtime alert services for online store owners (2026).
About Make (Integromat)
Visual automation platform for connecting apps and automating workflows. Make outages interrupt the integrations that keep your store's data in sync.
StatusBird monitors Make (Integromat) every 2 minutes, 24 hours a day, 7 days a week. When an outage or degradation is detected, StatusBird sends instant alerts so you can act before your customers notice. The 30-day uptime percentage and incident history above reflect live data from our monitoring network.
Make (Integromat) last five incidents
Every non-operational episode StatusBird measured in the last 90 days, newest first, labelled by the worst status reached. The availability figures above count major and critical outages only.
| Started (UTC) | Ended (UTC) | Duration | Worst status |
|---|---|---|---|
| Sep 18, 2026 12:23 | Sep 18, 2026 14:15 | 1 hour 52 minutes | degraded |
| Sep 09, 2026 16:12 | Sep 09, 2026 17:00 | 48 minutes | degraded |
| Sep 04, 2026 07:47 | Sep 04, 2026 07:49 | 2 minutes | degraded |
| Aug 24, 2026 11:37 | Aug 24, 2026 11:47 | 10 minutes | degraded |
| Aug 18, 2026 14:39 | Aug 18, 2026 14:43 | 4 minutes | degraded |
11 episodes in total over the last 90 days, 0 of them major or critical.
What to do when Make (Integromat) is down
A Make (Integromat) outage is not something you can fix, but how you respond in the first 15 minutes decides how much it costs you. This guide covers confirming the outage, limiting the damage, and keeping customers informed.
How do I confirm Make (Integromat) is actually down?
Check two independent sources before changing anything in your store. First, StatusBird's live Make (Integromat) status page, which is based on independent checks every 2 minutes. Second, Make (Integromat)'s own status page at status.make.com. If the official page still shows green, do not assume you are wrong: vendors often acknowledge incidents well after they start. If both look clean, the problem is more likely your store's configuration or a specific integration.
What does a Make (Integromat) outage look like?
- Scenarios showing no new executions in the Make history
- Orders not appearing in connected systems like your 3PL, ERP, or spreadsheets
- Webhook-based scenarios not triggering on store events
- Make dashboard unreachable or scenarios stuck in queued state
- Backlog of incomplete executions appearing after recovery
What breaks in your store
When Make is down, every scenario stops executing, so the automated handoffs between your store and other systems silently stall. Orders stop flowing to your 3PL or accounting tool, inventory updates stop propagating, and notification and tagging workflows go quiet. Webhook-triggered scenarios are the risk area, since events fired during a full outage may never be received, while scheduled scenarios generally just run late. The damage is often invisible until you notice downstream systems are stale.
For context, Make (Integromat) has had no major incidents in the last 90 days of StatusBird's independent monitoring (100.0% availability), so a real outage is unusual. That makes it easy to mistake one for a problem on your end, which is why confirming first matters.
What to do during the outage
- List your business-critical scenarios, such as order-to-fulfillment sync, and perform those handoffs manually during the outage.
- Export new orders from your store admin and import them into downstream systems by CSV if the gap grows.
- Note the outage start time so you know exactly which window of events to reconcile later.
- After recovery, check each critical scenario's execution history and manually re-run or replay missed events.
- Review incomplete executions in Make and resolve or retry them rather than deleting the backlog.
These steps follow the same logic Google codifies in its Site Reliability Engineering chapter on managing incidents: establish what is actually happening, contain the damage, and communicate clearly while the incident is still running.
Frequently asked questions
Will my Make scenarios automatically catch up on everything they missed?
Partially. Scheduled scenarios resume and process current data, and queued webhook events are often replayed, but events sent while Make's webhook intake was fully down may be lost. Treat the outage window as suspect: reconcile orders and syncs for that period manually rather than trusting the automation caught everything.
How do I know if a Make outage affected my store operations at all?
Check the execution history on your critical scenarios for a gap matching the outage window, then verify the downstream result, for example that every store order from that window exists in your fulfillment or accounting system. If counts match, you were lucky; if not, replay or manually enter the missing records.
After the outage
Once Make (Integromat) recovers, verify the affected workflows end to end rather than trusting the status page. Note the start and end times while they are fresh: if you are on a paid Make (Integromat) plan with an SLA, documented downtime is what a service credit claim is built on. See how to claim SLA credits for the process.
How this data is measured
StatusBird checks Make (Integromat)'s status every 2 minutes, around the clock, independently of the vendor. The availability figure counts major and critical outages only; minor degradation is excluded so numbers are not skewed by vendors that report small blips near-continuously. Grades run from A+ to F. See the live numbers on the Make (Integromat) reliability page and current status on the Make (Integromat) status page, or browse all 84 service grades.
This playbook was published separately until September 2026. It now lives here, alongside the live Make (Integromat) status it applies to.
Make (Integromat) status FAQ
Is Make (Integromat) down right now?
No. Make (Integromat) is operational in StatusBird's independent monitoring. That state began Sep 18, 2026 at 14:15 UTC and has lasted 20 days 2 hours. Last checked Oct 08, 2026 at 16:36 UTC.
How often does Make (Integromat) go down?
StatusBird recorded zero major or critical Make (Integromat) incidents in the last 90 days, at 100.00% availability and a A+ reliability grade. Minor degradation is excluded from that figure.
How long do Make (Integromat) outages usually last?
StatusBird measured no major or critical Make (Integromat) outages in the last 90 days. Counting every non-operational episode, including degraded performance, the average length was 23 hours 54 minutes.
What is the chance Make (Integromat) has a problem in the next 24 hours?
StatusBird's stack risk model puts the chance of any Make (Integromat) degradation in the next 24 hours at 23% (elevated) and the chance of a major or critical outage at 0% (normal). It is scored every 10 minutes from four inputs: how often Make (Integromat) has had an episode over the last 180 days, whether it has had one in the last 24 hours or 7 days, how often its degradations turn into major outages, and whether the infrastructure it runs on is having trouble right now.
What should I do when Make (Integromat) goes down?
Confirm the outage is on Make (Integromat)'s side rather than in your store, protect whatever the outage is breaking, and tell affected customers before they find out the hard way. The full step-by-step playbook for a Make (Integromat) outage is on this page, under 'What to do when Make (Integromat) is down'.
How do I get notified when Make (Integromat) goes down?
Use the free email alert form on this page, which needs no account and covers major and critical outages. Or open a StatusBird account: the free plan monitors 1 service with a next-day digest, and Pro at $29 a month checks all 84 services every 2 minutes and alerts by SMS, email, Slack, Teams or Discord, or subscribe to Make (Integromat)'s own status page at status.make.com.
What should I do when Make (Integromat) goes down? The full playbook is on this page.
Related services
Make (Integromat) guides
"Every figure we publish comes from the same 2-minute checks that trigger our customers' alerts. We publish the data exactly as we measured it, and anyone is free to cite it."
Sydney Murphy, founder of StatusBird
Cite this data: StatusBird monitoring data, https://statusbird.io/status/make, accessed October 08, 2026. See the methodology for how these numbers are measured.
Get alerted when Make (Integromat) goes down
StatusBird monitors Make (Integromat) and 83 other services your store depends on. Alerts by SMS, email, Slack, Teams or Discord on Pro.
Get started free