Until recently, most users of private CDN solutions have had unique use cases, requiring flexibility and customizability without the costs and challenges of building from scratch or relying solely on public/commercial CDNs. And in fairness, the features of a private CDN, such as custom PoP placement and custom configuration, aren’t for everyone. After all, commercial CDNs deliver what they promise: efficiency and performance in content delivery at large scale. 

Until they don't.

Origin shield technology isn’t new, and many companies already rely on origin shielding to protect their CDNs from overload.

The Fastly CDN outage on June 8th, which took down a major part of the internet, including popular websites and services, such as Reddit, Spotify, Twitch, Stack Overflow, GitHub, gov.uk, Hulu, HBO Max, Quora, PayPal, Vimeo, Shopify, Stripe, and news outlets CNN, The Guardian, The New York Times, BBC and Financial Times, taught everyone four important things: 

Whether you deploy a single CDN or rely on a multi-CDN strategy, an origin shield is a must-have to reduce the load on the origin, protect it from overload, and safeguard performance and QoE.