Skip to content

Outage tracker / HBO Max

Is HBO Max down?

I'm having a problem

Checks passingchecked 1 minute ago

Our checks of HBO Max pass from all 10 regions we check.

As of Oct 14, 2026, 5:12 AM UTC, RealUptime's checks of HBO Max passed in all 10 regions that returned a reading.

Front-door and live API checks

Our checks of HBO Max 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 HBO Max works for users.

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

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

our check readinglive · checked Oct 14, 2026, 5:12 AM UTC
US-East379 msChecks passing
US-West306 msChecks passing
Europe202 msChecks passing
Asia-Pacific468 msChecks passing
US-Central407 msChecks passing
Canada473 msChecks passing
UK127 msChecks passing
Southeast Asia435 msChecks passing
Australia1033 msChecks passing
South America951 msChecks passing
their status pagetheir claim, not our reading

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

HBO Max response time, by region

US-East
379msp95 · 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 337ms2026-09-16 UTC: p95 426ms2026-09-17 UTC: p95 394ms2026-09-18 UTC: p95 415ms2026-09-19 UTC: p95 382ms2026-09-20 UTC: p95 380ms2026-09-21 UTC: p95 367ms2026-09-22 UTC: p95 402ms2026-09-23 UTC: p95 407ms2026-09-24 UTC: p95 558ms2026-09-25 UTC: p95 482ms2026-09-26 UTC: p95 419ms2026-09-27 UTC: p95 346ms2026-09-28 UTC: p95 365ms2026-09-29 UTC: p95 361ms2026-09-30 UTC: p95 384ms2026-10-01 UTC: p95 502ms2026-10-02 UTC: p95 342ms2026-10-03 UTC: p95 441ms2026-10-04 UTC: p95 390ms2026-10-05 UTC: p95 427ms2026-10-06 UTC: p95 368ms2026-10-07 UTC: p95 359ms2026-10-08 UTC: p95 462ms2026-10-09 UTC: p95 355ms2026-10-10 UTC: p95 377ms2026-10-11 UTC: p95 371ms2026-10-12 UTC: p95 391ms2026-10-13 UTC: p95 433ms2026-10-14 UTC: p95 379ms
Sep 15Sep 29Oct 14
US-West
512msp95 · 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 508ms2026-09-16 UTC: p95 536ms2026-09-17 UTC: p95 625ms2026-09-18 UTC: p95 555ms2026-09-19 UTC: p95 513ms2026-09-20 UTC: p95 585ms2026-09-21 UTC: p95 569ms2026-09-22 UTC: p95 560ms2026-09-23 UTC: p95 567ms2026-09-24 UTC: p95 574ms2026-09-25 UTC: p95 588ms2026-09-26 UTC: p95 510ms2026-09-27 UTC: p95 446ms2026-09-28 UTC: p95 537ms2026-09-29 UTC: p95 507ms2026-09-30 UTC: p95 630ms2026-10-01 UTC: p95 689ms2026-10-02 UTC: p95 650ms2026-10-03 UTC: p95 539ms2026-10-04 UTC: p95 553ms2026-10-05 UTC: p95 629ms2026-10-06 UTC: p95 591ms2026-10-07 UTC: p95 559ms2026-10-08 UTC: p95 640ms2026-10-09 UTC: p95 582ms2026-10-10 UTC: p95 544ms2026-10-11 UTC: p95 556ms2026-10-12 UTC: p95 586ms2026-10-13 UTC: p95 485ms2026-10-14 UTC: p95 512ms
Sep 15Sep 29Oct 14
Europe
226msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 275ms2026-09-16 UTC: p95 254ms2026-09-17 UTC: p95 274ms2026-09-18 UTC: p95 251ms2026-09-19 UTC: p95 248ms2026-09-20 UTC: p95 254ms2026-09-21 UTC: p95 271ms2026-09-22 UTC: p95 270ms2026-09-23 UTC: p95 265ms2026-09-24 UTC: p95 277ms2026-09-25 UTC: p95 279ms2026-09-26 UTC: p95 279ms2026-09-27 UTC: p95 247ms2026-09-28 UTC: p95 256ms2026-09-29 UTC: p95 258ms2026-09-30 UTC: p95 258ms2026-10-01 UTC: p95 237ms2026-10-02 UTC: p95 239ms2026-10-03 UTC: p95 262ms2026-10-04 UTC: p95 587ms2026-10-05 UTC: p95 251ms2026-10-06 UTC: p95 236ms2026-10-07 UTC: p95 262ms2026-10-08 UTC: p95 258ms2026-10-09 UTC: p95 289ms2026-10-10 UTC: p95 275ms2026-10-11 UTC: p95 258ms2026-10-12 UTC: p95 254ms2026-10-13 UTC: p95 213ms2026-10-14 UTC: p95 226ms
Sep 15Sep 29Oct 14
Asia-Pacific
667msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 623ms2026-09-16 UTC: p95 480ms2026-09-17 UTC: p95 624ms2026-09-18 UTC: p95 628ms2026-09-19 UTC: p95 688ms2026-09-20 UTC: p95 560ms2026-09-21 UTC: p95 651ms2026-09-22 UTC: p95 620ms2026-09-23 UTC: p95 663ms2026-09-24 UTC: p95 575ms2026-09-25 UTC: p95 554ms2026-09-26 UTC: p95 592ms2026-09-27 UTC: p95 764ms2026-09-28 UTC: p95 583ms2026-09-29 UTC: p95 489ms2026-09-30 UTC: p95 584ms2026-10-01 UTC: p95 581ms2026-10-02 UTC: p95 540ms2026-10-03 UTC: p95 567ms2026-10-04 UTC: p95 589ms2026-10-05 UTC: p95 650ms2026-10-06 UTC: p95 655ms2026-10-07 UTC: p95 547ms2026-10-08 UTC: p95 508ms2026-10-09 UTC: p95 717ms2026-10-10 UTC: p95 504ms2026-10-11 UTC: p95 509ms2026-10-12 UTC: p95 617ms2026-10-13 UTC: p95 531ms2026-10-14 UTC: p95 667ms
Sep 15Sep 29Oct 14
US-Central
562msp95 · 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 439ms2026-09-16 UTC: p95 500ms2026-09-17 UTC: p95 529ms2026-09-18 UTC: p95 493ms2026-09-19 UTC: p95 440ms2026-09-20 UTC: p95 483ms2026-09-21 UTC: p95 444ms2026-09-22 UTC: p95 487ms2026-09-23 UTC: p95 454ms2026-09-24 UTC: p95 476ms2026-09-25 UTC: p95 396ms2026-09-26 UTC: p95 426ms2026-09-27 UTC: p95 411ms2026-09-28 UTC: p95 477ms2026-09-29 UTC: p95 420ms2026-09-30 UTC: p95 742ms2026-10-01 UTC: p95 382ms2026-10-02 UTC: p95 379ms2026-10-03 UTC: p95 347ms2026-10-04 UTC: p95 453ms2026-10-05 UTC: p95 483ms2026-10-06 UTC: p95 445ms2026-10-07 UTC: p95 389ms2026-10-08 UTC: p95 335ms2026-10-09 UTC: p95 413ms2026-10-10 UTC: p95 346ms2026-10-11 UTC: p95 387ms2026-10-12 UTC: p95 465ms2026-10-13 UTC: p95 427ms2026-10-14 UTC: p95 562ms
Sep 15Sep 29Oct 14
Canada
527msp95 · 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 481ms2026-09-16 UTC: p95 446ms2026-09-17 UTC: p95 433ms2026-09-18 UTC: p95 429ms2026-09-19 UTC: p95 437ms2026-09-20 UTC: p95 414ms2026-09-21 UTC: p95 488ms2026-09-22 UTC: p95 479ms2026-09-23 UTC: p95 452ms2026-09-24 UTC: p95 461ms2026-09-25 UTC: p95 462ms2026-09-26 UTC: p95 484ms2026-09-27 UTC: p95 437ms2026-09-28 UTC: p95 461ms2026-09-29 UTC: p95 488ms2026-09-30 UTC: p95 439ms2026-10-01 UTC: p95 460ms2026-10-02 UTC: p95 465ms2026-10-03 UTC: p95 470ms2026-10-04 UTC: p95 520ms2026-10-05 UTC: p95 534ms2026-10-06 UTC: p95 512ms2026-10-07 UTC: p95 458ms2026-10-08 UTC: p95 482ms2026-10-09 UTC: p95 554ms2026-10-10 UTC: p95 543ms2026-10-11 UTC: p95 484ms2026-10-12 UTC: p95 516ms2026-10-13 UTC: p95 636ms2026-10-14 UTC: p95 527ms
Sep 15Sep 29Oct 14
UK
158msp95 · 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 331ms2026-09-16 UTC: p95 361ms2026-09-17 UTC: p95 332ms2026-09-18 UTC: p95 280ms2026-09-19 UTC: p95 263ms2026-09-20 UTC: p95 297ms2026-09-21 UTC: p95 305ms2026-09-22 UTC: p95 319ms2026-09-23 UTC: p95 383ms2026-09-24 UTC: p95 377ms2026-09-25 UTC: p95 386ms2026-09-26 UTC: p95 331ms2026-09-27 UTC: p95 237ms2026-09-28 UTC: p95 505ms2026-09-29 UTC: p95 415ms2026-09-30 UTC: p95 446ms2026-10-01 UTC: p95 258ms2026-10-02 UTC: p95 235ms2026-10-03 UTC: p95 217ms2026-10-04 UTC: p95 218ms2026-10-05 UTC: p95 227ms2026-10-06 UTC: p95 225ms2026-10-07 UTC: p95 242ms2026-10-08 UTC: p95 234ms2026-10-09 UTC: p95 247ms2026-10-10 UTC: p95 228ms2026-10-11 UTC: p95 220ms2026-10-12 UTC: p95 215ms2026-10-13 UTC: p95 277ms2026-10-14 UTC: p95 158ms
Sep 15Sep 29Oct 14
Southeast Asia
696msp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 690ms2026-09-16 UTC: p95 800ms2026-09-17 UTC: p95 843ms2026-09-18 UTC: p95 923ms2026-09-19 UTC: p95 897ms2026-09-20 UTC: p95 1.0s2026-09-21 UTC: p95 1.8s2026-09-22 UTC: p95 1.8s2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.0s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.1s2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 836ms2026-10-01 UTC: p95 802ms2026-10-02 UTC: p95 846ms2026-10-03 UTC: p95 771ms2026-10-04 UTC: p95 783ms2026-10-05 UTC: p95 671ms2026-10-06 UTC: p95 715ms2026-10-07 UTC: p95 700ms2026-10-08 UTC: p95 697ms2026-10-09 UTC: p95 732ms2026-10-10 UTC: p95 732ms2026-10-11 UTC: p95 730ms2026-10-12 UTC: p95 722ms2026-10-13 UTC: p95 742ms2026-10-14 UTC: p95 696ms
Sep 15Sep 29Oct 14
Australia
1.6sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 1.8s2026-09-16 UTC: p95 1.9s2026-09-17 UTC: p95 1.9s2026-09-18 UTC: p95 1.9s2026-09-19 UTC: p95 1.9s2026-09-20 UTC: p95 1.7s2026-09-21 UTC: p95 1.7s2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 1.5s2026-09-24 UTC: p95 1.7s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 2.0s2026-09-27 UTC: p95 1.9s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 1.7s2026-09-30 UTC: p95 1.8s2026-10-01 UTC: p95 2.3s2026-10-02 UTC: p95 1.6s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 1.4s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.6s
Sep 15Sep 29Oct 14
South America
1.8sp95 · 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.1s2026-09-18 UTC: p95 948ms2026-09-19 UTC: p95 974ms2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 957ms2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 1.3s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.0s2026-10-06 UTC: p95 1.0s2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.8s
Sep 15Sep 29Oct 14
Why some readings show as awaiting data. 1 of 20 readings for HBO Max 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 HBO Max'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 HBO Max

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

What we measured, function by function

HBO Max 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: 379msstatus code: 400checked: Oct 14, 2026, 5:04 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach HBO Max normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 306msstatus code: 400checked: Oct 14, 2026, 5:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach HBO Max normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 407msstatus code: 400checked: Oct 14, 2026, 4:54 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach HBO Max normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 473msstatus code: 400checked: Oct 14, 2026, 5:09 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach HBO Max normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 951msstatus code: 400checked: Oct 14, 2026, 5:05 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach HBO Max 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: 202msstatus code: 400checked: Oct 14, 2026, 5:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach HBO Max normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 127msstatus code: 400checked: Oct 14, 2026, 5:11 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach HBO Max 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: 468msstatus code: 400checked: Oct 14, 2026, 5:12 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach HBO Max normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 435msstatus code: 400checked: Oct 14, 2026, 5:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach HBO Max normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1033msstatus code: 400checked: Oct 14, 2026, 5:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach HBO Max 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 HBO Max, 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 HBO Max yet, which is not evidence that nothing is wrong.

Recent probe events

No probe events on record yet for HBO Max.

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

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

Full check history for HBO Max: 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

HBO Max uptime by RealUptime's checksLive, from this page's own readings.
[![HBO Max uptime by RealUptime's checks](https://realuptime.io/outages/hbo-max/badge.svg?days=30)](https://realuptime.io/outages/hbo-max)
<a href="https://realuptime.io/outages/hbo-max"><img src="https://realuptime.io/outages/hbo-max/badge.svg?days=30" alt="HBO Max 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 HBO Max down?", https://realuptime.io/outages/hbo-max. 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 HBO Max's stated SLA

At or above your target

Our checks of HBO Max 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 HBO Max'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://default.any-any.prd.api.max.com/any/playback/v1/playbackInfo
secondary
https://www.max.com/

What our check can and cannot see

A pass means the service's servers answered our request with the error they give a request that carries no account or valid input. It does not show that sign-in works or that any real request succeeds.

Host checked: default.any-any.prd.api.max.com

RealUptime is not affiliated with HBO Max; the name identifies what we checked, and nothing here speaks for HBO Max's own team. We send a single web request to HBO Max from 10 regions on our own schedule and time the response. We do not see inside HBO Max's systems, do not use an account or real transaction, and are not the same signal HBO Max's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for HBO Max 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.