- HOSTED OFFICE
- CLOUD INNOVATION
- CLOUD HOSTING
- ADD-ON SERVICES
There are two billing methods available for CDN services: Pay-By-Traffic and Pay-By-Bandwidth.
Users may flexibly switch between the Pay-By-Bandwidth and Pay-By-Traffic billing methods.
The new billing method will take effect from the subsequent billing cycle.
Note: Bandwidth utilization equals actually used traffic (Gbps)/(peak bandwidth (Mbps) x 10.54).
For example, 1 Mbps bandwidth and 100% utilization for an entire day would generate 10.54 Gbps of traffic.
Billing item: Downstream traffic
|Traffic Tier||Asia price (JPY/GB)||Rest of The World price (JPY/GB)|
|0GB - 10TB (inclusive)|
|10TB - 50TB (inclusive)|
|50TB - 100TB (inclusive)|
Billing item: Peak bandwidth
|Peak Bandwidth Tier||Asia Price (JPY/Mbps/day)||Rest of the World Price (JPY/Mbps/day)|
|500 Mbps - 5 Gbps|
CDN is used to speed up files or content delivery on the cloud. When an access request is received, a CDN node passively retrieves the requested content from the origin site, caches a copy of the retrieved content and returns it to the user instantly. Depending on the location of the access request, the CDN node returns the cached content during subsequent requests instead of fetching it from the origin server to accelerate delivery.
A mirror site stores all data locally. So when an access request is made again, the mirror site directly pushes the requested content without going back to the origin ser
The edge nodes of CDN are distributed in multiple areas and maintained by different carriers, and not deployed only on BGP networks. The cache layer is located on the BGP network in Hangzhou. It retrieves resources from the origin site server.
No, Content Delivery Network is not updated in real time.
When a request is made for the first time, it may take longer than subsequent requests. This is because the request travels through two network layers, the CDN edge layer and intermediate layer, to retrieve data from the origin site.
You do not have to modify the origin site to use CDN. However, it is recommended to store static and dynamic resources separately to accelerate content distribution. This can be achieved by putting files in different domains
Content Delivery Network statistics are comprehensive as data is collected based on every logged access request. If a page contains multiple iframe tags, CDN counts those as multiple page views.
You can get deeper insights into the data by using third party tools compatible with our Managed Cloud CDN service such as CNZZ and Google Analytics.
Intermediation managed cloud CDN has an intelligent scheduling system and cache software—both of which work in tandem to accelerate content distribution.
Intermediation managed cloud CDN accelerates the resources under a domain name. For example, if you have the domain xyz.com which maps to a web application containing media content, CDN would cache these files. Next time a request is made for the same file, CDN would retrieve it quickly as it is saved locally.
There is no limit on the bandwidth of nodes and the minimum service capacity of a single node is 20Gbps.
Managed Cloud Content Delivery Network domain acceleration becomes effective within 30 minutes after the domain name is verified.
If the file loading rate is low or access error occurs after CDN acceleration, use the nslookup command and ping the CDN domain to obtain the IP address of the CDN node accessed by the user. You can then do basic troubleshooting and seek information to know the rate of delay and packet loss.
“A record” stands for address and is used to specify an IP address corresponding to a host name (or a domain name).
A CNAME record—a canonical name record—is used to map multiple names to the same CDN server. Generally, it is used on computers that provide both www and mail services.
Yes the our managed cloud CDN accelerates gaming apps. Companies dealing with development of online Android, PC or IOS games can use this for accelerated delivery of content and files.
Yes, our managed cloud CDN’s intelligent scheduling system checks all the ports mapped to the virtual IP address of each node to determine the health status. In case the health check fails, access requests will be diverted to a nearby node.
Ask your Intermediation account manager. we will perform for you the following action.
Intermediation managed cloud CDN can compress files stored on CDN nodes.
For file compression, content must meet the following requirements:
To update a cached file, you should synchronize the content at origin site by version number. However same name updates are not recommended.
If you need to update files with the same name, Ask our dedicated CDN team to submit refresh requests. You can request up to 1,000 refresh requests for the same domain every day. Directory level refresh is also supported.
A small traffic fee is charged even after the CDN service is discontinued for the following reasons: