Skip to content
Max logo

Streaming

Is Max down right now?

UnknownOfficial status last polled Aug 14, 2026 19:20 UTCmax.comNo official status page published

Max (formerly HBO Max) streaming

Are you on the Max team and see something inaccurate? Report it to us. We respond within one business day.

Is Max down right now?

Unknown. Max does not have a conclusive current status. A single-runtime HTTP reachability check succeeded; no fresh official status confirms whole-service health. No current vendor status signal: vendor status was last polled on 2026-08-14, more than 7 days ago.

Status as of Oct 2, 2026 22:59 UTC

Unknown

Max: status unknown

As of Oct 2, 2026 22:59 UTC

No product check is currently qualified to corroborate an incident for this service. Overall service status has not been established.

Reports 24h

0

Last incident

May 3, 2026 11:18 UTC

Trend

0/15m

Monitoring

Coverage gap

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Max.

0

Incident days

30

No recorded incident

0 min

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Max. Hover a day for detail.

Sep 3Sep 8Sep 13Sep 18Sep 23Sep 2801234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

0

Days with incidents

0 incidents

Busiest day

0 min

Recorded duration

Report volume

0 reports in last 24H

10:45 PM02:15 AM05:45 AM09:15 AM12:45 PM04:15 PM07:45 PM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Max outage on May 3 — 33-minute disruption

May 3, 10:44 AM → May 3, 11:18 AM · 33 minutes · high

A service disruption affected Max, detected following user reports. The incident lasted 33 minutes and was resolved on May 3, 2026, at 11:18 UTC.

Peak reports
5
in 15 min
Total reports
2
during the incident
Duration
33 minutes
tracked by PulseWatch

Impact

Users reported issues primarily related to the Max website being down. A total of two user reports were received during the incident, indicating a disruption in service availability. No specific regional impact was recorded for this event.

Top reported issues

  • Website down2

Incident timeline

  1. May 3, 10:44 AM

    PulseWatch detected elevated report volume (high severity)

  2. May 3, 11:00 AM

    Peak of 0 reports in 15 minutes (baseline 1.3)

  3. May 3, 11:18 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 3, 11:18 AM

    Website down clustered from 3 sources across 5 signals. Suppressed 4 redundant alerts.

Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals and the sources listed above.

Reliability

Not measured

30-day uptime

n/a

90-day uptime

n/a

Not calculated: Max is unknown, so there is no incident history to measure and no uptime figure is shown.

Other streaming services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedHigh

Max: grouped 5 related Website down alerts into one incident to reduce noise.

5/3/2026, 10:44:44 AM · 33 min

10:44 AM11:18 AM
Detection5/3/2026, 10:44:44 AM · 5mo ago

Detected — high severity

Max: grouped 5 related Website down alerts into one incident to reduce noise.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Max enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

  • 0 reports aggregated in last 24h
  • Crowdsourced baseline detection

Live signal

Status
Unknown
Monitoring
A single-runtime HTTP reachability check succeeded; no fresh official status confirms whole-service health. No current vendor status signal: vendor status was last polled on 2026-08-14, more than 7 days ago.
Coverage
Reachability and crowd signals only; not independently verifiable
Reports (24h)
0
Baseline / hour
5
Open threshold
3x

Official site

max.com