Live / Zapier / Incident
Zapier: zapier-dev-files.s3.amazonaws.com is tagged as "dangerous site" by Google
Zapier · zapier.comResolved2026-10-12 13:04 UTC
Public — what happened
Summary
Zapier said that starting October 9, 2026 at 17:07 UTC, Google Safe Browsing had flagged its file storage domain, so people opening Zapier-hosted file links in a browser could see a security warning or be blocked. The company said Tables and Forms users were most likely to be affected, while Zaps kept running and server-side file access was not hit in the same way. Zapier said Google pointed to specific files it considered dangerous, which its Security team removed before asking Google to review and lift the flag. The incident was marked resolved on October 12.
Timeline
- Started — 2026-10-09 17:07 UTC
- Investigating — 2026-10-09 17:07 UTC (3 updates)
- Identified — 2026-10-10 03:16 UTC (2 updates)
- Resolved — 2026-10-12 13:04 UTC · 3 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 42, 2026, our weekly internet health report.