Open
Mistral · Incident record · Jun 3, 17:01 UTC

Elevated error rate on Mistral 3-5

21/100
User-Impact Score · Degraded
2026-06-03 20:09 UTC — UIS 21
startednow

150h 12m · Mistral · scope unspecified · single-source — not confirmed.

Cite this incidentBibTeX · APA · MLA · Chicago · RIS
ai-receipts. (2026, June 3). Elevated error rate on Mistral 3-5 [Incident record, methodology v1.0]. ai-receipts. https://aireceipts.org/incidents/mistral:99c40f9c-8e97-4c1d-bab7-333ace873a9a
Embed this incidentiframe · CC-BY-4.0
<iframe src="https://aireceipts.org/incidents/mistral:99c40f9c-8e97-4c1d-bab7-333ace873a9a?embed=1" title="Mistral: Elevated error rate on Mistral 3-5 — ai-receipts incident record" width="100%" height="420" loading="lazy" style="border:1px solid #e4e4e7"></iframe>
<p><a href="https://aireceipts.org/incidents/mistral:99c40f9c-8e97-4c1d-bab7-333ace873a9a">Source: ai-receipts</a> · CC-BY-4.0</p>

Data record

UIS
21/100
Status
monitoring
Started (UTC)
2026-06-03 17:01
Duration
150h 12m
Components
Chat Completions API, Le Chat
Scope
scope unspecified — see methodology limitations
Confirmation
Unconfirmed — single source or weak corroboration only.
Methodology
v1 · how this score was computed · provider status page

Evidence chain

  1. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  2. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  3. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  4. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  5. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  6. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  7. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  8. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  9. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  10. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  11. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  12. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  13. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  14. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  15. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  16. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  17. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  18. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  19. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  20. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  21. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  22. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  23. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  24. Jun 3, 17:01 UTC
    [investigating]

    We are investigating the issue.

    permalink
  25. Jun 3, 17:44 UTC
    [monitoring]

    A fix has been implemented and we are monitoring the results.

    permalink
  26. Jun 3, 17:44 UTC
    [monitoring]

    A fix has been implemented and we are monitoring the results.

    permalink
  27. Jun 3, 17:44 UTC
    [monitoring]

    A fix has been implemented and we are monitoring the results.

    permalink
  28. Jun 3, 17:44 UTC
    [monitoring]

    A fix has been implemented and we are monitoring the results.

    permalink
  29. Jun 3, 17:44 UTC
    [monitoring]

    A fix has been implemented and we are monitoring the results.

    permalink
  30. Jun 3, 17:44 UTC
    [monitoring]

    A fix has been implemented and we are monitoring the results.

    permalink
  31. Jun 3, 17:44 UTC
    [monitoring]

    A fix has been implemented and we are monitoring the results.

    permalink
  32. Jun 3, 17:44 UTC
    [monitoring]

    A fix has been implemented and we are monitoring the results.

    permalink
  33. Jun 3, 17:44 UTC
    [monitoring]

    A fix has been implemented and we are monitoring the results.

    permalink
  34. Jun 3, 17:44 UTC
    [monitoring]

    A fix has been implemented and we are monitoring the results.

    permalink
  35. Jun 3, 17:44 UTC
    [monitoring]

    A fix has been implemented and we are monitoring the results.

    permalink
  36. Jun 3, 17:44 UTC
    [monitoring]

    A fix has been implemented and we are monitoring the results.

    permalink
  37. Jun 3, 17:44 UTC
    [monitoring]

    A fix has been implemented and we are monitoring the results.

    permalink
  38. Jun 3, 17:44 UTC
    [monitoring]

    A fix has been implemented and we are monitoring the results.

    permalink
  39. Jun 3, 17:44 UTC
    [monitoring]

    A fix has been implemented and we are monitoring the results.

    permalink
  40. Jun 3, 17:44 UTC
    [monitoring]

    A fix has been implemented and we are monitoring the results.

    permalink