zapier-dev-files.s3.amazonaws.com is tagged as "dangerous site" by Google

What to do

• Check whether you use Zapier in us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 2d 19h it lasted.

  Anything that failed between 2026-10-09 17:07 UTC and 2026-10-12 13:04 UTC may need a replay.

• Subscribe to Zapier's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=zapier works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Zapier 6

1. investigatingOct 9, 2026, 5:07 PM UTC

   We are investigating an issue where file links hosted on Zapier’s file storage (`zapier-dev-files.s3.amazonaws.com`) may be blocked or show a security warning because the domain has been flagged in Google Safe Browsing. What’s affected • Opening or downloading files from Zapier Forms and Tables when the browser or client enforces Google Safe Browsing • Other flows that open the same file URLs in the browser may see the same warning or block What’s still working • Zaps continue to run, and server-side access to files is not affected by this flag in the same way Customer impact • Multiple customers have reported being unable to open file links; we're still assessing the total scope. We're working with our Security team on the Google flag and mitigation. We will provide another update by 10:53 AM PT / 5:53 PM UTC. If you need help, contact Support: [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help")

   provider

2. investigatingOct 9, 2026, 7:06 PM UTC

   Our Security team continues to work to mitigate the issue and has reached out to Google's team for help resolving the "dangerous site" flag when opening files hosted on Zapier storage while Chrome's Safe Browsing is enabled. This issue primarily affects Tables and Forms users, but any workflow where users open a Zapier-hosted file in the browser can run into it. We'll continue to keep you up to date on our progress and hope to have another update within 2 hours. If you need assistance, please reach out to our Support team at [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help")

   provider

3. investigatingOct 9, 2026, 9:20 PM UTC

   Our team is continuing to investigate the "dangerous site" flag when opening files hosted on Zapier storage while Chrome's Safe Browsing is enabled. We are awaiting confirmation from Google that the issue is remediated. Users of Tables and Forms are the most likely to run into this, but it can happen anywhere a Zapier-hosted file is opened in the browser. We'll continue to keep you up to date on our progress. If you need assistance, please reach out to our Support team at [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help")

   provider

4. identifiedOct 10, 2026, 3:16 AM UTC

   We have received information from Google about the "dangerous site" flag on our file storage domain, and our Security team is now removing the files Google identified as dangerous to restore access. Once this cleanup is complete, we will work with Google to have the flag reviewed and lifted. We will update this page as soon as there is progress. Until then, you may still see a security warning when opening Zapier-hosted files in your browser. Zaps continue to run, and server-side file access isn't affected in the same way. If you need assistance, please reach out to our Support team at [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help")

   provider

5. identifiedOct 10, 2026, 3:50 AM UTC

   We've completed the initial cleanup and are now collaborating with the Google team to determine the next steps needed to clear the "dangerous site" flag on our file storage domain. During this period, your files that passed through Zapier remain safe, and Zaps, Tables, and Forms are functioning normally. Files passing through Zapier work normally on the system side as well. However, when opening a Zapier-hosted file link directly in your browser, you may still see the "dangerous site" warning until Google lifts the flag. We'll update this page as soon as we have news about when this flag will be removed. If you need assistance, please reach out to our Support team at [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help")

   provider

6. resolvedOct 12, 2026, 1:04 PM UTC

   We have worked with Google, and we can confirm this issue is now resolved. Files passing through Zapier worked normally during this time, and were safe to download. The file links are no longer being incorrectly flagged as a dangerous site. Thank you for your patience while we worked through this! If you need support, you can reach us at zapier.com/get-help.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.