PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if MiniMax is down?

PulseWatch evaluates user reports and replay-approved automated evidence for MiniMax. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported MiniMax issues today?

As of Oct 1, 2026 08:01 UTC, 0 users had reported issues with MiniMax in the previous 24 hours.

How can I report a MiniMax outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Other

Is MiniMax down right now?

UnknownOfficial status last polled Oct 1, 2026 06:48 UTCminimaxi.com Official status page

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

Is MiniMax down right now?

Unknown. MiniMax does not have a conclusive current status. The vendor reports operational; no fresh independent reachability check confirms it.

Status as of Oct 1, 2026 08:01 UTC

Unknown

MiniMax: status unknown

As of Oct 1, 2026 08:01 UTC

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

Reports 24h

Last incident

Sep 28, 2026 21:40 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 MiniMax.

Incident days

No recorded incident

2h 10m

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 MiniMax. Hover a day for detail.

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

Days with incidents

1 incident

Busiest day

2h 10m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

MiniMax outage on September 28 "," 1h 21m disruption

Sep 28, 08:18 PM → Sep 28, 09:40 PM · 1h 21m · high

A high-severity incident affected the MiniMax service. This disruption was detected via automated signals, including the vendor's own status page. The incident was resolved on September 28, 2026, at 21:40 UTC.

Peak reports

in 15 min

Total reports

during outage

Duration

1h 21m

until recovery

Impact

The MiniMax service experienced a high-severity disruption for 1 hour and 21 minutes. This incident was detected through automated monitoring and the vendor's status page. No user-reported data was collected for this incident, and therefore no information regarding specific affected features, regions, or issue types is available from user reports.

Outage timeline

Sep 28, 08:18 PM
PulseWatch detected the incident from automated vendor and probe signals (high severity)
Sep 28, 08:18 PM
Status updated: possible issue
Sep 28, 09:40 PM
Signals cleared — incident resolved

Official updates

Sep 28, 08:18 PM
MiniMax status page acknowledged the incident.
View official source

Reliability

Not measured

30-day uptime

n/a

90-day uptime

n/a

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

Other other services we monitor

Browse all

Community reports

0 comments

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

Be the first to post a report.

Incident timeline

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

Full history →

ResolvedHigh

MiniMax: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch MiniMax or have an alert rule on it can be alerted, labelled vendor-reported.

9/28/2026, 8:18:43 PM · 1h 21m

08:18 PM09:40 PM

Detection9/28/2026, 8:18:43 PM · 2d ago

Detected — high severity

ResolvedMedium