Vercel
Releases
Performance
Edge data-fetch route missing preferredRegion
Part of the Edge runtime readiness check · fix arrives as a guide
What it is
An edge route that fetches data sets no preferredRegion.
Why it matters
Edge functions run near the user, which is the point — but if the data lives in one region, a user far from it pays the round trip. Without a preference the placement is effectively arbitrary.
How to fix it
Set preferredRegion to the region hosting your data for data-heavy routes, and leave it unset for genuinely edge-appropriate work that does not call back to a single origin.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.