Mistral AI reported "Conversations API Degraded" on its status page at 2026-08-28 16:59 UTC.

Mistral AI did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-08-28 16:59 UTC and ended at 2026-08-28 17:04 UTC. It lasted 5 min.

How do I get alerts for Mistral AI?

Subscribe to the Mistral AI live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Mistral AI. outages.live reads it every few minutes and keeps every update.

Mistral AIIncident · 2026-08-28 16:59 UTC

Conversations API Degraded

ResolvedOfficial update

The incident has been resolved

The latest update from Mistral AI.

State

Resolved

Started

65 d ago

2026-08-28 16:59 UTC

Lasted

5 min

until 2026-08-28 17:04 UTC

Worst impact

Degraded

Timeline

2 updates

16:5917:0017:0117:0217:04

DegradedUpdate postedTimes in UTC

Investigating

5 min 100%

Updates

Times in UTC

As posted by Mistral AI

Resolved2026-08-28 17:04 UTC

The incident has been resolved

Investigating2026-08-28 16:59 UTC

Requests to the Conversations API are experiencing degraded service. We are currently investigating.

Mistral AI in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

35 min

This incident

86% shorter than the median

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

4 h 49 min

median 35 min

90 days agoToday

Other Mistral AI incidents

All incidents

Mistral AI·Vibe Code Web and Vibe Work sessions may fail to start or resume

Issue is solved.

Resolvedresolved 2 d ago

Mistral AI·Mistral Small 4 Availability Degradation

Services have been stable for a number of hours - will continue to monitor

Resolvedresolved 9 d ago

Mistral AI·Vibe Code Web sessions failing

Vibe Code Web sessions were failing between 16:15 and 16:21 UTC due to capacity issues.

Resolvedresolved 13 d ago

Mistral AI·Vibe is experiencing high latency with GLM 5.3

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.

Resolvedresolved 13 d ago

Mistral AI·Some Vibe Code Web sessions are terminating unexpectedly or are unable to start

This incident has been resolved. Vibe Code Web sessions are now starting and running normally.

Resolvedresolved 16 d ago

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.cc/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.cc/feed.xml?providers=mistral

Slack

/feed subscribe https://outages.cc/feed.xml?providers=mistral

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane