Performance Analytics

Learn how to analyze CDN performance in detail using the Performance Analytics dashboard.

The Performance Analytics dashboard provides an in-depth view of CDN responsiveness and reliability. It allows you to evaluate latency, request times, and cache efficiency across datacenters, countries, and ASNs. By correlating Round Trip Time (RTT), error ratios, and request metrics, you can detect bottlenecks, compare regions, and optimize content delivery performance.

1

Top Metrics

At the top of the dashboard, four indicators summarize CDN activity for the selected time range:

Metric	Description
Total Requests	Total number of requests served.
Total Bytes	Total data transferred through CDN.
Avg Request Time	Average server response time for all requests.
HIT Ratio	Percentage of requests served directly from cache.

Compare Avg Request Time with HIT Ratio — higher cache utilization typically leads to faster response times.

2

Traffic and Resource Analysis

Visualize traffic distribution across resources, countries, and ASNs.

• Requests per Resource (time series): Tracks total requests or data transfer per CDN resource.

• Requests per Country (time series): Displays the top five countries by traffic volume.

• Requests per ASN (time series): Highlights the most active ISPs (Autonomous System Numbers).

Switch the Metric filter from Requests to Bandwidth to analyze traffic volume instead of frequency.

3

Latency and RTT Insights

Measure how quickly CDN edge servers respond to user requests.

• Request Times (time series): Displays overall request duration trends.

• Request Time per Country (time series): Compares latency by user country.

• Request Time per Datacenter (time series): Highlights performance differences across Points of Presence (PoPs).

• Round Trip Time (RTT): Shows average TCP connection time between client and CDN edge.

Combine Country and Datacenter filters to isolate latency issues or identify underperforming PoPs.

Sudden spikes in Request Time per Country may indicate regional ISP routing problems or origin latency increases.

4

Error and Status Analytics

Track error ratios and status code trends.

• 4xx–5xx Ratio (time series): Percentage of client and server errors over time.

• 4xx–5xx Ratio per Datacenter (time series): Breaks down errors by PoP.

• 4xx–5xx Counts (time series): Shows total error responses within the selected range.

• Status Distribution (pie chart): Displays proportional breakdown of all HTTP responses (2xx–5xx).

High error ratios in low-traffic datacenters can appear inflated. Always verify data volume before interpreting

Persistent 5xx errors may indicate upstream (origin) issues or blocked connections between CDN and origin.

Filters

Each visualization updates dynamically based on the selected filters:

Filter	Description
Resource Name	Focus on a specific CDN resource.
Account Type	Filter by CDN account type.
Datacenter	Narrow down data by Point of Presence (PoP).
Country	View metrics for specific user regions.
ASN	Filter by Autonomous System Number.
Status	Select HTTP status codes (2xx–5xx).
HIT Status	Show cache performance by response type (HIT, MISS, etc.).
Metric	Choose metric type: Requests, Data Transferred, or Bandwidth.

Apply multiple filters — for example, Country + Datacenter — to correlate latency or error metrics within specific regions.

FAQ

Q1: What is RTT and how is it measured? RTT (Round Trip Time) represents the time between a user’s request and the CDN’s first response. It measures TCP-level latency between the client and the edge server.

Q2: Why are some charts empty after applying filters? Certain datasets may not contain results for selected filters (e.g., no traffic for a specific ASN or datacenter in that period). Try broadening the date range or removing filters.

Q3: Can I correlate cache ratio with latency? Yes. A higher HIT ratio typically lowers average request time since cached content is served directly from the nearest edge location.