Is DeepSeek Down? Live status & outage reports

Service info and troubleshooting

Site Won't Load or Times Out

If the page just spins or throws a connection error, the issue is almost always on the network side. Try switching from Wi-Fi to mobile data or the other way around. Clear your browser cache — stale cookies can block the handshake with the server. If you're on Chrome, disable extensions one by one; ad blockers sometimes interfere with API calls the interface depends on.

Chat Responses Stop Mid-Generation

This happens when the connection drops during a long output. It's not a bug in the model — it's a timeout. Reload the page and resend the message. If it keeps cutting off, try a shorter prompt or break your request into smaller parts. Switching to a wired connection usually solves it for good.

Login Errors and Account Access Issues

• Double-check that Caps Lock is off before entering your password
• If you use Google or Apple sign-in, make sure third-party cookies are enabled in your browser
• A 'session expired' error means you need to log out completely, clear cookies for the domain, and sign in again
• If the verification email never arrives, check your spam folder and whitelist the sender domain

App Crashes or Freezes on Mobile

The DeepSeek mobile app tends to freeze when the phone is low on RAM. Close background apps, then reopen it. If crashes are frequent, go to Settings, clear the app cache, and check whether an update is available — most stability fixes ship quietly without announcements.

Messages Not Sending in the Interface

If the send button does nothing or the message just disappears, the session has likely lost its connection to the backend. Refresh the tab. If the problem repeats, open DevTools (F12), go to the Console tab, and look for CORS or 403 errors — those point to a temporary server-side restriction that usually clears within minutes.

Slow Responses and High Latency

Peak hours — typically late evening UTC — hit the free tier hardest. If replies take 30+ seconds, it's server load, not your setup. The practical fix is to work during off-peak hours or, if the task is urgent, switch to the API with a paid key, which sits on a separate queue.

Generated Content Fails to Display

Sometimes a response renders as a blank block. This is a known rendering glitch tied to certain markdown combinations. Click inside the response area and hit Ctrl+A, then Ctrl+C — the text is usually there, just invisible. Pasting it into a plain text editor confirms it. A hard refresh (Ctrl+Shift+R) fixes the display for the next request.