Mistral API status
How fast the Mistral API starts answering from 6 cities, checked every 30 minutes.
- AI API
- Mistral AI
- mistral-medium-latest
Last checked Every 30 minutes
Collecting a baseline
Collecting a first visible token baseline for Mistral API from Amsterdam.
- Typical time to first token
- 373 ms
- Last 24 hours · usually 351 ms
- Slower time to first token
- 579 ms
- 95% of checks came in under this
- Failed requests
- 0
- Out of 828 requests in 24 hours
- Open incidents
- 0
- None right now
Mistral API by city
The latest time to first token from each test location against its usual value. Each mark in the strip is one check.
| City | Status | Now | Usual | Last 24 hours |
|---|---|---|---|---|
| Collecting baseline | 299 ms | 248 ms | ||
| Collecting baseline | 414 ms | 362 ms | ||
| Collecting baseline | 293 ms | 313 ms | ||
| Collecting baseline | 485 ms | 406 ms | ||
| Collecting baseline | 444 ms | 444 ms | ||
| Collecting baseline | 344 ms | 340 ms |
- Normal
- Slower than usual
- Some requests failed or degraded
- No check, or ours couldn't be verified
Colours compare each city with its own usual value, not with other services or cities. In the strip, grey marks are normal checks.
Last 24 hours
Time to first token for each check, as the median across all cities.
Recent incidents
All incidents →- Slower than usualAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal
, lasted 3.5 hours · peak 769 ms, usually 443 ms
Brief slowdowns in our checks
Two or more slow checks in a row over the last seven days that didn't last long enough to count as an incident.
- Amsterdam · slower for about an hour · peak 480 ms, usually 245 ms
How these checks work
- Every 30 minutes, each of our 6 test locations sends 3 requests to every service on this page.
- We compare each result with the same city's usual value over the last 7 days. A city is slower than usual above 1.5× that value (and at least 100 ms more), and degraded above 2.5×.
- If 10% or more of a city's recent requests fail, it shows "Some requests failed"; from 25% it is degraded.
- One city has to stay that way for 90 minutes before we show it. When 3 or more cities see it at the same time, we show it straight away. It takes 90 minutes of normal checks to clear.
- Each city also fetches two small files from two unrelated networks. If both are slow too, the problem is most likely on our side, and we say so instead of blaming the service.
How fast is your API around the world?
Run a free speed test from multiple cities and find out where your users are waiting. No setup, no account required.
No account required · Takes about 30 seconds.