Major outage
Together AI reports a major outage that affects MiniMax M3.1 Flash. The outage is resolved. It lasted 9 minutes.
State
Resolved
Started
Lasted
9 min
Worst impact
Major outage
Timeline
2 updatesComponents degraded
9 min 100%
Updates
Times in UTCAs posted by Together AI
Affected components
1Together AI in the last 90 days
Full historyIncidents in 90 days
3
Days with an incident
3
Median duration
6 min
This incident
1.5× the median
Other Together AI incidents
All incidentsTogether AI·Major outage
Together AI reports a major outage on the Inkling component. Together AI resolved the outage. It lasted 6 minutes, from 04:51 to 04:57 UTC.
Together AI·Major outage
Together AI reports a major outage that affects the Inkling component. Together AI resolved the outage after 6 minutes.
Follow Together AI
Your coding agent knows when Together AI is down, and tells you when a failure is theirs, not yours. You can also get Together AI 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.live/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 "together" and tell me if Together AI 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.live/feed.xml?providers=together/feed subscribe https://outages.live/feed.xml?providers=togetherFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane