Skip to content

Outage tracker / Netflix

Is Netflix down?

I'm having a problem

Checks passingchecked moments ago

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

As of Nov 5, 2026, 2:59 PM 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 Nov 5, 2026, 2:59 PM UTC
US-East1460 msChecks passing
US-West1282 msChecks passing
Europe1842 msChecks passing
Asia-Pacific3260 msChecks passing
US-Central904 msChecks passing
Canada1686 msChecks passing
UK578 msChecks passing
Southeast Asia4305 msChecks passing
Australia1420 msChecks passing
South America2759 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
1.8sp95 · latest
5s2.5s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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 918ms2026-10-15 UTC: p95 982ms2026-10-16 UTC: p95 891ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.9s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 1.6s2026-10-24 UTC: p95 1.8s2026-10-25 UTC: p95 1.6s2026-10-26 UTC: p95 2.8s2026-10-27 UTC: p95 1.7s2026-10-28 UTC: p95 1.6s2026-10-29 UTC: p95 1.7s2026-10-30 UTC: p95 1.7s2026-10-31 UTC: p95 1.7s2026-11-01 UTC: p95 1.7s2026-11-02 UTC: p95 2.3s2026-11-03 UTC: p95 2.5s2026-11-04 UTC: p95 2.6s2026-11-05 UTC: p95 1.8s
Oct 7Oct 21Nov 5
US-West
2.5sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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 956ms2026-10-15 UTC: p95 971ms2026-10-16 UTC: p95 991ms2026-10-17 UTC: p95 883ms2026-10-18 UTC: p95 931ms2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.8s2026-10-23 UTC: p95 1.9s2026-10-24 UTC: p95 2.0s2026-10-25 UTC: p95 2.0s2026-10-26 UTC: p95 2.1s2026-10-27 UTC: p95 2.1s2026-10-28 UTC: p95 1.8s2026-10-29 UTC: p95 1.9s2026-10-30 UTC: p95 1.8s2026-10-31 UTC: p95 1.9s2026-11-01 UTC: p95 1.9s2026-11-02 UTC: p95 2.3s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.8s2026-11-05 UTC: p95 2.5s
Oct 7Oct 21Nov 5
Europe
2.7sp95 · latest
5s2.5s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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 1.3s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 1.8s2026-10-19 UTC: p95 1.7s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 1.8s2026-10-24 UTC: p95 1.7s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 1.9s2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 2.4s2026-10-30 UTC: p95 2.0s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 2.5s2026-11-02 UTC: p95 2.7s2026-11-03 UTC: p95 2.9s2026-11-04 UTC: p95 4.5s2026-11-05 UTC: p95 2.7s
Oct 7Oct 21Nov 5
Asia-Pacific
4.9sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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.4s2026-10-15 UTC: p95 1.5s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 2.5s2026-10-18 UTC: p95 2.5s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 2.2s2026-10-21 UTC: p95 2.6s2026-10-22 UTC: p95 2.8s2026-10-23 UTC: p95 3.1s2026-10-24 UTC: p95 2.8s2026-10-25 UTC: p95 2.5s2026-10-26 UTC: p95 3.0s2026-10-27 UTC: p95 3.1s2026-10-28 UTC: p95 2.5s2026-10-29 UTC: p95 2.6s2026-10-30 UTC: p95 2.5s2026-10-31 UTC: p95 2.3s2026-11-01 UTC: p95 2.5s2026-11-02 UTC: p95 2.6s2026-11-03 UTC: p95 2.8s2026-11-04 UTC: p95 4.6s2026-11-05 UTC: p95 4.9s
Oct 7Oct 21Nov 5
US-Central
1.3sp95 · latest
2.5s1.3s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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.2s2026-10-15 UTC: p95 930ms2026-10-16 UTC: p95 975ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 2.0s2026-10-24 UTC: p95 1.9s2026-10-25 UTC: p95 2.0s2026-10-26 UTC: p95 2.0s2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 1.9s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
Canada
1.9sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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.3s2026-10-15 UTC: p95 1.4s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 972ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 1.5s2026-10-24 UTC: p95 1.6s2026-10-25 UTC: p95 1.5s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 1.8s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 1.8s2026-11-01 UTC: p95 1.9s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.5s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
UK
1.1sp95 · 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-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 879ms2026-10-15 UTC: p95 753ms2026-10-16 UTC: p95 762ms2026-10-17 UTC: p95 746ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 1.4s2026-10-25 UTC: p95 1.3s2026-10-26 UTC: p95 1.4s2026-10-27 UTC: p95 1.0s2026-10-28 UTC: p95 1.5s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
Southeast Asia
5.2sp95 · latest
10s5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-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.4s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 2.4s2026-10-17 UTC: p95 5.2s2026-10-18 UTC: p95 5.4s2026-10-19 UTC: p95 5.3s2026-10-20 UTC: p95 3.3s2026-10-21 UTC: p95 2.5s2026-10-22 UTC: p95 3.2s2026-10-23 UTC: p95 3.3s2026-10-24 UTC: p95 3.3s2026-10-25 UTC: p95 2.8s2026-10-26 UTC: p95 2.7s2026-10-27 UTC: p95 3.2s2026-10-28 UTC: p95 4.0s2026-10-29 UTC: p95 3.5s2026-10-30 UTC: p95 3.3s2026-10-31 UTC: p95 3.3s2026-11-01 UTC: p95 5.9s2026-11-02 UTC: p95 5.1s2026-11-03 UTC: p95 4.3s2026-11-04 UTC: p95 5.7s2026-11-05 UTC: p95 5.2s
Oct 7Oct 21Nov 5
Australia
2.4sp95 · 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-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.2s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.5s2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 2.8s2026-10-19 UTC: p95 2.7s2026-10-20 UTC: p95 2.8s2026-10-21 UTC: p95 2.7s2026-10-22 UTC: p95 2.6s2026-10-23 UTC: p95 2.4s2026-10-24 UTC: p95 2.5s2026-10-25 UTC: p95 2.6s2026-10-26 UTC: p95 2.5s2026-10-27 UTC: p95 2.4s2026-10-28 UTC: p95 2.5s2026-10-29 UTC: p95 2.5s2026-10-30 UTC: p95 2.8s2026-10-31 UTC: p95 2.6s2026-11-01 UTC: p95 2.6s2026-11-02 UTC: p95 2.7s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 2.3s2026-11-05 UTC: p95 2.4s
Oct 7Oct 21Nov 5
South America
4.5sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-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.5s2026-10-15 UTC: p95 2.5s2026-10-16 UTC: p95 2.4s2026-10-17 UTC: p95 5.1s2026-10-18 UTC: p95 5.4s2026-10-19 UTC: p95 5.2s2026-10-20 UTC: p95 5.4s2026-10-21 UTC: p95 5.8s2026-10-22 UTC: p95 4.9s2026-10-23 UTC: p95 8.5s2026-10-24 UTC: p95 5.5s2026-10-25 UTC: p95 5.1s2026-10-26 UTC: p95 4.8s2026-10-27 UTC: p95 4.8s2026-10-28 UTC: p95 5.3s2026-10-29 UTC: p95 4.9s2026-10-30 UTC: p95 5.0s2026-10-31 UTC: p95 5.1s2026-11-01 UTC: p95 4.8s2026-11-02 UTC: p95 5.9s2026-11-03 UTC: p95 4.5s2026-11-04 UTC: p95 5.5s2026-11-05 UTC: p95 4.5s
Oct 7Oct 21Nov 5

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 we measured, function by function

Netflix answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the web row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Help CenterUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Open Connect (fast.com)US-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Sign-inUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • TitlesUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
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: 1460msstatus code: 200checked: Nov 5, 2026, 2:51 PM 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: 1282msstatus code: 200checked: Nov 5, 2026, 2:52 PM 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: 904msstatus code: 200checked: Nov 5, 2026, 2:41 PM 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: 1686msstatus code: 200checked: Nov 5, 2026, 2:45 PM 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: 2759msstatus code: 200checked: Nov 5, 2026, 2:59 PM 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: 1842msstatus code: 200checked: Nov 5, 2026, 2:52 PM 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: 578msstatus code: 200checked: Nov 5, 2026, 2:57 PM 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: 3260msstatus code: 200checked: Nov 5, 2026, 2:54 PM 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: 4305msstatus code: 200checked: Nov 5, 2026, 2:58 PM 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: 1420msstatus code: 200checked: Nov 5, 2026, 2:57 PM 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" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

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.

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/
secondary
https://www.netflix.com/login
secondary
https://www.netflix.com/title/80057281
secondary
https://help.netflix.com/en
secondary
https://fast.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.