Operational Make status
make.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
No sign of a widespread Make problem right now; every source we read is quiet.
confidence: medium Vendor: operational · users: normal · routing: no data.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: eu2.make.com
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 89 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “Issues with Scenario saving and Execution on EU2”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside Make's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.
Who depends on whom
We don't map other services that depend on Make. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Make, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
Any new vendor incident, a jump in user reports above baseline, or trouble at the providers Make may depend on.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Make. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Issues with Scenario saving and Execution on EU2
minor resolved · started · resolved
3 updates
- identified
We are currently investigating an issue affecting the EU2 (eu2.make.com) region. Impacted Services: • Scenario Creation: Users are currently unable to savemodified scenarios. • Manual Execution: Triggering scenarios manually is currently failing. Status: Automated scenario runs are continuing as scheduled, but manual executions and new builds are not working. Our engineering team identified the issue and is working on a fix. We are actively working on a fix and will provide an update within the next 30 minutes, or as soon as more information becomes available. We apologize for the disruption to your workflows.
- identified
We are continuing to work on a fix for this issue.
- resolved
The issue affecting the EU2 (eu2.make.com) region has been fully resolved, and all system operations have returned to normal.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.