Atomile provides usage statistics across multiple dimensions to meet different analysis needs. These dimensions include Traffic, Bandwidth, Requests, and usage by Region and ISP.

How to Access Usage Statistics

1. Log in to the Atomile Console and select the corresponding product.
2. Click Statistical Analysis > Usage Statistics. You will see three tabs: Bandwidth/Traffic, Requests, and Region & ISP Distribution. Select the tab you want to view.
3. Filter by time range and domain, and then click Query to view the corresponding usage data.
4. In the upper-right corner of the usage chart, you can export detailed data by clicking .

Each tab displays usage data from a different perspective. For more information, refer to the sections below.

Bandwidth/Traffic

The Atomile Console displays the following sections by default.

Overall Trend

This summary chart shows the traffic generated on edge servers, relay servers (mid-tier CDN servers), and during back-to-origin, as well as the bandwidth saving ratio.

When the query time range is less than or equal to one day, the data granularity is 5 minutes. When the query time range is longer than one day, the data granularity changes to 1 hour.

For example, if you select June 1 and the domain atomile.com, the chart displays data at 5-minute intervals. It shows the bandwidth, traffic, and bandwidth saving ratio for the CDN edge servers, relay servers, and back-to-origin traffic on that date. If you select June 1 to June 2, the chart displays hourly data.

Edge

This chart shows the bandwidth and traffic generated on CDN edge servers.

• The default granularity is 5 minutes, which is also the finest granularity available.
• You can manually switch to other granularities.
• Comparative traffic and bandwidth usage across different time periods is supported.

Relay

This chart shows the bandwidth and traffic generated on CDN relay servers.

• The default granularity is 5 minutes.
• You cannot manually switch to other granularities for this chart.

Back-to-Origin

This chart shows the bandwidth and traffic generated during the back-to-origin process on CDN servers.

• The default granularity is 5 minutes, which is also the finest granularity available.
• You can manually switch to other granularities.
• Comparative traffic and bandwidth usage across different time periods is supported.

Bandwidth Saving Ratio

The bandwidth saving ratio helps you understand the value provided by caching.

• Bandwidth Savings: Without a CDN, every end-user request is sent to the origin server, consuming origin bandwidth. With a CDN, cached files can be served directly without returning to the origin, which reduces bandwidth usage on the origin server.

• Bandwidth Saving Ratio: This represents the reduction in back-to-origin bandwidth due to cached responses from the CDN. The calculation formula is:

  (Total Traffic - Back-to-Origin Traffic) / Total Traffic

  where Total Traffic = Edge Traffic.

When the query time range is less than or equal to one day, the data granularity is 5 minutes. When the query time range is longer than one day, the data granularity changes to 1 hour.

Daily Data

Displays the peak bandwidth, peak time, and total traffic for each day within the selected time range.

Bandwidth Saving Ratio Top 10 Domains

Displays the top 10 domains ranked by peak bandwidth saving ratio within the selected time range, along with the peak and average bandwidth saving ratios for each domain.

Requests

The Atomile Console displays the following sections by default.

Overall Trend

This summary chart shows the number of requests on edge servers and back-to-origin, as well as the hit ratio, in a single chart.

When the query time range is less than or equal to one day, the data granularity is 5 minutes. When the query time range is longer than one day, the data granularity changes to 1 hour.

For example, if you select June 1 and the domain atomile.com, the chart displays data at 5-minute intervals. It shows the number of requests on CDN edge servers, back-to-origin requests, and the hit ratio for that domain on that date. If you select June 1 to June 2, the chart displays hourly data.

Edge

This chart shows the number of requests generated on CDN edge servers.

• The default granularity is 5 minutes, which is also the finest granularity available.
• You can manually switch to other granularities.
• You can filter request data by network protocol, such as IPv4 and IPv6.

Back-to-Origin

This chart shows the number of requests generated during the back-to-origin process on CDN servers.

• The default granularity is 5 minutes, which is also the finest granularity available.
• You can manually switch to other granularities.

Hit Ratio

Without a CDN, every end-user request is sent to the origin server. With a CDN, cached files can be served directly without returning to the origin. This is called a cache hit.

The hit ratio is calculated as:

CDN Hit Requests / Total Edge Requests

When the query time range is less than or equal to one day, the data granularity is 5 minutes. When the query time range is longer than one day, the data granularity changes to 1 hour.

Daily Data

Displays the total number of requests for each day within the selected time range.

Hit Ratio Top 10 Domains

Displays the top 10 domains ranked by peak hit ratio within the selected time range, along with the peak and average hit ratios for each domain.

Type Ratio

• Edge PoP Requests: The number of requests received by CDN edge servers from end users.
• Back-to-Origin Requests: The number of requests generated when CDN servers request content from the origin.

The ratio of these two request types helps indicate the CDN cache hit ratio. A lower back-to-origin request ratio generally means a higher cache hit ratio.

Region & ISP Distribution

• Bandwidth/Traffic: After you click Query, the system displays peak bandwidth, peak time, and total traffic by region, sorted in descending order by peak bandwidth.
• Requests: After you click Query, the system displays the number of requests by region and the proportion of total regional requests, sorted in descending order by request count.
• Region: The region refers to the area where the end user is located. You can filter for the region you want to view and then click Query to see the distribution.