Why Netflix Rarely Goes Down

Netflix serves hundreds of millions of members worldwide, and outages that take the whole service down are rare. That reliability isn't luck. It's the result of a deliberate decision made after one painful failure in 2008, and an engineering culture built around assuming things will break.

(Note: "never" is too strong. Netflix has had outages and live-event problems, like buffering during the 2024 Paul vs Tyson fight. But its everyday streaming is remarkably resilient.)


🎯 Quick Answer (30-Second Read)

  • 2008 wake-up call: a database corruption stopped Netflix shipping DVDs for three days.
  • Seven-year move to AWS: finished in January 2016, replacing a big single database with distributed systems.
  • Microservices: hundreds of small services that fail independently.
  • Chaos engineering: tools like Chaos Monkey deliberately kill production servers so systems must survive failures.
  • Open Connect: Netflix's own content delivery network, with servers placed inside internet providers' networks.

The Timeline

timeline title Netflix reliability milestones 2007 : Streaming launches 2008 : Database corruption halts DVD shipping for 3 days 2012 : Chaos Monkey open-sourced 2016 : Cloud migration complete (January) 2024 : Paul vs Tyson: 65M concurrent streams

1. The Outage That Changed Everything

In August 2008, a major database corruption meant Netflix couldn't ship DVDs for three days. Its VP of cloud and platform engineering later described the lesson: move away from "vertically scaled single points of failure" like relational databases in their own data centre, towards highly reliable, horizontally scalable, distributed systems in the cloud.

That migration took seven years. Netflix shut down the last data-centre pieces used by its streaming service in January 2016.

Key takeaway: Netflix's reliability started with removing single points of failure, not with adding more servers.

2. Microservices: Small Pieces That Fail Alone

Instead of one giant application, Netflix runs hundreds of small services. If the service that recommends titles fails, playback can keep working. The blast radius of any single failure stays small.

Netflix also open-sourced the tools it built to run them, including Zuul (API gateway), Eureka (service discovery), Hystrix (circuit breaker, now in maintenance mode) and Spinnaker (continuous delivery). Those patterns spread across the industry.


3. Chaos Engineering: Break It on Purpose

Chaos Monkey randomly terminates production servers. Engineers have no choice but to build services that survive losing a machine at any moment. Netflix open-sourced it in 2012 as part of its Simian Army.

Chaos Kong went further, simulating the loss of an entire AWS region and shifting traffic to the remaining regions, to prove Netflix could survive a regional failure.

Chaos Monkey
Kills individual servers in production, so every service must tolerate instance failure.
Chaos Kong
Simulates losing a whole cloud region, testing regional failover end to end.

4. Open Connect: Netflix's Own CDN

The video itself doesn't stream from AWS. Netflix built Open Connect, its own content delivery network:

  • Open Connect Appliances (OCAs) are placed inside or near internet providers' networks, free for qualifying ISPs.
  • Netflix has described 18,000+ appliances across 175 countries (2024 presentation).
  • In 2018, Netflix said close to 95% of its traffic was delivered over direct connections between Open Connect and ISPs.

The split is simple: everything before you press play (sign-in, browsing, recommendations, choosing a server) runs in the cloud, and everything after (the video bytes) comes from Open Connect, often from a box inside your ISP.

flowchart LR TV["📺 Your TV / phone"] subgraph AWS["Control plane: AWS (multiple regions)"] GW["API gateway
(Zuul)"] --> MS["Hundreds of microservices
sign-in · profiles · search ·
recommendations · billing"] MS --> STEER["Playback service
picks the best OCA for you"] end subgraph ISP["Data plane: Open Connect"] OCA1["OCA inside your ISP"] OCA2["OCA at an internet exchange"] end TV -->|"1. browse, press play"| GW STEER -->|"2. list of OCA URLs"| TV TV ==>|"3. video streams from nearest OCA"| OCA1 TV -.->|fallback| OCA2 AWS -.->|"off-peak: fill OCAs with
tomorrow's popular titles"| ISP

Open Connect servers are filled with content during off-peak hours, based on what's predicted to be popular in that area, so peak-time viewing rarely needs to travel far.


5. Graceful Degradation

When something fails, Netflix aims to degrade instead of breaking. If personalised rows can't load, show a generic list. If one service times out, fail fast with a fallback rather than letting requests pile up. Circuit breakers (the pattern Hystrix popularised) stop one slow service from dragging down everything that depends on it.


Where It Still Gets Hard: Live Events

On-demand video can be cached near you in advance. Live events can't. On 15 November 2024, the Paul vs Tyson fight reached a peak of 65 million concurrent streams, and many viewers saw buffering. Live streaming at that scale remains a harder problem than on-demand, and it's where Netflix's newest engineering effort is focused.


Lessons for Any Engineering Team

  • Remove single points of failure first
  • Split systems so failures stay small (microservices or at least clear boundaries)
  • Test failure deliberately, not just success
  • Put content close to users
  • Design fallbacks so the core experience survives

Frequently Asked Questions

Does Netflix run on AWS?

Netflix's control plane (sign-in, browsing, recommendations, choosing which server streams to you) runs on AWS. It completed its cloud migration in January 2016. The video itself is delivered through Open Connect, Netflix's own CDN, with servers placed inside internet providers' networks.

What is Chaos Monkey?

Chaos Monkey is a Netflix tool that randomly terminates servers in production, so engineers must build services that survive losing any single machine. Netflix open-sourced it in 2012. It inspired the wider practice called chaos engineering.

Has Netflix ever gone down?

Yes. No large service has perfect uptime. Netflix has had incidents, and its 2024 Paul vs Tyson live stream drew widespread buffering complaints. Its on-demand streaming is unusually resilient because of its cloud architecture, chaos testing and Open Connect delivery network.


Conclusion

Netflix rarely goes down because it designs for failure at every level: no single points of failure, hundreds of independent services, deliberate chaos testing, its own CDN inside ISPs, and fallbacks that keep playback running. Live events are the frontier where those ideas are still being stretched.


Sources

Last verified: 14 October 2026.


Related reads: How Hotstar Handles Crores of Live Viewers · Microservices Architecture Explained · Load Balancer Explained · Why Apps Crash During High Traffic

I write about system design and how real products are built. Follow on LinkedIn or X, or invite me to speak.