Skip to content

Outage tracker / Disney+

Is Disney+ down?

I'm having a problem

Operationalchecked 2 minutes ago

We reached Disney+ from all 10 regions we check.

As of Oct 5, 2026, 8:15 PM UTC, Disney+ answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured Disney+ (since Aug 20, 2026).

Email me the next time we see Disney+ go down

Measured by our own probes from ten regions, not Disney+'s status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

our independent probeslive · checked Oct 5, 2026, 8:15 PM UTC
US-East478 msOperational
US-West749 msOperational
Europe82 msOperational
Asia-Pacific840 msOperational
US-Central702 msOperational
Canada527 msOperational
UK350 msOperational
Southeast Asia820 msOperational
Australia383 msOperational
South America642 msOperational
their status pagetheir claim, not our reading

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

Disney+ response time, by region

US-East
736msp95 · 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-06 UTC: p95 609ms2026-09-07 UTC: p95 592ms2026-09-08 UTC: p95 635ms2026-09-09 UTC: p95 665ms2026-09-10 UTC: p95 622ms2026-09-11 UTC: p95 670ms2026-09-12 UTC: p95 698ms2026-09-13 UTC: p95 649ms2026-09-14 UTC: p95 584ms2026-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 736ms
Sep 6Sep 20Oct 5
US-West
536msp95 · 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-06 UTC: p95 1.3s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 331ms2026-09-10 UTC: p95 309ms2026-09-11 UTC: p95 283ms2026-09-12 UTC: p95 271ms2026-09-13 UTC: p95 515ms2026-09-14 UTC: p95 517ms2026-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 536ms
Sep 6Sep 20Oct 5
Europe
241msp95 · 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-06 UTC: p95 215ms2026-09-07 UTC: p95 223ms2026-09-08 UTC: p95 224ms2026-09-09 UTC: p95 206ms2026-09-10 UTC: p95 237ms2026-09-11 UTC: p95 255ms2026-09-12 UTC: p95 354ms2026-09-13 UTC: p95 214ms2026-09-14 UTC: p95 265ms2026-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 241ms
Sep 6Sep 20Oct 5
Asia-Pacific
819msp95 · 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-06 UTC: p95 987ms2026-09-07 UTC: p95 894ms2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 975ms2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 893ms2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 984ms2026-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 819ms
Sep 6Sep 20Oct 5
US-Central
669msp95 · 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-06 UTC: p95 564ms2026-09-07 UTC: p95 574ms2026-09-08 UTC: p95 525ms2026-09-09 UTC: p95 612ms2026-09-10 UTC: p95 508ms2026-09-11 UTC: p95 549ms2026-09-12 UTC: p95 633ms2026-09-13 UTC: p95 596ms2026-09-14 UTC: p95 580ms2026-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 669ms
Sep 6Sep 20Oct 5
Canada
649msp95 · 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-06 UTC: p95 734ms2026-09-07 UTC: p95 559ms2026-09-08 UTC: p95 544ms2026-09-09 UTC: p95 739ms2026-09-10 UTC: p95 814ms2026-09-11 UTC: p95 740ms2026-09-12 UTC: p95 618ms2026-09-13 UTC: p95 484ms2026-09-14 UTC: p95 566ms2026-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 649ms
Sep 6Sep 20Oct 5
UK
312msp95 · 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-06 UTC: p95 376ms2026-09-07 UTC: p95 353ms2026-09-08 UTC: p95 342ms2026-09-09 UTC: p95 180ms2026-09-10 UTC: p95 263ms2026-09-11 UTC: p95 157ms2026-09-12 UTC: p95 259ms2026-09-13 UTC: p95 299ms2026-09-14 UTC: p95 287ms2026-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 312ms
Sep 6Sep 20Oct 5
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-06 UTC: p95 1.1s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 1.3s2026-09-12 UTC: p95 1.6s2026-09-13 UTC: p95 1.4s2026-09-14 UTC: p95 1.4s2026-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.1s
Sep 6Sep 20Oct 5
Australia
1.2sp95 · 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-06 UTC: p95 1.2s2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.0s2026-09-10 UTC: p95 933ms2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 1.4s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.1s2026-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.2s
Sep 6Sep 20Oct 5
South America
1.2sp95 · 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-06 UTC: p95 1.2s2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 828ms2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 1.3s2026-09-13 UTC: p95 1.3s2026-09-14 UTC: p95 1.4s2026-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.2s
Sep 6Sep 20Oct 5

Is it Disney+, or is it you?

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: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
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 we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 478msstatus code: 401checked: Oct 5, 2026, 8:09 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
      Operationallatency: 749msstatus code: 401checked: Oct 5, 2026, 8:08 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
      Operationallatency: 702msstatus code: 401checked: Oct 5, 2026, 8:15 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
      Operationallatency: 527msstatus code: 401checked: Oct 5, 2026, 8:10 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
    Operationallatency: 642msstatus code: 401checked: Oct 5, 2026, 8:03 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 82msstatus code: 401checked: Oct 5, 2026, 8:10 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
      Operationallatency: 350msstatus code: 401checked: Oct 5, 2026, 8:08 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 840msstatus code: 401checked: Oct 5, 2026, 8:11 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
      Operationallatency: 820msstatus code: 401checked: Oct 5, 2026, 7:57 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
      Operationallatency: 383msstatus code: 401checked: Oct 5, 2026, 8:08 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 outages

No outages on record yet for Disney+.

measured 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 measurements and Disney+'s own claim at the time, side by side.

Full availability history for Disney+: 90-day availability by region, month-by-month uptime, and every incident on record.

Put this badge in your README

Disney+ uptime measured by RealUptimeLive, from this page's own readings.
[![Disney+ uptime measured by RealUptime](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 measured by RealUptime"></a>

The badge shows the share of our probes that succeeded 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: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Disney+'s SLA implies, from our measurement

At or above your target

We measured none of downtime for Disney+ over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, 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/
RealUptime is not affiliated with Disney+; the name identifies what we measured, 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 clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.