‹ Back to incident history

Model Performance or Availability Issue

ResolvedMajor outageGroq
Tuesday, October 13, 2026 02:17 – Tuesday, October 13, 2026 02:36 (18 min)
Affected components
Preview Models / minimaxai/minimax-m2.7
Updates
IdentifiedTuesday, October 13, 2026 02:17

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.

maintenance_scheduledSaturday, October 25, 2025 02:25

When: Monday, Nov 3, 2025 • 00:00 to 03:00 UTC (Sunday, Nov 2, 16:00 to 19:00 PT) What • We’re performing planned maintenance on the me-central-1 deployment of meta-llama/llama-4-maverick-17b-128e-instruct to keep systems current. Other regions remain available. Impact • No customer action required. • Requests that explicitly target the me-central-1 endpoint for this model will be unavailable for approximately 2 hours within the window, possibly longer if troubleshooting is required. • Requests not pinned to me-central-1 will continue to be served by other regions. Updates • We will post at start, after the change completes, and when monitoring finishes.

Incident data from the Groq official status page:Read the official incident

About this data

Where does the incident data for Groq come from?

Data comes from the Groq official status page, syncs every 5 minutes, and covers 90 days. The detail page links to the original report.

How do I read the component status bars?

Each block is one day. Green means no issue was reported, yellow means degraded performance, red means a major outage, and gray means no data. Availability covers the last 90 days.

Why is history missing for some services?

Only services with a public official status page are included.

How is duration calculated?

Duration runs from the official start time to recovery, or to the current time for ongoing incidents. Incidents spanning multiple days appear on each affected day.

See the full service list and live status in the status overview