Vercel says it has cut the slow tail of one of its CDN routing operations by changing how edge metadata is fetched and cached for large deployments.

In a September 10 engineering post, the company said every request through its CDN depends on metadata lookups that help determine which paths exist and how a route should be served. Vercel said the platform previously fetched and cached that metadata one path at a time. That approach became costly for large sites with hundreds of thousands of paths, especially after frequent deployments introduced fresh metadata and new cache misses.

The company says production experiments led it to group related path metadata so one fetch could populate cache entries for many later lookups. According to Vercel, the change reduced P99 metadata lookup latency by 91% and also made deployments faster.

For site operators, the update is a reminder that CDN performance is not only about bandwidth or geographic coverage. Framework-aware platforms increasingly make routing, build output, and edge metadata part of the request path. When those internal control-plane lookups slow down, large sites can see latency even before application code runs.

The announcement is most relevant to high-route-count applications, content-heavy sites, and teams that deploy frequently on Vercel. It also gives operators a useful question to ask any managed hosting or edge platform: how quickly does newly deployed routing metadata become available at the edge, and what happens during cache misses?

Source: Vercel engineering: “How we cut CDN metadata lookup latency by 91%”.