FAQs

A CDN provides high availability to web applications, scalability to handle high traffic loads, savings in infrastructure and accelerating the delivery of content, which results in an increase in the number of page views to a website, rate reduction drop and increased depth of visits, leading to increased conversion rates and user satisfaction.

When a user performs a first request to our network, we made a new request to the origin and send back the response to the user, storing the object in cache to be used in subsequent requests, allowing faster file transfer to other users. HTTP caching in our network of geographically distributed nodes reduces the distance between your users and your web resources. Because of this and while avoiding the generation of dynamic content for each request, web site response time is reduced significantly and greatly improves the speed of static object delivery.

A CDN is a distributed cache in which elements of a web site are stored for some time, after which they are removed from cache to be obtained later by users requests. Entire website is not transferred, so the use of resources is optimized. To operate a CDN, it requires a source or origin to fetch the requested web content. An ordinary hosting is a source to which users connect directly to obtain content. Scaling this type of service is complicated and expensive by the need of having to support underutilized infrastructure for any unexpected load. Using a CDN takes advantage of its own global network to scale on demand if necessary.

No, a CDN does not replace a hosting. The service will use as a source any existing hosting provider to fetch content for distribution to end users.

Of course. All website regardless of size can get the same benefits when using our services. By providing faster response times to end users, it provides a better experience, while also differentiate your website over your competition.

Our service is 100% provided by us, without intermediaries, with local support in Mexico. We create our own content distribution network (CDN) based on a high-performance architecture in the cloud. We use the latest technology to achieve a guaranteed acceleration of web applications.

Our service is compatible with any type of website, web application or mobile application that communicates via HTTP through ports 80 and 443, either static or dynamic content.

Yes, we work on HTTPS over port 443.

Our CDN can protect a website against DDoS attacks by spreading the burden of attack to our global network. Furthermore, it is not necessary to develop a DDoS protection system, as this solution is implemented by default in our CDN.

No, we work under pay-as-you-go, without contracts.

We provide no-cost trial period during which information is gathered how much traffic is generated and how much it would cost per month. To get an idea, you can multiply the number of monthly page views of a website by an average weight Bytes of Web pages that make up the site. During the test you can clearly measure the improvement in the response time of the site.

Generally it is not required to make changes to source code, except in extraordinary cases. Most websites can use our service transparently.

Yes, with a simple change of the DNS CNAME settings we can accelerate entire websites with static and dynamic content.

We guarantee an availability of 99.95% through our SLA.

Nothing, the service will not be interrupted. Our network is decentralized so that we can lose a full point of presence and the content will be distributed by other points of presence.

Our global network consists of multiple connections with speeds of up to 10Gbps. The speed of downloading content depends on the connection speed of the end user.

Yes, we can extend our reach virtually to everywere in the world at the request of our customers.

Yes, you can configure subdomains partially to test the acceleration of a website. By local changes, you can test the entire website.

No. Our CDN keep a copy of all content requested by end users for some time, but if the source is still unavailable, the distribution of content cannot continue.

Using various techniques, it is possible to store in cache certain type of dynamic content. See: Caching

Yes it's posible. By DNS configuration is possible to point "A" records to public IPs of our points of presence in a region, which will serve as a second layer of cache and a shield providing additional protection.

The service uses our network globally. Files are stored in locations where end-user requests are received.

From our console you can define rules which states how long it should be stored each type of content.

Purging content is performed in real time (milliseconds) from the console or using our API.

Changes made from the console can be seen reflected in a few minutes (10-15 minutes).

Yes, because customers has the control of DNS configurations. While the service is not used, no charge will be generated since we only charge according to data being transferred through our network. The service can be canceled by request via email or can be left idle for the required time.