Live

Mistral Small 4 Server-side errors

0

Mistral Small 4 had intermittent server-side errors. Mistral AI reported the incident as resolved after 3 hours and 22 minutes.

State

Resolved

Started

Lasted

3 h 22 min

Worst impact

Degraded

Timeline

5 updates
16:1517:0617:5618:4719:37
DegradedNoticeUpdate postedTimes in UTC

Investigating

2 h 21 min 70%

Resolved

18 min 9%

Monitoring

44 min 22%

Updates

Times in UTC

As posted by Mistral AI

Resolved

The partial outage has been resolved.

Monitoring

We have implemented a fix and are actively monitoring model health.

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.

Resolved

The incident has been resolved.

Investigating

We are experiencing server-side errors on Mistral Small 4 and are actively investigating.

Mistral AI in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

25

Days with an incident

21

Median duration

38 min

This incident

5.4× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

3 days
median 38 min
90 days agoToday

Other Mistral AI incidents

All incidents

Follow Mistral AI

Your coding agent knows when Mistral AI is down, and tells you when a failure is theirs, not yours. You can also get Mistral AI incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "mistral" and tell me if Mistral AI has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=mistral
Slack
/feed subscribe https://outages.live/feed.xml?providers=mistral

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane