ModelClockminimax-m3 deprecation and shutdown dates on every platform
minimax-m3 is tracked on 6 providers and hosting routes. First to go: Together AI shuts down MiniMaxAI/MiniMax-M3 on Nov 6, 2026.
Together AI
| Date | Model | Status | Replacement | Source |
|---|---|---|---|---|
MiniMaxAI/MiniMax-M3 | Shuts down11 days | MiniMaxAI/MiniMax-M3.1-Flash | Notice ↗ |
Impossibl
| Date | Model | Status | Replacement | Source |
|---|---|---|---|---|
| — | minimaxai/minimax-m3 | No deprecation notice tracked | None published | Notice ↗ |
MiniMax
| Date | Model | Status | Replacement | Source |
|---|---|---|---|---|
| — | MiniMax-M3 | No deprecation notice tracked | None published | Notice ↗ |
AssemblyAI
| Date | Model | Status | Replacement | Source |
|---|---|---|---|---|
| — | minimax-m3 | No deprecation notice tracked | None published | Notice ↗ |
Fireworks AI
| Date | Model | Status | Replacement | Source |
|---|---|---|---|---|
| — | MiniMax M3 | No deprecation notice tracked | None published | Notice ↗ |
Ofox
| Date | Model | Status | Replacement | Source |
|---|---|---|---|---|
| — | MiniMax M3 | No deprecation notice tracked | None published | Notice ↗ |
Every provider sets its own dates
A deadline on one platform says nothing about another: OpenAI, Azure, Amazon Bedrock, Google Vertex AI and model routers each retire their own copies on their own schedule. Snapshots of the same model (for example dated versions) are listed separately because each has its own date. Rows marked “No deprecation notice tracked” mean ModelClock has not seen a retirement notice for that route, not that one cannot exist.