Live

MiniMax

MiniMax is operational

Checked 3 min ago Operational

History

90 days agoToday

Incidents in 90 days

50

Days with an incident

11

Median duration

3 min

Longest incident

1 h 5 min

Components

3
Large Language Models (LLM) Operational
90 days ago11 days with an incidentToday
Text-to-Speech Operational
90 days ago1 day with an incidentToday
Video Generation Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 22, 2026

Duration3 min09:10 to 09:13Elevated errors on Large Language Models (LLM)Partial outage

This incident has been resolved.

Duration3 min09:01 to 09:04Elevated errors on Large Language Models (LLM)Partial outage

This incident has been resolved.

Duration5 min08:01 to 08:06Elevated errors on Large Language Models (LLM)Partial outage

This incident has been resolved.

Duration2 min07:58 to 08:00Elevated errors on Large Language Models (LLM)Partial outage

This incident has been resolved.

Duration3 min07:07 to 07:10Elevated errors on Large Language Models (LLM)Partial outage

This incident has been resolved.

Duration1 min07:02 to 07:03Elevated errors on Large Language Models (LLM)Partial outage

This incident has been resolved.

Duration2 min03:02 to 03:04Elevated errors on Large Language Models (LLM)Partial outage

This incident has been resolved.

Duration3 min02:56 to 02:59Elevated errors on Large Language Models (LLM)Partial outage

This incident has been resolved.

Duration6 min02:37 to 02:43Elevated errors on Large Language Models (LLM)Partial outage

This incident has been resolved.

Duration3 min02:30 to 02:33Elevated errors on Large Language Models (LLM)Partial outage

This incident has been resolved.

Duration7 min02:21 to 02:28Elevated errors on Large Language Models (LLM)Partial outage

This incident has been resolved.

Duration4 min02:16 to 02:20Elevated errors on Large Language Models (LLM)Partial outage

This incident has been resolved.

Duration1 min02:12 to 02:13Elevated errors on Large Language Models (LLM)Partial outage

This incident has been resolved.

Duration2 min02:02 to 02:04Elevated errors on Large Language Models (LLM)Partial outage

This incident has been resolved.

Duration4 min01:11 to 01:15Elevated errors on Large Language Models (LLM)Partial outage

This incident has been resolved.

Duration2 min01:02 to 01:04Elevated errors on Large Language Models (LLM)Partial outage

This incident has been resolved.

Follow MiniMax

Your coding agent knows when MiniMax is down, and tells you when a failure is theirs, not yours. You can also get MiniMax incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "minimax" and tell me if MiniMax has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=minimax
Slack
/feed subscribe https://outages.cc/feed.xml?providers=minimax

Go from tracking outages to fixing production issues with Polylane.

Try Polylane