Nine days ago I published a post about throttling PubTrivia to Fast 3G, and it contains this sentence:
the throttle profile's 150ms of latency barely registers against a cache hit because the response is already sitting in Frankfurt
I had measured the time to first byte, seen 20 to 27 ms, and filled in the geography myself. This week I actually read the routing header, and it does not say Frankfurt. It says Frankfurt and then Washington, on every single page we serve.
The header
Vercel puts a route record in x-vercel-id . It has either two fields or three:
$ curl -sI https://pub-trivia.app/robots.txt | grep -i x-vercel-id x-vercel-id: fra1::l7q47-1794480117345-9116948a70f0
$ curl -sI https://pub-trivia.app/faq | grep -i x-vercel-id x-vercel-id: fra1::iad1::7t9xq-1794480117086-4132f34336c8
Enter fullscreen mode
Exit fullscreen mode
fra1 is Frankfurt, which is where my request lands, and it is in both. iad1 is Washington DC, and it is in the second one.…