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

What to do

• Check whether your product depends on Groq. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 6h 5m it lasted.

  Anything that failed between 2026-10-10 10:09 UTC and 2026-10-10 16:14 UTC may need a replay.

• Subscribe to Groq's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=groq works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Groq 2

1. identifiedOct 10, 2026, 10:09 AM UTC

   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.

   provider

2. resolvedOct 10, 2026, 4:14 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.