Vercel
Releases
Performance
Single-region function defaults with a cross-region database
Part of the Deployment posture check · fix arrives as a guide
What it is
Functions are configured for a single region that is not where the database lives.
Why it matters
Every query pays cross-region latency, and it compounds — a handler making four sequential queries pays that round trip four times. It shows up as a slow application with fast-looking individual queries.
How to fix it
Set the function region to match the database's region. Where reads must be global, put a read replica near the functions rather than moving the round trips further apart.
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.