Live  /  Providers  /  Make

Make

make.comNo open incidents

Independent assessment — SquidGrid is not affiliated with Make. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

SaaS & business software · SquidGrid tracks Make’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what Make is reporting

Current & recent incidents

Resolved

Parts of the make.com website unavailable

Major impact · 2026-11-10 08:19 UTC · source

Resolved

Delayed processing of incoming events

Minor impact · 2026-11-03 08:35 UTC · source

Resolved

Failing scenarios with "Scenario" app

Minor impact · 2026-10-12 09:29 UTC · source

Resolved

Degradation on us1.make.celonis.com

Major impact · 2026-09-18 14:14 UTC · source

Resolved

Degradation on EU1 Region

Major impact · 2026-09-09 16:59 UTC · source

Incident titles and states as published by the provider. Times in UTC.

Track record

SquidGrid has archived 5 incidents from Make’s own status page since 2026-09-09.

Recent incidents in the archive

Computed by SquidGrid from the incidents Make published. Their own page shows only recent history; this archive keeps every one.

Independent path health

A status page tells you what Make has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

Make runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of Make is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with Make.