Groq
Groq is operational
History
Incidents in 90 days
3
Days with an incident
2
Median duration
23 min
Longest incident
6 h 5 min
Components
15Oct 12, 2026
The issues affecting **minimaxai/minimax-m2.7** have been **resolved**. The model is operating normally. Root cause: **hardware connectivity issues**. We apologize for the disruption and thank you for your patience.groqstatus.com
The **Groqcloud console issue has been resolved**. All services are operating normally. We apologize for the disruption and **appreciate your patience**.groqstatus.com
Maintenance
Follow Groq
Your coding agent knows when Groq is down, and tells you when a failure is theirs, not yours. You can also get Groq 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 "groq" and tell me if Groq 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=groq/feed subscribe https://outages.live/feed.xml?providers=groqGo from tracking outages to fixing production issues with Polylane.
Try Polylane