Skip to content

Outage tracker / Disney+

Is Disney+ down?

I'm having a problem

Checks passingchecked 1 minute ago

Our checks of Disney+ pass from all 10 regions we check.

As of Nov 5, 2026, 2:04 PM UTC, RealUptime's checks of Disney+ passed in all 10 regions that returned a reading.

Front-door and live API checks

Our checks of Disney+ did not fail from two or more distant regions in the 77 days we have checked it (since Aug 20, 2026). This does not show Disney+ works for users.

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

One email when our checks of Disney+ 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 Disney+'s official status.

our check readinglive · checked Nov 5, 2026, 2:04 PM UTC
US-East1989 msChecks passing
US-West1652 msChecks passing
Europe1171 msChecks passing
Asia-Pacific2216 msChecks passing
US-Central2094 msChecks passing
Canada1037 msChecks passing
UK371 msChecks passing
Southeast Asia1415 msChecks passing
Australia818 msChecks passing
South America2010 msChecks passing
their status pagetheir claim, not our reading

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

Disney+ response time, by region

US-East
1.9sp95 · 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 828ms2026-10-08 UTC: p95 898ms2026-10-09 UTC: p95 718ms2026-10-10 UTC: p95 693ms2026-10-11 UTC: p95 634ms2026-10-12 UTC: p95 736ms2026-10-13 UTC: p95 821ms2026-10-14 UTC: p95 806ms2026-10-15 UTC: p95 786ms2026-10-16 UTC: p95 751ms2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 2.1s2026-10-19 UTC: p95 2.0s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 2.2s2026-10-22 UTC: p95 2.2s2026-10-23 UTC: p95 2.2s2026-10-24 UTC: p95 2.2s2026-10-25 UTC: p95 2.1s2026-10-26 UTC: p95 2.6s2026-10-27 UTC: p95 2.2s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 2.1s2026-10-30 UTC: p95 2.2s2026-10-31 UTC: p95 2.4s2026-11-01 UTC: p95 2.4s2026-11-02 UTC: p95 2.8s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
US-West
2.3sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 477ms2026-10-08 UTC: p95 603ms2026-10-09 UTC: p95 612ms2026-10-10 UTC: p95 764ms2026-10-11 UTC: p95 639ms2026-10-12 UTC: p95 652ms2026-10-13 UTC: p95 679ms2026-10-14 UTC: p95 629ms2026-10-15 UTC: p95 639ms2026-10-16 UTC: p95 635ms2026-10-17 UTC: p95 906ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.5s2026-10-21 UTC: p95 2.1s2026-10-22 UTC: p95 2.2s2026-10-23 UTC: p95 2.0s2026-10-24 UTC: p95 1.9s2026-10-25 UTC: p95 1.9s2026-10-26 UTC: p95 2.2s2026-10-27 UTC: p95 2.1s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 2.0s2026-10-30 UTC: p95 1.9s2026-10-31 UTC: p95 2.1s2026-11-01 UTC: p95 2.1s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 2.4s2026-11-05 UTC: p95 2.3s
Oct 7Oct 21Nov 5
Europe
1.2sp95 · 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-10-07 UTC: p95 294ms2026-10-08 UTC: p95 396ms2026-10-09 UTC: p95 298ms2026-10-10 UTC: p95 364ms2026-10-11 UTC: p95 388ms2026-10-12 UTC: p95 322ms2026-10-13 UTC: p95 166ms2026-10-14 UTC: p95 232ms2026-10-15 UTC: p95 215ms2026-10-16 UTC: p95 212ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.3s2026-10-25 UTC: p95 1.3s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.4s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
Asia-Pacific
4.6sp95 · 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 872ms2026-10-08 UTC: p95 866ms2026-10-09 UTC: p95 868ms2026-10-10 UTC: p95 812ms2026-10-11 UTC: p95 797ms2026-10-12 UTC: p95 866ms2026-10-13 UTC: p95 843ms2026-10-14 UTC: p95 795ms2026-10-15 UTC: p95 1.0s2026-10-16 UTC: p95 946ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 2.2s2026-10-22 UTC: p95 2.6s2026-10-23 UTC: p95 3.0s2026-10-24 UTC: p95 2.8s2026-10-25 UTC: p95 2.2s2026-10-26 UTC: p95 2.4s2026-10-27 UTC: p95 2.2s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 1.8s2026-10-30 UTC: p95 1.8s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 2.0s2026-11-02 UTC: p95 2.8s2026-11-03 UTC: p95 3.9s2026-11-04 UTC: p95 3.6s2026-11-05 UTC: p95 4.6s
Oct 7Oct 21Nov 5
US-Central
2.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 698ms2026-10-08 UTC: p95 637ms2026-10-09 UTC: p95 615ms2026-10-10 UTC: p95 666ms2026-10-11 UTC: p95 584ms2026-10-12 UTC: p95 651ms2026-10-13 UTC: p95 684ms2026-10-14 UTC: p95 719ms2026-10-15 UTC: p95 621ms2026-10-16 UTC: p95 716ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.4s2026-10-22 UTC: p95 1.4s2026-10-23 UTC: p95 2.1s2026-10-24 UTC: p95 2.1s2026-10-25 UTC: p95 2.1s2026-10-26 UTC: p95 2.4s2026-10-27 UTC: p95 2.2s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 2.0s2026-10-30 UTC: p95 2.3s2026-10-31 UTC: p95 2.2s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 2.1s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 2.2s2026-11-05 UTC: p95 2.3s
Oct 7Oct 21Nov 5
Canada
1.7sp95 · latest
5s2.5s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 923ms2026-10-08 UTC: p95 915ms2026-10-09 UTC: p95 843ms2026-10-10 UTC: p95 878ms2026-10-11 UTC: p95 906ms2026-10-12 UTC: p95 889ms2026-10-13 UTC: p95 790ms2026-10-14 UTC: p95 923ms2026-10-15 UTC: p95 748ms2026-10-16 UTC: p95 738ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 2.3s2026-10-23 UTC: p95 2.4s2026-10-24 UTC: p95 2.3s2026-10-25 UTC: p95 2.3s2026-10-26 UTC: p95 2.9s2026-10-27 UTC: p95 2.5s2026-10-28 UTC: p95 2.3s2026-10-29 UTC: p95 2.3s2026-10-30 UTC: p95 2.4s2026-10-31 UTC: p95 2.3s2026-11-01 UTC: p95 2.4s2026-11-02 UTC: p95 2.6s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 2.4s2026-11-05 UTC: p95 1.7s
Oct 7Oct 21Nov 5
UK
1.1sp95 · latest
2.5s1.3s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 308ms2026-10-08 UTC: p95 359ms2026-10-09 UTC: p95 470ms2026-10-10 UTC: p95 251ms2026-10-11 UTC: p95 273ms2026-10-12 UTC: p95 348ms2026-10-13 UTC: p95 184ms2026-10-14 UTC: p95 187ms2026-10-15 UTC: p95 210ms2026-10-16 UTC: p95 352ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.6s2026-10-23 UTC: p95 1.7s2026-10-24 UTC: p95 1.8s2026-10-25 UTC: p95 1.8s2026-10-26 UTC: p95 2.2s2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 1.6s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
Southeast Asia
1.9sp95 · 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-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 2.9s2026-10-22 UTC: p95 3.3s2026-10-23 UTC: p95 3.0s2026-10-24 UTC: p95 2.8s2026-10-25 UTC: p95 2.9s2026-10-26 UTC: p95 3.0s2026-10-27 UTC: p95 2.9s2026-10-28 UTC: p95 3.1s2026-10-29 UTC: p95 2.7s2026-10-30 UTC: p95 2.8s2026-10-31 UTC: p95 2.9s2026-11-01 UTC: p95 3.0s2026-11-02 UTC: p95 2.4s2026-11-03 UTC: p95 2.2s2026-11-04 UTC: p95 1.8s2026-11-05 UTC: p95 1.9s
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 965ms2026-10-08 UTC: p95 899ms2026-10-09 UTC: p95 951ms2026-10-10 UTC: p95 870ms2026-10-11 UTC: p95 904ms2026-10-12 UTC: p95 814ms2026-10-13 UTC: p95 904ms2026-10-14 UTC: p95 871ms2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 952ms2026-10-17 UTC: p95 1.7s2026-10-18 UTC: p95 1.9s2026-10-19 UTC: p95 1.8s2026-10-20 UTC: p95 2.6s2026-10-21 UTC: p95 2.9s2026-10-22 UTC: p95 2.7s2026-10-23 UTC: p95 2.5s2026-10-24 UTC: p95 2.4s2026-10-25 UTC: p95 3.0s2026-10-26 UTC: p95 3.0s2026-10-27 UTC: p95 3.2s2026-10-28 UTC: p95 3.1s2026-10-29 UTC: p95 3.5s2026-10-30 UTC: p95 3.7s2026-10-31 UTC: p95 2.4s2026-11-01 UTC: p95 2.5s2026-11-02 UTC: p95 2.4s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.3s2026-11-05 UTC: p95 2.4s
Oct 7Oct 21Nov 5
South America
2.5sp95 · 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-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 891ms2026-10-13 UTC: p95 840ms2026-10-14 UTC: p95 1.3s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 692ms2026-10-18 UTC: p95 728ms2026-10-19 UTC: p95 750ms2026-10-20 UTC: p95 3.1s2026-10-21 UTC: p95 2.7s2026-10-22 UTC: p95 2.9s2026-10-23 UTC: p95 4.9s2026-10-24 UTC: p95 3.4s2026-10-25 UTC: p95 3.6s2026-10-26 UTC: p95 3.7s2026-10-27 UTC: p95 3.4s2026-10-28 UTC: p95 2.5s2026-10-29 UTC: p95 2.8s2026-10-30 UTC: p95 2.5s2026-10-31 UTC: p95 2.6s2026-11-01 UTC: p95 2.7s2026-11-02 UTC: p95 2.7s2026-11-03 UTC: p95 2.4s2026-11-04 UTC: p95 2.5s2026-11-05 UTC: p95 2.5s
Oct 7Oct 21Nov 5

Check your own site while you wait on Disney+

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 Disney+. It cannot diagnose Disney+'s own systems.

What we measured, function by function

Disney+ 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 api 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.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Awaiting dataCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-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
  • App configurationUS-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
  • Sign-inUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Awaiting dataCanada: 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: 1989msstatus code: 401checked: Nov 5, 2026, 1:57 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Disney+ normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1652msstatus code: 401checked: Nov 5, 2026, 2:00 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Disney+ normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 2094msstatus code: 401checked: Nov 5, 2026, 1:58 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Disney+ normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 1037msstatus code: 401checked: Nov 5, 2026, 1:59 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Disney+ normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 2010msstatus code: 401checked: Nov 5, 2026, 2:04 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Disney+ 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: 1171msstatus code: 401checked: Nov 5, 2026, 1:53 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Disney+ normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 371msstatus code: 401checked: Nov 5, 2026, 1:54 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Disney+ 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: 2216msstatus code: 401checked: Nov 5, 2026, 1:59 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Disney+ normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1415msstatus code: 401checked: Nov 5, 2026, 1:49 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Disney+ normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 818msstatus code: 401checked: Nov 5, 2026, 2:00 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Disney+ 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 Disney+, 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 Disney+ yet, which is not evidence that nothing is wrong.

Recent probe events

No probe events on record yet for Disney+.

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

We have been measuring Disney+ since August 20, 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 Disney+ covering any window you pick, with our check readings and Disney+'s own claim at the time, side by side.

Full check history for Disney+: 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

Disney+ uptime by RealUptime's checksLive, from this page's own readings.
[![Disney+ uptime by RealUptime's checks](https://realuptime.io/outages/disney-plus/badge.svg?days=30)](https://realuptime.io/outages/disney-plus)
<a href="https://realuptime.io/outages/disney-plus"><img src="https://realuptime.io/outages/disney-plus/badge.svg?days=30" alt="Disney+ 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 Disney+ down?", https://realuptime.io/outages/disney-plus. The readings change with every check, so give the date you read them.

How our checks compare with Disney+'s stated SLA

At or above your target

Our checks of Disney+ 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 Disney+'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

primaryfunctional: live API
https://disney.api.edge.bamgrid.com/v1/public/graphql
secondary
https://www.disneyplus.com/
secondary
https://www.disneyplus.com/identity/login
secondary
https://bam-sdk-configs.bamgrid.com/bam-sdk/v5.0/disney-svod-3d9324fc/browser/v24.0/linux/chrome/prod.json
secondary
https://help.disneyplus.com/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: disney.api.edge.bamgrid.com

RealUptime is not affiliated with Disney+; the name identifies what we checked, and nothing here speaks for Disney+'s own team. We send a single web request to Disney+ from 10 regions on our own schedule and time the response. We do not see inside Disney+'s systems, do not use an account or real transaction, and are not the same signal Disney+'s own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Disney+ is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.