DownForAI

Make (ex-Integromat) status: API, auth, latency & outage reports

Make (ex-Integromat) is operational right now. DownForAI checks Make (ex-Integromat) every ~75 minutes across 1 monitored surface, with 0 community reports in the last 24 hours.

Operational
Last probe 1h ago·1 surface
Official statusHigh confidence
📡 Official status page →📚 Docs →
100.0%
24h Uptime
140ms
p50 Network Latencyⓘ
621ms
p95 Network Latencyⓘ
0
Incidents (30d)

DownForAI monitors Make (ex-Integromat) via a single endpoint — Make Web. Current status: operational — all surfaces are responding normally. Measured uptime over the last 24 hours: 100.0%. Median response time (24 h): 140 ms; p95: 621 ms.

No agent runtime incidents have been tracked for Make (ex-Integromat) since monitoring began, and no community reports were submitted in the last 24 hours. Automated checks continue on the configured schedule.

Data confidence: HighLast checked 1h 17m ago · 1 monitored surface · 1 with 24 h latency data

Current Status

✅
Operational
Everything works normally
✓Checked by our probes · 91ms
Verified 1h ago
✓No major incident reported
ⓘNo reports in the last 24h

Having issues?

Help other users by reporting if Make (ex-Integromat) is not working for you.

0reports in the last 24 hours

Surface Health

Make WebOperational
HTTP 200p50 140ms1h ago

Uptime — last 24h

100.0%

Network latency — last 20 probes

Loading…

What DownForAI can verify about Make (ex-Integromat)

No confirmed provider-side issue detected
DownForAI currently sees Make (ex-Integromat) as operational based on available monitoring signals.
Signal source: official status API · Monitoring confidence: High
Still having trouble?

The issue may be account-specific, regional, network-related, or related to authentication, billing, quota, or rate limits.

Incident history (30d)

✓No incidents recorded in the past 30 days.

Reported symptoms

No user reports for Make (ex-Integromat) in the last 24 hours.

Known error signatures

Common failure patterns and how to diagnose them

Provider details

Make (formerly Integromat) is a visual automation platform with AI modules and agents, running scenarios in Make's cloud on operation-based plans. Its incidents — scenario queues, webhook ingress, specific app modules — are published on an Atlassian status page.

What we monitor
Make scenario runtime — Executions and schedules
Webhooks — Incoming triggers
App modules — Per-app connectors
Ecosystem dependencies
Every connected app

Fallback alternatives

What to use if this service is down

Make is down
Zapier AI, n8n or Activepieces (monitored on DownForAI) run equivalent automations
Major migration

How we monitor

DownForAI checks monitored AI service surfaces on a rotating schedule, roughly every 75 minutes per surface, from a single centralized probe infrastructure. For services with an official machine-readable status page, we use that official status signal when available. For other services, we perform a basic public-surface check. Some services block datacenter probes; in those cases we mark them as “Monitoring limited” instead of treating a failed probe as a confirmed outage. Status is classified as Operational, Degraded, or Outage. Network latency (check response time) measures how long the monitored endpoint took to respond to our probe — it is not model inference speed, time-to-first-token, or tokens-per-second performance. We are independent of all providers listed and receive no compensation to report any particular status.

Make (ex-Integromat) statusEmbed this status badgeREADME · docs ▾
Markdown
[![Make (ex-Integromat) status](https://downforai.com/api/badge/make-ai.svg)](https://downforai.com/make-ai)
HTML
<a href="https://downforai.com/make-ai"><img src="https://downforai.com/api/badge/make-ai.svg" alt="Make (ex-Integromat) status" /></a>

Community Discussion

0/1000
No comments yet. Be the first to share your experience!

Still having issues with Make (ex-Integromat)?

Let the community know and help others experiencing the same problem.