Skip to content

Outage tracker / Netflix

Is Netflix down?

I'm having a problem

Checks passingchecked 1 minute ago

Our checks of Netflix pass from all 10 regions we check.

As of Oct 14, 2026, 4:14 AM UTC, RealUptime's checks of Netflix passed in all 10 regions that returned a reading.

Front-door checks

Last time our checks failed from two or more distant regions: 20 min on Sep 9, 2026 (web surface, from Southeast Asia and US-West).

Email me when our checks of Netflix fail from two or more distant regions

One email when our checks of Netflix fail from two or more distant regions, and one when they pass, after you confirm the address. No account, no card.

This is our own reading from outside. It is not Netflix's official status.

our check readinglive · checked Oct 14, 2026, 4:14 AM UTC
US-East801 msChecks passing
US-West488 msChecks passing
Europe976 msChecks passing
Asia-Pacific1239 msChecks passing
US-Central437 msChecks passing
Canada937 msChecks passing
UK455 msChecks passing
Southeast Asia1826 msChecks passing
Australia1480 msChecks passing
South America1209 msChecks passing
their status pagetheir claim, not our reading

Netflix publishes no status feed we can read, so the only reading here is our check reading on the left.

Netflix response time, by region

US-East
758msp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 754ms2026-09-16 UTC: p95 791ms2026-09-17 UTC: p95 851ms2026-09-18 UTC: p95 808ms2026-09-19 UTC: p95 889ms2026-09-20 UTC: p95 932ms2026-09-21 UTC: p95 939ms2026-09-22 UTC: p95 831ms2026-09-23 UTC: p95 958ms2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 995ms2026-09-26 UTC: p95 904ms2026-09-27 UTC: p95 884ms2026-09-28 UTC: p95 868ms2026-09-29 UTC: p95 829ms2026-09-30 UTC: p95 840ms2026-10-01 UTC: p95 1.0s2026-10-02 UTC: p95 825ms2026-10-03 UTC: p95 909ms2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.0s2026-10-06 UTC: p95 939ms2026-10-07 UTC: p95 877ms2026-10-08 UTC: p95 856ms2026-10-09 UTC: p95 789ms2026-10-10 UTC: p95 828ms2026-10-11 UTC: p95 807ms2026-10-12 UTC: p95 761ms2026-10-13 UTC: p95 797ms2026-10-14 UTC: p95 758ms
Sep 15Sep 29Oct 14
US-West
1.0sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 895ms2026-09-16 UTC: p95 991ms2026-09-17 UTC: p95 932ms2026-09-18 UTC: p95 924ms2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 952ms2026-09-28 UTC: p95 990ms2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 976ms2026-10-03 UTC: p95 983ms2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.0s2026-10-06 UTC: p95 999ms2026-10-07 UTC: p95 991ms2026-10-08 UTC: p95 1.0s2026-10-09 UTC: p95 839ms2026-10-10 UTC: p95 877ms2026-10-11 UTC: p95 863ms2026-10-12 UTC: p95 836ms2026-10-13 UTC: p95 880ms2026-10-14 UTC: p95 1.0s
Sep 15Sep 29Oct 14
Europe
914msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 1.5s2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.7s2026-09-26 UTC: p95 1.8s2026-09-27 UTC: p95 1.6s2026-09-28 UTC: p95 1.7s2026-09-29 UTC: p95 1.9s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 1.7s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 914ms
Sep 15Sep 29Oct 14
Asia-Pacific
1.2sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 921ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 1.4s2026-10-06 UTC: p95 1.5s2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.2s
Sep 15Sep 29Oct 14
US-Central
1.4sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 976ms2026-09-17 UTC: p95 844ms2026-09-18 UTC: p95 910ms2026-09-19 UTC: p95 763ms2026-09-20 UTC: p95 766ms2026-09-21 UTC: p95 768ms2026-09-22 UTC: p95 895ms2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 970ms2026-09-28 UTC: p95 934ms2026-09-29 UTC: p95 954ms2026-09-30 UTC: p95 878ms2026-10-01 UTC: p95 950ms2026-10-02 UTC: p95 874ms2026-10-03 UTC: p95 874ms2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 982ms2026-10-06 UTC: p95 1.0s2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 829ms2026-10-10 UTC: p95 931ms2026-10-11 UTC: p95 961ms2026-10-12 UTC: p95 886ms2026-10-13 UTC: p95 860ms2026-10-14 UTC: p95 1.4s
Sep 15Sep 29Oct 14
Canada
1.4sp95 · latest
2.5s1.3s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 1.9s2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.0s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.5s2026-09-23 UTC: p95 1.5s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 1.9s2026-09-30 UTC: p95 2.0s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.7s2026-10-03 UTC: p95 1.7s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 2.1s2026-10-06 UTC: p95 2.2s2026-10-07 UTC: p95 986ms2026-10-08 UTC: p95 1.5s2026-10-09 UTC: p95 845ms2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.4s
Sep 15Sep 29Oct 14
UK
875msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 994ms2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 987ms2026-09-18 UTC: p95 996ms2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 943ms2026-09-22 UTC: p95 822ms2026-09-23 UTC: p95 786ms2026-09-24 UTC: p95 974ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 855ms2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 959ms2026-10-02 UTC: p95 1.6s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.4s2026-10-06 UTC: p95 1.4s2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 1.0s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 875ms
Sep 15Sep 29Oct 14
Southeast Asia
2.4sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 2.2s2026-09-16 UTC: p95 2.3s2026-09-17 UTC: p95 2.1s2026-09-18 UTC: p95 2.2s2026-09-19 UTC: p95 2.1s2026-09-20 UTC: p95 2.1s2026-09-21 UTC: p95 2.6s2026-09-22 UTC: p95 2.4s2026-09-23 UTC: p95 3.4s2026-09-24 UTC: p95 2.9s2026-09-25 UTC: p95 2.5s2026-09-26 UTC: p95 2.8s2026-09-27 UTC: p95 2.1s2026-09-28 UTC: p95 2.2s2026-09-29 UTC: p95 2.8s2026-09-30 UTC: p95 2.2s2026-10-01 UTC: p95 2.1s2026-10-02 UTC: p95 2.4s2026-10-03 UTC: p95 2.2s2026-10-04 UTC: p95 2.2s2026-10-05 UTC: p95 2.5s2026-10-06 UTC: p95 2.4s2026-10-07 UTC: p95 2.5s2026-10-08 UTC: p95 2.4s2026-10-09 UTC: p95 2.5s2026-10-10 UTC: p95 2.3s2026-10-11 UTC: p95 2.6s2026-10-12 UTC: p95 2.5s2026-10-13 UTC: p95 2.1s2026-10-14 UTC: p95 2.4s
Sep 15Sep 29Oct 14
Australia
2.2sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 2.7s2026-09-16 UTC: p95 2.7s2026-09-17 UTC: p95 2.5s2026-09-18 UTC: p95 2.5s2026-09-19 UTC: p95 2.7s2026-09-20 UTC: p95 2.9s2026-09-21 UTC: p95 3.1s2026-09-22 UTC: p95 3.0s2026-09-23 UTC: p95 2.7s2026-09-24 UTC: p95 3.0s2026-09-25 UTC: p95 2.1s2026-09-26 UTC: p95 2.5s2026-09-27 UTC: p95 2.1s2026-09-28 UTC: p95 2.3s2026-09-29 UTC: p95 2.4s2026-09-30 UTC: p95 2.5s2026-10-01 UTC: p95 2.0s2026-10-02 UTC: p95 2.3s2026-10-03 UTC: p95 2.2s2026-10-04 UTC: p95 2.4s2026-10-05 UTC: p95 2.8s2026-10-06 UTC: p95 2.4s2026-10-07 UTC: p95 1.7s2026-10-08 UTC: p95 2.7s2026-10-09 UTC: p95 2.2s2026-10-10 UTC: p95 2.2s2026-10-11 UTC: p95 2.2s2026-10-12 UTC: p95 2.5s2026-10-13 UTC: p95 2.6s2026-10-14 UTC: p95 2.2s
Sep 15Sep 29Oct 14
South America
2.4sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 2.5s2026-09-16 UTC: p95 2.9s2026-09-17 UTC: p95 2.9s2026-09-18 UTC: p95 2.5s2026-09-19 UTC: p95 2.5s2026-09-20 UTC: p95 2.6s2026-09-21 UTC: p95 2.5s2026-09-22 UTC: p95 2.5s2026-09-23 UTC: p95 2.2s2026-09-24 UTC: p95 2.1s2026-09-25 UTC: p95 2.8s2026-09-26 UTC: p95 2.8s2026-09-27 UTC: p95 2.9s2026-09-28 UTC: p95 2.8s2026-09-29 UTC: p95 2.8s2026-09-30 UTC: p95 3.1s2026-10-01 UTC: p95 2.6s2026-10-02 UTC: p95 2.3s2026-10-03 UTC: p95 3.1s2026-10-04 UTC: p95 3.4s2026-10-05 UTC: p95 2.5s2026-10-06 UTC: p95 2.5s2026-10-07 UTC: p95 1.6s2026-10-08 UTC: p95 1.8s2026-10-09 UTC: p95 2.5s2026-10-10 UTC: p95 2.1s2026-10-11 UTC: p95 2.2s2026-10-12 UTC: p95 2.6s2026-10-13 UTC: p95 2.7s2026-10-14 UTC: p95 2.4s
Sep 15Sep 29Oct 14

Check your own site while you wait on Netflix

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Netflix. It cannot diagnose Netflix's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 801msstatus code: 200checked: Oct 14, 2026, 4:14 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Netflix normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 488msstatus code: 200checked: Oct 14, 2026, 4:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Netflix normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 437msstatus code: 200checked: Oct 14, 2026, 4:14 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Netflix normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 937msstatus code: 200checked: Oct 14, 2026, 4:11 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Netflix normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1209msstatus code: 200checked: Oct 14, 2026, 4:08 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Netflix normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 976msstatus code: 200checked: Oct 14, 2026, 4:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Netflix normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 455msstatus code: 200checked: Oct 14, 2026, 4:12 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Netflix normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1239msstatus code: 200checked: Oct 14, 2026, 4:11 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Netflix normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1826msstatus code: 200checked: Oct 14, 2026, 3:55 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Netflix normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1480msstatus code: 200checked: Oct 14, 2026, 4:13 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Netflix normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Netflix, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Netflix yet, which is not evidence that nothing is wrong.

Recent probe events

Checks failing, 20mour checks · Southeast Asia and US-West2026-09-09

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Netflix since August 8, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Netflix covering any window you pick, with our check readings and Netflix's own claim at the time, side by side.

Full check history for Netflix: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Put this badge in your README

Netflix uptime by RealUptime's checksLive, from this page's own readings.
[![Netflix uptime by RealUptime's checks](https://realuptime.io/outages/netflix/badge.svg?days=30)](https://realuptime.io/outages/netflix)
<a href="https://realuptime.io/outages/netflix"><img src="https://realuptime.io/outages/netflix/badge.svg?days=30" alt="Netflix uptime by RealUptime's checks"></a>

The badge shows the share of our checks that passed over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Netflix down?", https://realuptime.io/outages/netflix. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

How our checks compare with Netflix's stated SLA

At or above your target

Our checks of Netflix failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from Netflix's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primary
https://www.netflix.com/

What our check can and cannot see

A pass means the service's public web page loaded and answered normally. It does not show that the product, the API or sign-in behind it works; a page can load from a cache while the product is down.

Host checked: www.netflix.com

RealUptime is not affiliated with Netflix; the name identifies what we checked, and nothing here speaks for Netflix's own team. We send a single web request to Netflix from 10 regions on our own schedule and time the response. We do not see inside Netflix's systems, do not use an account or real transaction, and are not the same signal Netflix's own team has access to. Treat this as one external data point, not a verdict. What we check for Netflix is its front door only: a passing check means the endpoints above answered, not that the underlying product or account features work. Read the full methodology.