Live / Zapier / Incident
Zapier: Security updates in progress for third-party software components
Zapier · zapier.comResolved2026-10-27 10:56 UTC
Public — what happened
Summary
Zapier said it was installing security updates to the Node.js software used in parts of its service, following a security release from the Node.js project. The company said it found no customer impact or sign of exploitation and that customers did not need to do anything, though some people might notice brief delays in workflows while updates were applied. Updates from October 22 and 23 said the rollout was progressing and the remaining components were being worked through. Zapier marked the incident resolved on October 27 at 10:56 UTC.
Timeline
- Started — 2026-10-22 15:29 UTC
- Investigating — 2026-10-22 15:29 UTC (2 updates)
- Identified — 2026-10-23 17:33 UTC
- Resolved — 2026-10-27 10:56 UTC · 5 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Zapier against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Zapier: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Zapier report →
More from Zapier
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.