Is Netflix down right now?
HostTracker's monitoring network reached netflix.com and completed a full check without errors. It has been up for 8d 3h.
Checking netflix.com right now
A fresh check, started when you opened this page - each probe runs its own independent DNS, TCP, TLS and HTTP request. Anonymous runs sample the network; a signed-in account checks from more locations.
Incident history
LAST 90 DAYSAbout Netflix outages
Written by the HostTracker monitoring team · updated from live probe data.
Netflix streams video to well over 200 million households, and because most viewing happens in concentrated evening peaks - or during the simultaneous worldwide release of a major title - a Netflix problem is felt by huge audiences at exactly the same moment. Its architecture also makes "is Netflix down" genuinely ambiguous: the website and apps run on centralized cloud infrastructure, but the video itself is served by Open Connect cache appliances installed inside individual ISPs' networks, so playback can fail for one provider's customers while netflix.com loads perfectly everywhere else. Netflix's own error codes (NW-2-5 and friends) mostly point at local network issues, which makes an independent, multi-location reachability check the quickest way to tell a real Netflix incident apart from a problem between your device and their nearest cache.
Common causes of Netflix downtime
Login and profile-service incidents that block sign-in and the "Who's watching" screen while already-running streams keep playing
Open Connect CDN issues inside a specific ISP that cause buffering or playback errors regionally while the main site stays reachable
Demand spikes around major title premieres and live events - live broadcasts stress a different, less cache-friendly delivery path than regular on-demand streaming
Device-family-specific app or API incidents where smart-TV or console apps fail while the browser player works normally
Not sure whether it's Netflix or your own connection? Read the full breakdown in our website down checker guide for a general walkthrough of diagnosing any outage, from DNS failures to expired certificates.
Other services we track
HostTracker has monitored websites and online services since 2004 and is trusted by 500,000+ sites today, covering 13 check types from 300+ global locations. Want the same multi-location confirmation and instant alerts for your own site or any service you depend on? Getting started costs nothing - start a free monitor or compare plans and pricing.
Questions people ask during an outage
The live probe run on this page tests netflix.com from a broad sample of HostTracker's 300+-location monitoring network - many independent networks at the same moment, rather than just your own connection. If every location fails to reach it, the outage is real and affects everyone; if only a few locations fail while most load normally, the problem is local to those regions or networks rather than Netflix being fully down. A single refresh from your own browser can never make that distinction, because it only ever tests from one vantage point on one network.
Yes. HostTracker lets you add any URL - including third-party services you depend on, not just your own website - as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.
No - as of the most recent check, netflix.com is responding normally to HostTracker's monitoring network, and has been up for 8d 3h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.
Usually not. NW-2-5 and most other NW-prefixed codes indicate a network-connectivity problem between your device and Netflix, which is far more often caused by your home network, DNS settings, or ISP routing than by Netflix itself. During a genuine Netflix incident, errors tend to spike across many different codes and device types at once rather than showing one code on one device. The fastest way to tell the difference is to check netflix.com's reachability from multiple independent locations: if it's reachable globally while your device errors, the problem is almost certainly on your side of the connection - restart your router and device before assuming an outage.
Netflix delivers the actual video from Open Connect cache servers placed inside or very close to individual ISPs' networks - so the streaming path differs by provider in a way most websites' traffic doesn't. Congestion or a fault affecting the cache cluster serving your ISP can degrade playback for that provider's customers specifically, while users on other networks stream normally and netflix.com itself stays up. If mobile data works but your home connection doesn't, this kind of ISP-localized delivery issue (or a peering/congestion problem at your provider) is the likely cause rather than a global Netflix outage.
Monitor your website from 300+ locations
Start a free trial and get instant alerts when your site goes down - verified from multiple locations before you're notified.