Managed Cloud CDN

Accelerated distribution of any type of content to users across the globe.

Managed Cloud CDN

Scalable and cost-effective content delivery service for accelerated distribution of any type of content to users across the globe. Intermediation Cloud CDN (Content Delivery Network) is a network of multi nodes distributed across the globe to deliver content from your website to end users anywhere in the world.

Through the cloud CDN you can effectively shorten website response times to milliseconds, ensure smooth video streaming and handle large volumes of traffic.

Intermediation Managed Cloud CDN is a low-cost and scalable service, and comes without any long-term contracts or minimum usage commitments. This way you only pay for content delivered through the CDN.

A complete content delivery network architecture

The most common functions associated with the content delivery network include file accessibility, application processing, multimedia delivery and caching. A content delivery network has the same importance as that of a Web Hosting package that you select for your website.

Go Global With CDN

Content delivery network has transformed the way in which data is transferred across multiple locations. A content delivery network has the same importance as that of a Web Hosting package that you select for your website.

What is a CDN?

CDN is short for Content Delivery Network which is a network of servers that deliver cached static content from websites to users based on the geographic location of the user. Pretty confusing eh? Let’s break it down in simpler words.

Normally when a user comes to your blog, they are redirected to your web host’s server (i.e
Your web host’s server is located at a central location i.e Tokyo, Japan. So every user on your website is accessing this one server to view your website.

Now if you have high volume of traffic, then you can overload your server which leads to a slow loading site or even server crash.

This is where a CDN comes in handy because it is a network of servers, but most importantly these servers are spread through out the world.

When you use a CDN, your static content is cached and stored on all of these servers.

Static content includes images, stylesheets (css files), javascripts, Flash, etc.

Now when a user visits your site (original server), the CDN technology redirects them to the closest server to their location.

For example: If your main server is hosted in Tokyo, Japan, and someone from Hong Kong, tries to access it, then they will be redirected to the closest server which may be in Honk Kong. This limits the number of internet hops needed to transmit the static files to your end user.

User’s proximity to your web server has an impact on load time.

By deploying your content across multiple geographically dispersed servers, you can make your pages load faster from the user’s perspective.

This is when CDN comes in handy. In simple words, the closer the CDN server is to where your user is, the faster the user gets the content.

Benefits of our managed CDN



  • Using simple custom configuration options, Managed Cloud CDN allows to add, delete, modify and search query domain names on your own.
  • Supports customizing anti-leech measures, cache policies, HTTP request headers, and other functions.

Auto scaling

  • Provides flexible features like auto scaling.
  • Website traffic spikes are handled automatically.
  • Reduces load on origin site.

Content Delivery

  • Intermediation Managed Cloud CDN service has multi CDN servers or nodes located in Asia and across the globe.

Cost Effective

  • Pay only for what resources you use.
  • No long-term contract or minimum usage.
  • Easy Payment Methods

Massive Storage

  • Supports a massive storage capacity of up to 1.5PB.

Very Fast

  • Enables website response time in milliseconds.
  • Ensures smooth video streaming.

Managed CDN Pricing

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.


Users are billed by daily peak bandwidth. A peak bandwidth value is recorded at intervals of 5 minutes for a total of 288 values a day. The highest value is used for billing purposes. This billing method is applicable to scenarios where the domain name traffic curve is relatively flat or where bandwidth utilization exceeds a daily rate of 30%.


Users are billed according to the actual traffic used and calculated on an hourly basis. This billing method is applicable to scenarios where the domain name traffic curve has substantial fluctuations and bandwidth spikes or where the bandwidth utilization is less than 30% for the day

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.

Description of “Pay-By-Traffic”

Billing item: Downstream traffic

Traffic TierAsia price (JPY/GB)Rest of The World price (JPY/GB)
0GB - 10TB (inclusive)
10TB - 50TB (inclusive)
50TB - 100TB (inclusive)
> 100TB

Description of “Pay-By-Bandwidth”

Billing item: Peak bandwidth

Peak Bandwidth TierAsia Price (JPY/Mbps/day)Rest of the World Price (JPY/Mbps/day)
0-500 Mbps
500 Mbps - 5 Gbps
> 5Gbps


In the case of Pay-By-Bandwidth, the default upper limit bandwidth is 100 Gbps. Please contact us if you require a higher limit.


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 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.

TTL in our managed cloud CDN is the duration of the cached objects/files. You can customize the TTLs for various objects like JavaScript, Images, and CSS according to your needs. For example, you can set a TTL of 60 seconds for a JavaScript file.

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.

  • Change the CNAME of your domain to the address of your A record
  • Direct the CNAME to your origin site
  • Stop the CDN service through our CDN console.

Intermediation managed cloud CDN can compress files stored on CDN nodes.

For file compression, content must meet the following requirements:

  • The content retrieved from the origin site should be greater than 1,024 bytes.
  • The files to be compressed must be in the following formats: content-type: text/xml, text/plain, text/css, application/javascript, application/x-javascript, application/rss+xml, text/javascript, image/tiff, and image/svg+xml.

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:

  • The local DNS server has a cache and if the cache has not expired, the DNS will continue to direct requests to the CDN node. This will produce a small CDN traffic fee.
  • Some software that can be downloaded also has local DNS caches. A suspended CDN domain may produce a small CDN traffic fee until the cache expires.

Need more information about our managed cloud CDN service ? Please contact your Intermediation CDN Assistant Manager we will be glad to help you

the only way to predict the future is…to create it !