Mistral

Impact-weighted uptime

Mistral published 2.8 incidents per 30 days on average to its status feed across the last 6 months (n=17). We surface this number instead of classifying providers because uptime feeds vary in publishing volume for reasons we cannot judge from outside; compare the uptime numbers below across providers with this denominator in mind.

Uptime weighted by per-incident UIS over the window, computed from incidents this provider published to its own feed. n splits into live (observed in real time) and historical (re-derived from the provider's own archive). Not directly comparable across providers — see the feed-volume disclosure above. How this is computed.

Multi-region reachability + latency

Published SLA compliance

Component classification · 10 rules

Components classified by class (primary inference, secondary API, auxiliary). Flagship models tracked: 3.

Latency probe · parallel-run, methodology v1.0

Alt-signal observations · last 24 hours

Unconfirmed signal observations from the last 1440 minutes. None are published incidents; they corroborate confirmed incidents and feed the multi-source gate. Single-source signal is intentionally not auto-posted.

Per-model community reports · last 24 hours

Per-model claims are gated: published only when the provider names the model OR at least two GitHub SDK issues name it with an HTTP 5xx pattern within 30 minutes. Other mentions are surfaced as community reports without a per-model claim.