Mistral AI reported "Vibe Work is experiencing errors with GLM 5.3" on its status page at 2026-11-11 12:09 UTC. Vibe Work had errors with GLM 5.3 and GLM 5.2. Mistral AI identified the issue and monitored the fix. The outage is resolved and lasted 24 minutes.

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-11-11 12:09 UTC and ended at 2026-11-11 12:33 UTC. It lasted 24 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. A language model writes the summary from those updates.

Mistral AIIncident ·

Vibe Work is experiencing errors with GLM 5.3

ResolvedOfficial update

Vibe Work had errors with GLM 5.3 and GLM 5.2. Mistral AI identified the issue and monitored the fix. The outage is resolved and lasted 24 minutes.

State

Resolved

Started

Lasted

24 min

Worst impact

Partial outage

Timeline

3 updates

12:0912:1512:2112:2712:33

Partial outageUpdate postedTimes in UTC

Identified

21 min 89%

Monitoring

3 min 11%

Updates

Times in UTC

As posted by Mistral AI

Resolved

The issue affecting GLM 5.3 short and GLM 5.2 has been resolved. Success rates are back to normal.

Monitoring

We're monitoring the deployments.

Identified

We have identified the issue and are working on a fix.

Mistral AI in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

36 min

This incident

33% shorter than the median

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

3 days

median 36 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

Vibe Code Web and Vibe Work sessions did not start or resume. Mistral AI reported that the issue is resolved. It lasted from 30 October 2026 to 2 November 2026.

Resolved

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

Issue is solved.

Resolved

Mistral AI·Mistral Small 4 Availability Degradation

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

Resolved

Mistral AI·Vibe Code Web sessions failing

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

Resolved

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.

Resolved

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