# Clients blocked by persistent actions now receive a 403 Forbidden response

By Steven Van · 2025-01-28

Vercel WAF persistent actions now return an explicit 403 instead of a silent failure, so an intentional block is easy to tell apart from an error.

Clients blocked by a persistent action in the [Vercel](<https://creatorstoolbox.com/tools/vercel>) Web Application Firewall (WAF) now get a 403 Forbidden response. Before, the block failed silently. The change [took effect on 28 January 2025](<https://vercel.com/changelog/clients-blocked-by-persistent-actions-now-receive-a-403-forbidden-response>).

The status code makes it clear that the connection is being intentionally denied. Persistent actions in the WAF help reduce edge request load and stop malicious traffic earlier, which cuts down unnecessary processing for your applications.

![Vercel](<https://www.google.com/s2/favicons?domain=vercel.com&sz=128>)

Vercel

The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config.

[View Vercel →](<https://creatorstoolbox.com/tools/vercel>)

[Original source](<https://vercel.com/changelog/clients-blocked-by-persistent-actions-now-receive-a-403-forbidden-response>)

[Read Clients blocked by persistent actions now receive a 403 Forbidden response on Creators Toolbox](<https://creatorstoolbox.com/blog/vercel-clients-blocked-by-persistent-actions-now-receive-a-403-forbidden-resp>)

---
Canonical source: https://creatorstoolbox.com/blog/vercel-clients-blocked-by-persistent-actions-now-receive-a-403-forbidden-resp