โ Back to the carnage
GROQ
๐ 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)
// The official story
Model Performance or Availability Issue
// Status page says
Status: Identified 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. Affected components minimaxai/minimax-m2.7 (Partial outage)
๐ Official status page (for the PR-approved version)
https://groqstatus.com//incidents/01M4RNBH8R850TCY7FTW0VBJ1TGroq's Greatest Hits
๐ข GROQ
3d ago
๐ด 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)