Make incident

Multiple zones impacted due to AWS Incident

Major Resolved View vendor source →

Make experienced a major incident on October 20, 2025 affecting eu2.make.com and eu2.make.com and 1 more component, lasting 21h 32m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 10:04 AM UTC
Resolved
Oct 21, 2025, 07:37 AM UTC
Duration
21h 32m
Detected by Pingoru
Oct 20, 2025, 10:04 AM UTC

Affected components

eu2.make.comeu2.make.comeu2.make.comeu2.make.comus1.make.comus1.make.comus1.make.comus1.make.comMake Grid

Update timeline

  1. identified Oct 20, 2025, 10:04 AM UTC

    Due to an incident in Amazon Web Services, Make platform was impacted today from 08:50 CEST. Current Impact: Some scenarios may still experience delays. In addition, certain scenarios connected to third-party services were temporarily disabled due to the AWS impact on those third-party providers as well. Grid: us.grid.make.com is currently not fetching new data due to the ongoing AWS issue. Next Steps: We have identified the cause as an ongoing AWS incident and are monitoring their recovery progress.

  2. identified Oct 20, 2025, 11:55 AM UTC

    We are continuing to work on a fix for this issue.

  3. identified Oct 20, 2025, 01:23 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Oct 20, 2025, 01:37 PM UTC

    Current Impact: All services, including us.grid.make.com and affected third-party connections, have recovered. Next Steps: We are monitoring the platform for any potential residual issues related to the earlier AWS incident.

  5. monitoring Oct 20, 2025, 06:43 PM UTC

    UPDATE: us.grid.make.com - Data fetching for grid services in the US region is temporarily impacted due to an ongoing AWS issue affecting event source mappings. All other components of the Make platform remain fully operational.

  6. monitoring Oct 21, 2025, 05:02 AM UTC

    UPDATE: All services, including us.grid.make.com have recovered. We are monitoring the platform for any potential issues.

  7. resolved Oct 21, 2025, 07:37 AM UTC

    This incident has been resolved.