If chat.mistral.ai isn't loading, start with the basics: clear your browser cache, disable extensions (especially ad blockers), and try a different browser. Chromium-based browsers tend to work most reliably. If the issue persists across browsers, check whether your DNS resolver is causing delays — switching to 8.8.8.8 or 1.1.1.1 often helps.
Failed login attempts usually come down to a few things:
If you're hitting the API and getting 429 errors, you've exceeded your rate limit. Back off and retry with exponential delay. For 500-level errors, the issue is server-side — retry after a short wait. Hanging requests with no response usually point to a timeout setting on your end; set an explicit timeout in your HTTP client rather than waiting indefinitely.
Card declines on the billing page are often caused by your bank flagging an unfamiliar merchant. Contact your bank to approve the transaction, or try a different card. Make sure the billing address matches exactly what your bank has on file — even a minor mismatch can trigger a rejection. If the payment page itself freezes after you click confirm, do not click again; wait and check your email for a confirmation before retrying to avoid duplicate charges.
Streaming responses that cut off abruptly usually indicate a connection drop between your client and the server. If you're using the web interface, a simple page refresh and resending the prompt resolves it most of the time. In API integrations, implement proper stream error handling and reconnect logic rather than assuming the stream will always complete cleanly.
After extended use, the chat interface can accumulate enough state in memory to become sluggish or unresponsive. Starting a new conversation thread rather than continuing an extremely long one keeps things running smoothly. If the interface is fully frozen, a hard reload (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) clears the JS state without losing your account session.