Observed incident recordDetected by RELIASTRA probes
Official status page failure window - Mistral AI
Incident aabff51e-2162-465d-9bae-235714236614 - endpoint status.mistral.ai, measured from us-east. Confirming rule: 2 consecutive failed observations counted 2 of them.
Observed window
- Opened
- 26 Sep 2026 17:10:56 UTC
- Confirmed
- 26 Sep 2026 17:15:54 UTC - the run that made the failure count reach the threshold; this record did not exist before it
- Recovered
- not recorded - open at last read
- Duration
- not recorded
What was measured
- Endpoint observed
- Official status page - https://status.mistral.ai
- Measured from
- us-east - the only observation region named in this record; nothing about other regions is claimed or inferred
- Failed observations
- 2, consecutive through the trigger set
- Failure shape
- client-visible HTTP errors (4xx) at the probed endpoint - status codes recorded: 403
- Observation references
- first 17ad1713-5dee-410d-ac61-1dc85b35051b last ab753af7-21ff-4281-86a5-0b3c9d1b3e98
The claim, in full
Between 2026-09-26T17:10:56.034848+00:00 and 2026-09-26T17:15:54.233717+00:00, RELIASTRA probes in us-east recorded 2 consecutive failed observations against https://status.mistral.ai (the observed Mistral AI target). Failure class: http_4xx; observed status: 403. This record describes the observed endpoint only and is not a statement about the vendor's services as a whole. That is all of it. Nothing about the vendor as a whole, nothing about other regions, nothing about your requests - the record you are reading is the measurement, not a narration of it.
Evidence artifact
No frozen artifact yet for this record's current state - the freeze runs shortly after a record opens or resolves, so one may appear here within minutes. The record's fields above are the claim meanwhile, exactly as the detector wrote them; nothing on this page depends on the artifact existing.
What this record does not establish
- Causation
- Not established. A 5xx can be the vendor, a shared middle path, or the probe's own egress - the record reports what came back, not why.
- Vendor acknowledgement
- Mistral AI may have recorded this window differently, later, or not at all. RELIASTRA does not ingest vendor-reported status, so no reconciliation is offered either way.
- Global reach
- This window is named for us-east. A record from one observation region never settles the question in another.
- Customer impact
- Whether your requests were affected is your measurement to make - this record carries only RELIASTRA's own probes.
Where this fits
- Mistral AI - current recordLive observatory
- All observed incidents - mistralIncident search
- Cross-vendor observed incident searchIncident search
- How RELIASTRA measures vendor reliabilityMethodology