MiniMax
MiniMax is operational
History
Incidents in 90 days
50
Days with an incident
11
Median duration
3 min
Longest incident
1 h 5 min
Components
3Oct 27, 2026
Oct 22, 2026
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
Oct 21, 2026
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
Oct 20, 2026
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
Oct 19, 2026
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
Oct 17, 2026
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
Oct 16, 2026
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
This incident has been resolved.status.minimax.io
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.
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.
https://outages.cc/feed.xml?providers=minimax/feed subscribe https://outages.cc/feed.xml?providers=minimaxGo from tracking outages to fixing production issues with Polylane.
Try Polylane