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 Oct 14, 2026, 4:57 AM 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 55 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 Oct 14, 2026, 4:57 AM UTC
US-East719 msChecks passing
US-West370 msChecks passing
Europe89 msChecks passing
Asia-Pacific638 msChecks passing
US-Central249 msChecks passing
Canada448 msChecks passing
UK120 msChecks passing
Southeast Asia872 msChecks passing
Australia545 msChecks passing
South America127 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
738msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 567ms2026-09-16 UTC: p95 734ms2026-09-17 UTC: p95 685ms2026-09-18 UTC: p95 746ms2026-09-19 UTC: p95 677ms2026-09-20 UTC: p95 585ms2026-09-21 UTC: p95 682ms2026-09-22 UTC: p95 675ms2026-09-23 UTC: p95 719ms2026-09-24 UTC: p95 898ms2026-09-25 UTC: p95 657ms2026-09-26 UTC: p95 610ms2026-09-27 UTC: p95 648ms2026-09-28 UTC: p95 604ms2026-09-29 UTC: p95 716ms2026-09-30 UTC: p95 874ms2026-10-01 UTC: p95 705ms2026-10-02 UTC: p95 745ms2026-10-03 UTC: p95 747ms2026-10-04 UTC: p95 731ms2026-10-05 UTC: p95 738ms2026-10-06 UTC: p95 717ms2026-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 738ms
Sep 15Sep 29Oct 14
US-West
560msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 614ms2026-09-16 UTC: p95 661ms2026-09-17 UTC: p95 670ms2026-09-18 UTC: p95 646ms2026-09-19 UTC: p95 628ms2026-09-20 UTC: p95 630ms2026-09-21 UTC: p95 605ms2026-09-22 UTC: p95 675ms2026-09-23 UTC: p95 716ms2026-09-24 UTC: p95 709ms2026-09-25 UTC: p95 737ms2026-09-26 UTC: p95 632ms2026-09-27 UTC: p95 663ms2026-09-28 UTC: p95 518ms2026-09-29 UTC: p95 644ms2026-09-30 UTC: p95 519ms2026-10-01 UTC: p95 596ms2026-10-02 UTC: p95 590ms2026-10-03 UTC: p95 558ms2026-10-04 UTC: p95 523ms2026-10-05 UTC: p95 547ms2026-10-06 UTC: p95 571ms2026-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 560ms
Sep 15Sep 29Oct 14
Europe
347msp95 · latest
500ms250ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 274ms2026-09-16 UTC: p95 375ms2026-09-17 UTC: p95 397ms2026-09-18 UTC: p95 289ms2026-09-19 UTC: p95 319ms2026-09-20 UTC: p95 327ms2026-09-21 UTC: p95 391ms2026-09-22 UTC: p95 390ms2026-09-23 UTC: p95 291ms2026-09-24 UTC: p95 279ms2026-09-25 UTC: p95 324ms2026-09-26 UTC: p95 379ms2026-09-27 UTC: p95 345ms2026-09-28 UTC: p95 389ms2026-09-29 UTC: p95 381ms2026-09-30 UTC: p95 210ms2026-10-01 UTC: p95 280ms2026-10-02 UTC: p95 299ms2026-10-03 UTC: p95 276ms2026-10-04 UTC: p95 348ms2026-10-05 UTC: p95 246ms2026-10-06 UTC: p95 324ms2026-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 347ms
Sep 15Sep 29Oct 14
Asia-Pacific
725msp95 · 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 1.0s2026-09-16 UTC: p95 982ms2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 989ms2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 964ms2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 1s2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 989ms2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 837ms2026-10-06 UTC: p95 860ms2026-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 725ms
Sep 15Sep 29Oct 14
US-Central
614msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 647ms2026-09-16 UTC: p95 480ms2026-09-17 UTC: p95 577ms2026-09-18 UTC: p95 534ms2026-09-19 UTC: p95 536ms2026-09-20 UTC: p95 567ms2026-09-21 UTC: p95 532ms2026-09-22 UTC: p95 589ms2026-09-23 UTC: p95 569ms2026-09-24 UTC: p95 632ms2026-09-25 UTC: p95 626ms2026-09-26 UTC: p95 530ms2026-09-27 UTC: p95 536ms2026-09-28 UTC: p95 566ms2026-09-29 UTC: p95 596ms2026-09-30 UTC: p95 690ms2026-10-01 UTC: p95 601ms2026-10-02 UTC: p95 557ms2026-10-03 UTC: p95 506ms2026-10-04 UTC: p95 651ms2026-10-05 UTC: p95 672ms2026-10-06 UTC: p95 538ms2026-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 614ms
Sep 15Sep 29Oct 14
Canada
954msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 625ms2026-09-16 UTC: p95 683ms2026-09-17 UTC: p95 538ms2026-09-18 UTC: p95 525ms2026-09-19 UTC: p95 736ms2026-09-20 UTC: p95 771ms2026-09-21 UTC: p95 651ms2026-09-22 UTC: p95 667ms2026-09-23 UTC: p95 775ms2026-09-24 UTC: p95 769ms2026-09-25 UTC: p95 729ms2026-09-26 UTC: p95 703ms2026-09-27 UTC: p95 754ms2026-09-28 UTC: p95 755ms2026-09-29 UTC: p95 738ms2026-09-30 UTC: p95 898ms2026-10-01 UTC: p95 957ms2026-10-02 UTC: p95 865ms2026-10-03 UTC: p95 637ms2026-10-04 UTC: p95 640ms2026-10-05 UTC: p95 676ms2026-10-06 UTC: p95 766ms2026-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 954ms
Sep 15Sep 29Oct 14
UK
185msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 311ms2026-09-16 UTC: p95 386ms2026-09-17 UTC: p95 455ms2026-09-18 UTC: p95 478ms2026-09-19 UTC: p95 438ms2026-09-20 UTC: p95 362ms2026-09-21 UTC: p95 365ms2026-09-22 UTC: p95 491ms2026-09-23 UTC: p95 617ms2026-09-24 UTC: p95 683ms2026-09-25 UTC: p95 601ms2026-09-26 UTC: p95 408ms2026-09-27 UTC: p95 437ms2026-09-28 UTC: p95 428ms2026-09-29 UTC: p95 570ms2026-09-30 UTC: p95 337ms2026-10-01 UTC: p95 444ms2026-10-02 UTC: p95 587ms2026-10-03 UTC: p95 611ms2026-10-04 UTC: p95 513ms2026-10-05 UTC: p95 323ms2026-10-06 UTC: p95 348ms2026-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 185ms
Sep 15Sep 29Oct 14
Southeast Asia
1.1sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 1.4s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 1.5s2026-09-18 UTC: p95 1.6s2026-09-19 UTC: p95 1.8s2026-09-20 UTC: p95 2.2s2026-09-21 UTC: p95 2.1s2026-09-22 UTC: p95 2.0s2026-09-23 UTC: p95 2.2s2026-09-24 UTC: p95 1.8s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.8s2026-09-27 UTC: p95 1.7s2026-09-28 UTC: p95 1.8s2026-09-29 UTC: p95 1.7s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 1.0s2026-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.1s
Sep 15Sep 29Oct 14
Australia
696msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 993ms2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 952ms2026-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 696ms
Sep 15Sep 29Oct 14
South America
1.1sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 1.4s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 1.4s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 1.6s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.4s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 1.0s2026-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.1s
Sep 15Sep 29Oct 14
Why some readings show as awaiting data. 1 of 20 readings for Disney+ came back as a filtered response to our automated checks (a response code that refuses automated clients, such as 403, 405, 406, 429 or 451, a redirect loop, or a timeout that a second endpoint answered) rather than a normal pass or failure. That tells us about our own probe's reception, not about Disney+'s health, so we publish no verdict for those readings rather than guessing in either direction. 1 of those reading received an actual response: the connection, the TLS handshake, and the edge all answered, with a measured latency. Our check passed there, just not through the specific path automated checks are filtered on. Read how we tell the difference.

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
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: 719msstatus code: 401checked: Oct 14, 2026, 4:54 AM 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: 370msstatus code: 401checked: Oct 14, 2026, 4:55 AM 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: 249msstatus code: 401checked: Oct 14, 2026, 4:40 AM 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: 448msstatus code: 401checked: Oct 14, 2026, 4:43 AM 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: 127msstatus code: 401checked: Oct 14, 2026, 4:45 AM 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: 89msstatus code: 401checked: Oct 14, 2026, 4:57 AM 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: 120msstatus code: 401checked: Oct 14, 2026, 4:49 AM 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: 638msstatus code: 401checked: Oct 14, 2026, 4:52 AM 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: 872msstatus code: 401checked: Oct 14, 2026, 4:45 AM 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: 545msstatus code: 401checked: Oct 14, 2026, 4:57 AM 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"></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 Disney+ down?", https://realuptime.io/outages/disney-plus. 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 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/

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.