Skip to main content
Make

Increased scenario failures — Cloudflare API incident

Degraded Lasted 0m · started · Make's page

Level
confirmed
Worst impact
Degraded
Down Index
8of 100

What to do

  • Check whether your product depends on Make. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

    Anything that failed between 2026-06-12 16:01 UTC and 2026-06-12 13:30 UTC may need a replay.
  • Subscribe to Make's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=make works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Make 1

  1. resolved

    Between 15:30 and 17:27 CEST, some users might experienced an increased number of failed or invalid scenarios on zones EU1, EU2, US1, US2. This was caused by an incident on Cloudflare's side, where their API returned 500 errors affecting request routing through our infrastructure. The issue was fully resolved by 17:27 CEST once Cloudflare restored normal API operation. We apologise for the inconvenience.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-6f40173a88

Is Make still down?

No, this incident was resolved 2026-06-12 13:30 UTC. For Make's live state, see https://down.guide/make.

How long did it last?

0m, from 2026-06-12 16:01 UTC to 2026-06-12 13:30 UTC, by the times Make posted.

What caused it?

Make hasn't published a root cause. If it does, it shows here.

Where does this come from?

Make's official status page, https://status.make.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.