Live  /  Make  /  Incident

Make: Delayed processing of incoming events

Make · make.comMinor incidentResolved2026-11-03 08:35 UTC
Public — what happened

Summary

Make reported a minor incident in which incoming events from apps that rely on shared webhooks were not processed for a period on 2 November 2026, which the company put between 12:52 and 13:19 UTC. Make said it identified the cause and applied a correction by 13:50 UTC, then watched executions to confirm things were working. The incident was marked resolved on 3 November at 08:35 UTC.

Affected

eu1.make.com, eu2.make.com, us1.make.com, us2.make.com, eu1.make.celonis.com, us1.make.celonis.com

As listed on Make’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Make against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Make: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Make report →

More from Make

Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.

The full archive is on the Make status & history page.

Related: Make status & history. SquidGrid is not affiliated with Make.