Hi! I'm seeing very high amount of edge requests for some projects on vercel in the observability panel. The majority seems to be against /_next/image and is during build and / or revalidation of data. I'm 100% sure this is not generated by real user requests (the edge requests does not match up against the number of users at all) so I'm trying to figure out what the culprit is and how we should optimize this.

Some notes about our setup:
1) We optimize images with next/image and use absolute remote urls in src. The remote hostname is added to next.config.ts
2) We run nextjs 15, app router and hosting on vercel.
3) Almost all pages (around 1000) are generated as static html with generateStaticParams.
4) Content are fetched, cached and revalidated by SanityLive.

Any suggestions why /_next/image get tons of edge requests during build (or revalidation)? I thought these requests only would fire on user request? Am I missing something?

Is this by design with next/image (and remote sources)?
Or is it most likely something with the sanity / nextjs revalidation?
Or something completely else?

Thank you, all input appreciated