Make logo

Is Make Down?

SaaSLive status, outages, and incident history

Degraded. Make is up but having problems.

Make is reporting degraded performance as of November 10, 2026. Expect slower responses or more errors. The affected components are listed below.

DegradedChecked just nowLive · every 60s1 active incident

Don't find out like this next time

You searched to find out Make was down. Next time we tell you, usually before your customers do, and always before you think to check.

Free, no password, no card. Unsubscribe in one click.

Official Make status page
How we know: the official Make status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Make Status Summary

As of 04:24 UTC on 10 November 2026, Make is reporting degraded performance. PulsAPI checked Make's official status page and found 29 of 30 components operational, with 1 active incident. Over the last 30 days PulsAPI measured 99.95% uptime for Make, counting degraded performance as up. The latest incident, "Parts of the make.com website unavailable", started on Nov 9, 2026 and is still open.

Cite as: PulsAPI, “Make status”, checked 10 November 2026, 04:24 UTC. https://www.pulsapi.com/services/make

Make Component Status

1 of 30 Make components are impaired. Worst problems listed first.

1partial outage29operational
Website » make.com
Partial Outage
Apps » eu1.make.celonis.com
Operational
Apps » eu1.make.com
Operational

27 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Apps » eu2.make.com, Apps » make.com, Apps » us1.make.celonis.com, Apps » us1.make.com, Apps » us2.make.com, Make Grid, Responsive Webhooks » eu1.make.celonis.com, Responsive Webhooks » eu1.make.com, Responsive Webhooks » eu2.make.com, Responsive Webhooks » us1.make.celonis.com, Responsive Webhooks » us1.make.com, Responsive Webhooks » us2.make.com, and 15 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Make Outages & Incidents

Incident history from the official Make status page, including resolution updates.

Parts of the make.com website unavailableStarted Nov 9, 2026Investigating

The external provider has resolved the issue and the make.com website, including the homepage, is loading correctly again. Some visitors may briefly still see a blank page until cached content refreshes. We are monitoring the situation and will provide a final update once we have confirmed the fix is stable. --- [2026-11-09T17:42:54.440+01:00] (identified) The issue has been identified and a fix is being implemented. --- [2026-11-09T17:34:25.418+01:00] (investigating) We are investigating an issue with an external provider where some pages of the make.com website, including the homepage (www.make.com), are not loading and show a blank page. Other pages, such as make.com/integrations, as well as the Make platform and scenario executions, are not affected. We will provide an update within the next hour, or sooner if more information is available.

Delayed processing of incoming eventsResolved Nov 2, 2026 · 18h 47mResolved

This incident has been resolved. --- [2026-11-02T14:50:56.453+01:00] (monitoring) The cause has been identified. We have now corrected the issue and are actively monitoring the executions. --- [2026-11-02T14:48:30.357+01:00] (investigating) Today between 12:52 and 13:19 UTC, Make did not process incoming events from apps that use shared webhooks

Failing scenarios with "Scenario" appResolved Oct 12, 2026 · 1h 5mResolved

This incident has been resolved. --- [2026-10-12T10:36:22.718+02:00] (identified) The issue has been identified and our team is fixing it. Some scenarios may be deactivated; we'll re-enable them. --- [2026-10-12T10:23:43.060+02:00] (investigating) Scenarios with the "Scenario" app (e.g. "Start a scenario", "Run a scenario" or "Return output") are throwing a validation error when the run begins. We are currently investigating the issue.

Make Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Make incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 12100.00% average · 7 days with incidentsNov 10

Going further back: Make uptime by month and every recorded Make outage.

Live Make Outage Reports

Problems reported by engineers using Make. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Make problems reported yet.

Are you seeing Make problems too?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Make

Make publishes a public status page at status.make.com covering 34 components, including eu1.make.com, eu2.make.com and us1.make.com. PulsAPI tracks Make outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured Make uptime at 99.95%. Response times, incident history, and SLA tracking for Make are available on the PulsAPI dashboard.

Make Status FAQ

Is Make down right now?

The verdict at the top of this page comes from the latest poll of the official Make status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Make is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Make recovers.

How do I check Make uptime history?

PulsAPI tracks Make uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.95%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Make changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Make outages?

PulsAPI reads the official Make status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Make components?

Yes. PulsAPI monitors 30 individual Make components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Make goes down?

Yes. Create a free account and subscribe to Make: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Make to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Make problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Make?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Make plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Make with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services