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 reports that the issue is resolved. The outage lasted from 30 October 2026 to 2 November 2026.
State
Resolved
Started
3 d ago
2026-10-30 15:22 UTC
Lasted
3 days
until 2026-11-02 09:27 UTC
Worst impact
Degraded
Timeline
2 updatesIdentified
3 days 100%
Updates
Times in UTCAs posted by Mistral AI
This issue has been resolved. Vibe Code Web and Vibe Work sessions are starting and resuming normally.
We identified the root cause and are working on a fix
Mistral AI in the last 90 days
Full historyIncidents in 90 days
24
Days with an incident
21
Median duration
36 min
This incident
111× the median
Other Mistral AI incidents
All incidentsMistral AI·Vibe Code Web and Vibe Work sessions may fail to start or resume
Issue is solved.
Mistral AI·Mistral Small 4 Availability Degradation
Services have been stable for a number of hours - will continue to monitor
Mistral AI·Vibe Code Web sessions failing
Vibe Code Web sessions were failing between 16:15 and 16:21 UTC due to capacity issues.
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.
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.
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.
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.
https://outages.cc/feed.xml?providers=mistral/feed subscribe https://outages.cc/feed.xml?providers=mistralFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane