Live / Zapier / Incident
Zapier: Assessment of recently reported PHP vulnerabilities
Zapier · zapier.comResolved2026-10-22 14:46 UTC
Public — what happened
Summary
Zapier posted a notice on October 22, 2026 at 14:02 UTC about its review of PHP security vulnerabilities that were publicly reported the day before. The company said it had not found any impact on customers, and that its security and engineering teams were checking for possible exposure in its NodeJS services and elsewhere. Zapier said the assessment was still underway at that point and that it would post further findings, and it marked the notice as resolved at 14:46 UTC.
Timeline
- Started — 2026-10-22 14:02 UTC
- Investigating — 2026-10-22 14:02 UTC
- Resolved — 2026-10-22 14:46 UTC · 44 min 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.