Official incident history

  1. Mistral AI: degraded performance

    Provider's original title: Vibe Work issues with GLM 5.3 Short

    Started: · Duration: still open
    Provider updates (2)
    1. Investigating “Vibe Work users may face intermittent issues - cause identified and mitigation in progress”
    2. Monitoring “Performance healing - monitoring and continuing to apply improvements”
    Open
  2. Mistral AI: outage or errors

    Provider's original title: Mistral Small 4 Server-side errors

    Started: · Duration: 67 min
    Provider updates (6)
    1. Investigating “We are experiencing server-side errors on Mistral Small 4 and are actively investigating.”
    2. Monitoring “We have identified the issue and implemented a fix. The service has been mitigated and we are monitoring for full recovery.”
    3. Resolved “The incident has been resolved.”
    4. Investigating “We are investigating partial degradation affecting mistral-small-2603, causing intermittent server-side errors. We are actively working to identify and resolve the issue.”
    5. Monitoring “We have implemented a fix and are actively monitoring model health.”
    6. Resolved “The partial outage has been resolved.”
    Resolved
  3. Mistral AI: outage or errors

    Provider's original title: OCR 4.1 Server-side errors

    Started: · Duration: 30 min
    Provider updates (2)
    1. Investigating “We're seeing elevated latency and intermittent server-side errors affecting OCR models (OCR 3, OCR 4.1, OCR-2512). We're actively investigating and working on mitigation.”
    2. Resolved “The partial outage affecting OCR has been resolved.”
    Resolved
  4. Mistral AI: outage or errors

    Provider's original title: Vibe Work is experiencing errors with GLM 5.3

    Started: · Duration: 33 min
    Provider updates (3)
    1. Identified “We have identified the issue and are working on a fix.”
    2. Monitoring “We're monitoring the deployments.”
    3. Resolved “The issue affecting GLM 5.3 short and GLM 5.2 has been resolved. Success rates are back to normal.”
    Resolved
  5. Started: · Duration: 3956 min
    Provider updates (3)
    1. Investigating “We identified the root cause and are working on a fix”
    2. Identified “We identified the root cause and are working on a fix”
    3. Resolved “This issue has been resolved. Vibe Code Web and Vibe Work sessions are starting and resuming normally.”
    Resolved
  6. Started: · Duration: 217 min
    Provider updates (3)
    1. Investigating “We identified the root cause and are working on a fix.”
    2. Monitoring “We have applied a mitigation and are now monitoring the situation.”
    3. Resolved “Issue is solved.”
    Resolved
  7. Mistral AI: degraded performance

    Provider's original title: Mistral Small 4 Availability Degradation

    Started: · Duration: 165 min
    Provider updates (3)
    1. Investigating “Investigating reports of a high failure rate on Mistral Small 4 (MS4).”
    2. Monitoring “Service healing, monitoring stability”
    3. Resolved “Services have been stable for a number of hours - will continue to monitor”
    Resolved
  8. Mistral AI: outage or errors

    Provider's original title: Vibe Code Web sessions failing

    Started: · Duration: 0 min
    Provider updates (1)
    1. Resolved “Vibe Code Web sessions were failing between 16:15 and 16:21 UTC due to capacity issues.”
    Resolved
  9. Mistral AI: increased latency

    Provider's original title: Vibe is experiencing high latency with GLM 5.3

    Started: · Duration: 68 min
    Provider updates (3)
    1. Investigating “We are investigating the issue.”
    2. Identified “We have identified the issue and are working on a fix”
    3. Resolved “The issue causing elevated latency and errors for Vibe sessions using GLM 5.3 has been resolved. Service performance has returned to normal, and we are continuing to monitor.”
    Resolved
  10. Started: · Duration: 24 min
    Provider updates (3)
    1. Identified “We identified the root cause and are working on a fix.”
    2. Monitoring “We are monitoring recovery.”
    3. Resolved “This incident has been resolved. Vibe Code Web sessions are now starting and running normally.”
    Resolved
  11. Mistral AI: outage or errors

    Provider's original title: Fixed errors on workflow APIs

    Started: · Duration: 22 min
    Provider updates (2)
    1. Investigating “Currently investigating.”
    2. Resolved “Fixed the root cause.”
    Resolved
  12. Mistral AI: outage or errors

    Provider's original title: Total Unavailability on ML4 GLM5.2 and GLM5.3

    Started: · Duration: 0 min
    Provider updates (1)
    1. Resolved “GLM 5.2, GLM 5.3, and Mistral Large 4 were unavailable from 2026-10-12 12:48:31 UTC to 2026-10-12 13:01:10 UTC.”
    Resolved
  13. Started: · Duration: 171 min
    Provider updates (4)
    1. Investigating “We are investigating an issue causing some Vibe Code Web sessions to stop unexpectedly during execution. Our team is working to identify and mitigate the issue. We will provide updates as they become available. ”
    2. Identified “We have identified the issue and are working on a fix.”
    3. Monitoring “We have deployed a fix and are monitoring.”
    4. Resolved “The issue causing some Vibe Code Web sessions to terminate unexpectedly has been resolved.”
    Resolved
  14. Mistral AI: degraded performance

    Provider's original title: Elevated error rate on some of our services

    Started: · Duration: 160 min
    Provider updates (4)
    1. Investigating “We identified an elevated error rate on some of our surfaces (Vibe, Studio, Settings page). Investigations are ongoing”
    2. Identified “Root cause has been identified. Services are coming back up.”
    3. Monitoring “Metrics are back to normal. We are still monitoring the services actively.”
    4. Resolved “All services are now back to normal”
    Resolved
  15. Mistral AI: degraded performance

    Provider's original title: Audio speech to text degradation

    Started: · Duration: 21 min
    Provider updates (2)
    1. Investigating “There is a degradation affecting the audio STT models.”
    2. Resolved “The audio STT model degradation has been resolved.”
    Resolved
  16. Mistral AI: outage or errors

    Provider's original title: Skill creation and updates unavailable

    Started: · Duration: 28 min
    Provider updates (2)
    1. Investigating “We are investigating an issue preventing users from creating or updating skills in Le Chat and AI Studio.”
    2. Resolved “We have deployed a fix restoring skill creation and updates in Le Chat and AI Studio.”
    Resolved
  17. Mistral AI: degraded performance

    Provider's original title: Mistral OCR 4 is degraded

    Started: · Duration: 21 min
    Provider updates (2)
    1. Investigating “We are currently investigating degraded availability on Mistral OCR 4.”
    2. Resolved “We've rolled out a fix for the degradation and availability has recovered”
    Resolved
  18. Started: · Duration: 14 min
    Provider updates (2)
    1. Investigating “We are currently investigating elevated error rates on Mistral Small 4.”
    2. Resolved “The incident has been resolved.”
    Resolved
  19. Started: · Duration: 163 min
    Provider updates (2)
    1. Investigating “Our team is currently investigating elevated error rates for Mistral OCR 4 models.”
    2. Resolved “The incident has been resolved.”
    Resolved
  20. Mistral AI: degraded performance

    Provider's original title: Vibe Work - Degraded output quality

    Started: · Duration: 5 min
    Provider updates (2)
    1. Investigating “We are investigating reports of Vibe Work generating incoherent/incorrect responses.”
    2. Resolved “We’ve identified the issue and rolled out a fix.”
    Resolved

What the provider published about this service, with the provider's own updates (wording quoted as published).

Evidence

Official
Mistral AI Status ↗ · Minor service outage · Nov 19, 11:12 PM UTC

Why this assessment

  • Provider reports: “Minor service outage”

Rule set assess-1. The same evidence always gives the same result.

Evidence and freshness

Each source separately: who says it, when it was last observed, and whether it is recent enough to be used.

SourceLast observedAgeUsed in assessment
Official1 min agoYes, recent

Technical details

Affected components (provider)

The provider lists no degraded components.

Official status page ↗