Why Is the Traffic Usage in a Traffic Package Different from That Shown in Data Analysis?

Possible causes:

1. There is an approximately one-hour delay in the traffic data displayed on the Data Analysis page, while usage deductions from your traffic package are delayed by about four hours. Due to this timing difference, the traffic displayed on the Data Analysis page may be higher than the amount deducted from the traffic package.
   Assume that 20 MB of traffic is consumed from 12:00:00 to 13:00:00.

   • The usage is deducted from your traffic package at 17:00:00.
   • It is reflected on the Data Analysis page at 14:00:00.

     Therefore, when the 20 MB appears on the Data Analysis page, it has not yet been deducted from the traffic package, resulting in a temporary discrepancy.

     

     If you are billed by traffic on a pay-per-use basis, the traffic usage shown on the Data Analysis page may also differ from your real-time billing records due to this same timing delay.

2. The Data Analysis page displays the logged traffic statistics of acceleration domain names. These statistics are obtained from logs at the application level. However, the billable traffic (the actual network traffic) is 7% to 15% higher than the displayed statistics on the Data Analysis page because TCP/IP packet headers and TCP retransmissions also need to be counted in. Therefore, the billable traffic will be typically 10% higher than the statistics displayed on the console. As a result, the used traffic in the traffic package is higher than that displayed on the Data Analysis page.