Yes — you can usually tell whether a Vercel deployment is in the US by checking the response headers or the function region, not just the public URL. Vercel’s docs and community reports point to the x-vercel-id header for the request region, and to function-region settings/env vars for serverless code.

Fastest check

Open your site in the browser, then:

  1. Open Developer Tools.
  2. Go to Network.
  3. Reload the page.
  4. Click the main request and inspect Response Headers.
  5. Look for x-vercel-id; the first part often includes the region code, such as fra1 for Frankfurt.

What it means

  • If the header shows a U.S. region code, your request was served from the U.S.
  • If it shows a non-U.S. code like fra1, then it was served elsewhere.
  • Static assets may be served from the edge globally, so they are not a reliable indicator of where the whole app is “hosted.”

For serverless functions

If your app uses Vercel Functions, check the configured region in your project settings or vercel.json. The regions setting applies to functions, and Vercel’s docs also mention region configuration for functions directly.

Practical test

If you want to verify from code, return the x-vercel-id header or inspect AWS_REGION inside the function runtime. Community discussions note both approaches for identifying the execution region.

Simple rule

  • Website files : globally distributed, not tied to one U.S. location.
  • Functions : can be pinned to a region, including U.S. regions, depending on your config.

So the real question is usually not “Is my Vercel site hosted in the US?” but “Which region served this request, and where are my functions running?”

Example

If you see x-vercel-id: ...fra1..., that request came from Frankfurt, not the U.S.

TL;DR: check x-vercel-id in response headers for the actual serving region, and check your Vercel function region settings if you care about server-side execution.