Is Mistral AI down?
Right now
No. Mistral AI is operational.
Mistral AI API edge answers UpButler's independent probe; no machine-readable official status.
No official machine-readable status
For agents
proceed
Proceed.
GET upbutler.com/status/mistral/status.agent.json
MCP: upstream_status {"service":"mistral"}
La Plateforme and the Mistral model API.
What Mistral AI reports
status.mistral.ai sits behind a browser challenge; we do not work around it. Only the independent probe is shown.
Their status page: status.mistral.aiUpButler's independent probe
API edge is answeringHTTP 401 · 35 ms
One request without credentials to api.mistral.ai every two minutes. An answer (the expected "not authenticated") shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.
Checked · up since 2026-10-10 01:23 UTC
Mistral AI incidents, last 90 days
Without a machine-readable source there is no incident history to show. Mistral AI keeps its own at status.mistral.ai.
Tell your outage from Mistral AI's
Declare that your project depends on Mistral AI. When one of your monitors fails while Mistral AI has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- mistralcurl -s https://upbutler.com/status/mistral/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "mistral",
"verdict": "proceed",
"status": "operational",
"reason": "Mistral AI API edge answers UpButler's independent probe; no machine-readable official status",
"retryAfterSec": null,
"incident": null,
"probe": {
"state": "up",
"statusCode": 401
}
}Questions
- Is Mistral AI down right now?
- No. As of 2026-10-10 05:12 UTC, Mistral AI is operational. This page reads the status again every 2 minutes.
- Where does this status come from?
- status.mistral.ai sits behind a browser challenge; we do not work around it. Only the independent probe is shown.
- What does UpButler's own Mistral AI check prove?
- Every two minutes UpButler sends one request without credentials to the Mistral AI API edge (api.mistral.ai). Any answer from the edge, usually HTTP 401, shows that DNS, TLS and routing work. It does not prove that authenticated requests succeed, so it can say "reachable" while Mistral AI reports degraded service. It is useful the other way round: when the probe fails before their status page changes.
- How can my agent or app check Mistral AI status?
- Fetch https://upbutler.com/status/mistral/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"mistral"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Mistral AI's?
- Add "mistral" to the dependencies of your UpButler workspace. When one of your monitors fails while Mistral AI has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in ai models and tooling
UpButler is not affiliated with Mistral AI. Status and incident text belong to Mistral AI and are read from their public status source; the probe result is UpButler's own measurement.