Discord won't connect. ChatGPT says "Something went wrong." YouTube spins forever. The first question is always the same: is the service down, or is it my account, my app or my connection?
Apps make this harder than websites. They hide the real error behind friendly messages, they retry silently, and they often half-work: you can log in but messages don't send. This guide shows how to get a reliable answer in about a minute, and what to do in each case.
Step 1: Check the official status page
Almost every large service publishes a status page that lists its components and any open incidents. A few you'll use often:
| Service | Status page |
|---|---|
| Discord | discordstatus.com |
| ChatGPT / OpenAI | status.openai.com |
| GitHub | githubstatus.com |
| Slack | slack-status.com |
| Zoom | status.zoom.us |
| Cloudflare | cloudflarestatus.com |
For anything else, search for "service name status" or look in the help center footer.
How to read them:
- Look at components, not just the banner. "Partial outage" on "Voice" or "Image generation" explains a lot even if the overall banner is green.
- Check the incident timestamps. An incident opened 3 minutes ago is very likely what you're seeing.
- Don't trust "all green" in the first half-hour. Status pages are updated by people during an incident. The first reports from users often come 10 to 30 minutes before the page changes.
Step 2: Check an independent outage tracker
Because official pages lag, an outside view helps. Independent trackers test services from their own servers and show live status without waiting for the company to confirm. upordown.online tracks more than 130 popular services in one place and lets you test any other site, which is handy when you're not sure whether it's one app or a wider problem, such as a cloud or CDN provider taking several apps down at once.
When several unrelated apps fail at the same moment, suspect a shared provider (a major cloud region, a CDN or a DNS provider) or your own connection.
Step 3: Look for other users reporting it
Real-time user reports are often the very first signal:
- Search the service's name plus "down" on social media and sort by latest. A burst of posts within the last few minutes is a strong sign.
- Check the service's official support account; many post incident updates there first.
- Look at the service's subreddit or community forum, where "is it down for anyone else?" threads appear quickly.
One or two posts mean little. Dozens in ten minutes, from different countries, mean a real outage.
Step 4: Decode the app's error message
Apps often reveal more than you think:
- Discord "Connecting…" or "RTC Connecting" that never finishes: the gateway or voice servers aren't reachable. If text works but voice doesn't, it's usually a voice region problem or your firewall/VPN blocking UDP.
- Discord "Awaiting endpoint": voice server for that region is struggling. Server admins can change the voice region in the channel settings to test.
- ChatGPT "Something went wrong" / "Network error": often a backend issue or a long response that timed out. If short prompts work and long ones fail, it's load, not your network.
- ChatGPT "Too many requests" or usage limit messages: that's your account's limit, not an outage.
- HTTP 502, 503, 504 in a browser version of the app: the service's servers are failing. That's an outage on their side.
- "You're offline" while other apps work: the app's own connection check is failing, which points to the service or a blocked domain on your network.
Step 5: Rule out your own side in two minutes
If the status page and outside trackers say everything is fine, it's probably local. Work through these in order:
- Switch networks. Turn off Wi-Fi on your phone and try on mobile data. If it works there, your Wi-Fi, router or ISP is involved.
- Try the web version. Open the service in a browser (for example the web versions of Discord or ChatGPT). If the web works and the app doesn't, update or reinstall the app.
- Disable VPN, proxy and ad-blockers. These frequently block the domains apps use for real-time connections.
- Log out and back in. Expired sessions produce vague "something went wrong" errors.
- Restart the app fully. On desktop, quit it from the system tray or menu bar, not just the window. On mobile, swipe it away and reopen.
-
Clear the app's cache. Discord on Windows keeps its cache in
%AppData%\discord\Cache; on macOS in~/Library/Application Support/discord/Cache. Quit Discord, delete the folder's contents, and reopen. On Android, Settings → Apps → the app → Storage → Clear cache. - Check the date and time. A wrong system clock breaks secure connections. Turn on automatic time.
A quick command-line check also helps on desktop. If the service's address resolves and responds, your machine can reach it:
curl -sS -o /dev/null -w "%{http_code}\n" https://discord.com
On Windows, run the same line in PowerShell as curl.exe instead of curl. A 200, 301 or 403 response means the network path works and the issue is in the app or your account. Could not resolve host or a timeout points to your network.
Step 6: If it really is down, work around it
- Don't keep reinstalling. It won't help and may log you out of everything.
- Avoid hammering retry. Repeated sends can create duplicate messages or posts when the service recovers.
- Save your work. In ChatGPT, copy long prompts somewhere before resubmitting.
- Use a backup channel. For teams, agree on a fallback (email, a second chat app) for when the main tool goes down.
- Watch, don't refresh. Subscribe to the status page's email or RSS updates, or keep a live tracker open, and get on with something else.
FAQ
How do I know if Discord is down or just me?
Check discordstatus.com and an independent tracker. If both look normal, try Discord in a browser on mobile data. If that works, the issue is your app, network or VPN.
Why does ChatGPT say "Something went wrong"?
It's usually a temporary server-side error or a request that took too long. Check the status page, retry with a shorter prompt, start a new chat, or log out and back in.
Can an app be down in one country only?
Yes. Outages often hit one region, one data center or one ISP's route to the service. That's why reports from many locations matter more than one person's experience.
Why is the status page green when the app isn't working?
Status pages are usually updated manually and often lag the real problem. Partial or regional issues may never appear as a full outage.
How long do outages of big apps usually last?
Most resolve in under an hour. Major incidents can last a few hours. The status page's incident history shows how long past ones took.
Top comments (0)