Groq Cloud incident

meta-llama/llama-4-scout-17b-16e-instruct Degraded Performance

Minor Resolved View vendor source →

Groq Cloud experienced a minor incident on February 5, 2026 affecting meta-llama/llama-4-scout-17b-16e-instruct, lasting —. The incident has been resolved; the full update timeline is below.

Started
Feb 05, 2026, 06:32 PM UTC
Resolved
Feb 05, 2026, 06:32 PM UTC
Duration
Detected by Pingoru
Feb 05, 2026, 06:32 PM UTC

Affected components

meta-llama/llama-4-scout-17b-16e-instruct

Update timeline

  1. investigating Feb 05, 2026, 06:09 PM UTC

    Status: Investigating We are currently investigating reports of an issue with meta-llama/llama-4-scout-17b-16e-instruct. Users may be experiencing elevated error rates and or slow responses. Other models remain operational. Our team is analyzing logs and infrastructure to identify the cause. Affected components meta-llama/llama-4-scout-17b-16e-instruct (Degraded performance)

  2. monitoring Feb 05, 2026, 06:21 PM UTC

    Status: Monitoring meta-llama/llama-4-scout-17b-16e-instruct and performance is improving. We’re now monitoring the model to ensure stability. If all remains normal, we will resolve the incident in the next update. Affected components meta-llama/llama-4-scout-17b-16e-instruct (Operational)

  3. resolved Feb 05, 2026, 06:32 PM UTC

    Status: Resolved The issues affecting meta-llama/llama-4-scout-17b-16e-instruct have been resolved. The model is once again operating normally. We apologize for the disruption and thank you for your patience. Affected components meta-llama/llama-4-scout-17b-16e-instruct (Operational)