Fastly cache MISS on every request — is shielding configured?

Question

Hi! Running Next.js 15 on Hobby in `europe-west4`. My marketing pages send `Cache-Control: public, s-maxage=3600` \+ `Surrogate-Control: max-age=3600`, but `x-cache` always returns MISS, even on consecutive requests, because each one lands on a different Fastly cache node:

```
Run 1: x-cache: MISS  cache-lhr-egll1980025-LHR
Run 2: x-cache: MISS  cache-lhr-egll1980052-LHR
Run 3: x-cache: MISS  cache-lon420144-LON
...

```

Looks like Fastly is configured without shielding, so every POP hits origin independently. Result: synthetic Lighthouse from cold regions shows LCP 3.3-4.4s vs lab 2.5s, that's killing my Core Web Vitals score and Google search ranking signal.

Two questions:

1. Is Fastly shielding something Railway can enable per-project, or is it tier-gated?
2. If tier-gated, which plan unlocks it?

Domain: `www.whyiq.ai` if it helps to look at responses.

Thanks!