Make logo

Is Make Down?

SaaSLive status, outages, and incident history

No. Make is up right now.

Every monitored Make system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 4m agoLive · 60s while moving

Know the moment Make breaks

Make is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

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

How we know: the official Make status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Make Component Status

The main Make systems on this page. All 30 are operational right now.

30operational
Apps » eu1.make.celonis.com
Operational
Apps » eu1.make.com
Operational
Apps » eu2.make.com
Operational

27 more components tracked

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

Also tracking 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, Scenario Executions » eu1.make.celonis.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.

Scenario logs in UI not loadingResolved Sep 23, 2026 · -59 minResolved

Scenario logs in the UI were not loading. Clicking on logs in scenario history timed out. Fetching logs via API was not impacted. All zones were affected. The issue was already fixed.

Degradation on us1.make.celonis.comResolved Sep 18, 2026 · 5h 10mResolved

This incident has been resolved. --- [2026-09-18T16:14:13.554+02:00] (monitoring) Update: Corrective actions have been applied, and the situation has stabilized. We are actively monitoring the platform to ensure full performance and recovery. We will continue to provide updates as we observe system behavior. --- [2026-09-18T15:36:46.954+02:00] (identified) Investigation still ongoing. We are actively working to isolate the issue and will provide another update shortly. --- [2026-09-18T15:08:23.303+02:00] (identified) Update: Investigation is still ongoing. Our team is actively analyzing the issue to determine the root cause, and we will share further details as soon as more information becomes available. --- [2026-09-18T14:40:50.444+02:00] (identified) Update: We have identified the root cause of the issue and our engineering team is actively working on a resolution. Further updates will be provided as progress is made.. --- [2026-09-18T14:22:05.681+02:00] (investigating) We are investigating an issue affecting the us1.make.celonis.com region. Users may experience instability with scenario executions, webhook processing, and overall platform access. Our engineering team is actively working to restore stability, and we will share another update within the next hour

Degradation on EU1 RegionResolved Sep 9, 2026 · 18h 17mResolved

This incident has been resolved. --- [2026-09-09T18:59:37.335+02:00] (monitoring) Operational metrics on eu1.make.com have returned to healthy levels. While system operations have normalized, our engineering team remains in a monitoring state to verify that performance remains consistent --- [2026-09-09T18:11:54.098+02:00] (investigating) We are investigating an issue affecting the eu1.make.com region. Users may experience instability with scenario executions, webhook processing, and overall platform access. Our engineering team is actively working to restore stability, and we will share another update within the next hour

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 history49 days observed
Aug 8100.00% average · 7 days with incidentsSep 25

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.

Something wrong with Make on your end?

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.97%. 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 a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

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.97%. 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 a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

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

2463+ 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