---
title: "CDN location (Help Center / Filters / Geography)"
ai_context: "Use this article for questions about the RUMvision CDN location filter, comparing real-user performance by CDN or edge location and identifying regional delivery differences. It explains that the dimension represents the CDN or edge server location involved in serving the HTML document, becomes available based on the configured Tech stack and exposed CDN information, and can help reveal location-specific differences in TTFB and server response behavior. Relevant for questions about CDN regions, edge locations, cache hit ratio, origin routing, network latency, regional TTFB differences, non-European versus European delivery performance, CDN configuration and diagnosing whether slower requests are linked to a specific serving location."
canonical: "https://www.rumvision.com/help-center/filters/geography/cdn-location/"
---

Breadcrumbs: [Home](https://www.rumvision.com/?format=md) > [Help Center](https://www.rumvision.com/help-center/?format=md) > [Filters](https://www.rumvision.com/help-center/filters/?format=md) > [Geography](https://www.rumvision.com/help-center/filters/geography/?format=md) > CDN location

# CDN location

The CDN location dimension allows you to segment performance data by the CDN location that served the HTML document. The reported value represents the location of the CDN or edge server that was last involved in delivering the page response to the visitor.

> This dimension becomes available depending on [your domain's Tech stack settings](https://www.rumvision.com/help-center/settings/domain/techstack/?format=md) and the CDN information exposed by your configured provider.

Many websites use a CDN as part of their hosting or ecommerce platform, while others configure one separately for performance, caching or security. Comparing performance by CDN location can help reveal regional differences in request handling and delivery.

If you are comparing CDN providers or their global network coverage, [CDN Planet](https://www.cdnplanet.com/) provides an overview of providers, locations and available services.

## Use-case

Slow server responses can originate from several parts of the delivery chain, including your application, hosting infrastructure, caching layer, CDN or the network distance between the visitor and the serving location.

Filtering by CDN location can help identify whether certain edge locations consistently show higher TTFB or other server-side delays. When one location performs noticeably worse than others, this can point towards differences in latency, cache hit ratio, origin routing or regional CDN configuration.

## Example

In the example below, the overall [TTFB](https://www.rumvision.com/help-center/glossary/metrics/time-to-first-byte/?format=md) is 1265ms, but the results vary considerably between CDN locations. Locations outside Europe show higher TTFB than the rest.

This does not identify the exact cause by itself, but it provides a useful starting point for investigating regional latency, cache effectiveness and how often requests from a specific CDN location need to reach the origin.

[![TTFB grouped by CDN location](https://www.rumvision.com/file/upload/img/user-guide/ttfb-by-cdn-location.png)](https://www.rumvision.com/file/upload/img/user-guide/ttfb-by-cdn-location.png)