outages.live
Live
GroqIncident · 2026-10-12 18:17 UTC

Model Performance or Availability Issue

ResolvedOfficial update

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.

The latest update from Groq.

State

Resolved

Started

20 d ago

2026-10-12 18:17 UTC

Lasted

18 min

until 2026-10-12 18:36 UTC

Worst impact

Partial outage

Timeline

2 updates
18:1718:2218:2718:3118:36
Partial outageUpdate postedTimes in UTC

Identified

18 min 100%

Updates

Times in UTC

As posted by Groq

Resolved2026-10-12 18:36 UTC

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.

Identified2026-10-12 18:17 UTC

We have **identified the problem** affecting the **minimaxai/minimax-m2.7** service. The issue was traced to **hardware connectivity issues**. A fix is in progress. Users may still see **API failures** until the fix completes.

Groq in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

3

Days with an incident

2

Median duration

23 min

This incident

21% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

6 h 5 min
median 23 min
90 days agoToday

Other Groq incidents

All incidents

Groq·GroqCloud Console Errors Affecting Multiple Regions

The **Groqcloud console issue has been resolved**. All services are operating normally. We apologize for the disruption and **appreciate your patience**.

Resolvedresolved 20 d ago

Groq·Model Performance or Availability Issue - minimaxai/minimax-m2.7

The issues affecting **minimaxai/minimax-m2.7** have been **resolved**. The model is operating normally. Root cause: **Data center hardware issues**. We apologize for the disruption and thank you for your patience.

Resolvedresolved 22 d ago

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.

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 "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.

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane