Cache response types

Understanding cache response types can help you gain insight into the effectiveness (or ineffectiveness) of your CDN and your origin server, as well as the relationship between the two. uses 6 cache response types which are viewable in both our real-time logs (we’re working on our real-time logging feature right now, using Elasticsearch) and the Activity screen for each of your configurations:

  • CACHE_HIT – The file was served from cached copy. No hit was made against the origin server. Size recorded will be the size of the file on disk.
  • CACHE_MISS_CACHE – The file was not found in the cache, therefore a request to origin was made and the content was pass-thru streamed to the end user while at the same time cached on Size recorded will be the size in Content-Length header sent by the origin server for the file.
  • CACHE_MISS_EXPIRED – The cache record indicates that the file has gone over the TTL (time-to-live) and has therefore expired. The file will be re-downloaded from origin and pass-thru streamed to the end user. Size recorded will be the size in Content-Length header sent by the origin server for the file.
  • CACHE_MISS_STREAM – The cache record states the file is in “DOWNLOADING” state, probably from a previous “CACHE_MISS_CACHE”. Since the file is already being cached, there is no need to create another cached copy on Since it is still downloading it is not useful to read the incomplete cached copy and send it back to the client. So we hit the origin server for this. Size recorded will be the size in Content-Length header sent by the origin server for the file.
  • CACHE_MISS_SOURCE_FAILED – The cache engine received an error while trying to retrieve the content from origin. This indicates non-HTTP errors while connecting to your origin server. For example, DNS name resolution errors or network connectivity errors.
  • CACHE_MISS_OTHER – The cache engine received an error while trying to retrieve content from origin. This indicates HTTP-related errors while connecting and trying to GET content from your origin server. For example, HTTP 4xx or HTTP 5xx errors.

If your CDN and origin server are configured correctly then the ratio of CACHE_HIT responses to other responses will be as high as possible, thereby translating into a ‘hit ratio’ of (hopefully) 99%+ for static content.

What about dynamic content (or “event driven content” as Fastly more aptly names it) you ask? That’s another story, and we’ll leave that one for the another blog post 😉

When latency matters, RTMP still reigns supreme

If you operate a business with latency-sensitive live streaming as a key component, then you’ll already know that RTMP is still the king of ‘real-time’ live streaming. What do we mean by “latency-sensitive”? Essentially, if your business demands the smallest possible delay between the real-world event which is being filmed by your camera source and the stream which is landing on your customer’s device, then you’re operating in a latency-sensitive live streaming environment.

Some of our existing enterprise CDN customers are able to achieve such low latency that they’re measuring it in milliseconds. And with you’ll have access to the exact same streaming technologies, at a fraction of the price 🙂

We’ll be launching with full RTMP to multi-bitrate HLS support, as well as stream DRM protection via API auth.

So what are you waiting for? Get on over to the home page and put email address down to join the beta release of our Linode CDN. We’re on schedule for launch around beginning of next month. You can also follow on Twitter for regular updates.

We’ll see you soon!

Shared SSL, Hosted SSL, and HTTPS requests will all be free!

Encryption – use it!

We’ll be launching with full SSL support:

  • Shared SSL for those of you wanting to use your config’s subdomain – e.g.
  • Hosted SSL for those of you wanting to upload your own SSL certificate and key and then CNAME your domain to your config’s subdomain – e.g. –>
  • Unlimited HTTPS requests

How much? Free, of course! 🙂 Coming up next, we’ll talk about’s support for HTTP/2. Stay tuned!

Here’s a sneak peek of’s DRM protection

Protection of your content is of paramount importance. supports Digital Rights Management (DRM) for your content via a central authorization server. This method of content protection requires you to have an authorization URL where all requests for protected content must first be authorized.

How It Works

When a client requests protected content over, the path of the file and any HTTP GET query parameters are sent via HTTP POST to the authorization URL configured for the site. If the request is authorized, the authorization server responds with an HTTP 200 response. The content body of the response can optionally contain a JSON object with the correct path for the content on the origin server. Any other response from the authorization server is considered as an authorization failure and the client will receive an HTTP 403 error instead of the requested content.

Head on over to our docs to read more about how’s DRM protection feature works.

We’ve got more awesome features coming soon, like Hotlink Whitelists and customizable cache paths and lifetimes, so stay tuned 🙂

Your Linode CDN is coming soon. Join the beta!

Over the years there have been many rumours, rumblings, and rants about the need for a Linode CDN. Well, after spending a few years in the enterprise content delivery space we came to the conclusion that we might as well do it ourselves. So we did, and is our gift to you. is a high performance CDN powered by Linode’s awesome SSD servers and trusted network partners.

Here’s a sneak peek at what we’re rolling out in the coming weeks:

  • Linode powered edge servers
  • HTTP/2 ready
  • Instant cache purge
  • Free shared SSL and certificate hosting
  • Low latency live streaming and VOD
  • Web Application Firewalls (WAF)
  • Unlimited domains
  • RTMP to multi-bitrate HLS
  • DRM protection via API auth
  • Hotlink whitelists
  • Customizable cache paths
  • Customizable path lifetimes
  • Unlimited origins
  • Detailed reports

Head over to the home page to sign up for the beta. We’ll see you soon 🙂