Vercel renames Edge Requests to CDN Requests across dashboards, invoices and API

What changed

Vercel has renamed one of its core usage metrics: the figure previously reported and billed as Edge Requests will now appear as CDN Requests. According to a changelog entry on the Vercel blog dated September 30, the change is a rebrand and nothing more — pricing, plan limits, and how usage is measured all stay exactly as they were.

The reasoning behind the new label, Vercel says, is accuracy. These are requests served by Vercel's CDN, and the new name is meant to make that explicit rather than implying a separate "edge" product tier.

Where the new name appears

The CDN Requests terminology now shows up in four customer-facing places:

• the usage dashboard
• the Observability Events chart
• usage notifications
• invoice line items

For most users, that makes the change cosmetic: the next invoice and the next look at the usage dashboard will read slightly differently, with no difference in the numbers themselves.

What is not affected

Vercel is explicit that nothing about the metering changes. Pricing for the metric, the limits attached to it, and the way usage is counted are all unchanged, so nobody should see a cost shift as a result of this rename.

Behind the scenes, metric IDs and product aliases are also untouched. Vercel notes that saved queries keep working, so teams with existing monitoring or analytics queries built on those identifiers do not need to rewrite anything.

The one real change: the billing API

There is a single behavioral change buried in the announcement, and it matters to anyone building against Vercel's billing surfaces. In the billing charges API, the ServiceName field now returns the new name — CDN Requests — instead of Edge Requests.

Vercel's recommendation is that integrations which match charges on ServiceName should switch to the SkuId field instead, because SkuId is designed to remain stable across renames like this one. Any internal tool, chargeback script, or finance automation that string-matches ServiceName against the old "Edge Requests" value will stop matching once the new name propagates, and the failure mode is likely to be quiet: rows simply won't be categorized, rather than throwing an obvious error.

Vercel points readers to its CDN pricing and usage documentation for further detail.

Why it matters

Renamed billing line items are a small change with a long tail. The visible part — a new label on dashboards and invoices — is trivial, but the invisible part is the lesson: human-readable names in billing APIs are not stable contracts, and this rename is a concrete example. Teams that keyed logic on ServiceName now have a broken assumption; teams that already used SkuId have nothing to do.

The practical checklist is short. Check whether anything in your tooling references "Edge Requests" in the context of Vercel billing, and if it does, move that matching over to SkuId so the next rename is a non-event. For everyone else, this is a vocabulary update: same metric, same price, new name.