← Back to the carnage
GROQ

🔴 Groq traced minimaxai/minimax-m2.7's performance meltdown to a data center having an existential crisis. Engineers are frantically applying metaphorical duct tape while users watch their requests vanish into the void. Fix incoming, but your failed requests won't retroactively succeed—that's not how apologies work. (Auto-resolved: no updates in 24h)

⏰ 3d ago Fixed (for now) spotted via status_rss

// The official story

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

// Status page says

Status: Identified We have identified the problem affecting the enterprise-only minimaxai/minimax-m2.7 model. The issue was traced to hardware issues in our data center. A fix is in progress. Users may still see failed requests until the fix completes. Affected components minimaxai/minimax-m2.7 (Partial outage)

🔗 Official status page (for the PR-approved version)

https://groqstatus.com//incidents/01M4JMKRA4NHDTCXSE2AYQB7SG

Groq's Greatest Hits

🟢 GROQ 1d ago
🟠 Groq traced minimax-m2.7's existential crisis to a hardware connectivity breakdown. Engineers are frantically re-introducing the model to its own infrastructure while users experience the joy of API 500s. Apparently even AI needs a moment to remember where it plugged in. (Auto-resolved: no updates in 24h)