Twitter/X "Something Went Wrong" Error: How to Fix (2026)
You try to load your timeline, post, or open a profile and X throws up a wall: "Something went wrong. Try again." The Twitter "something went wrong" error is one of the platform's most common messages, and the good news is it's almost always temporary and fixable on your end. It's usually a stale cache, a network hiccup, a rate limit, or an X server blip — not a problem with your account.
This guide explains exactly what triggers the error in 2026 and walks through the fixes in order, from the 10-second reload that solves most cases to the deeper steps for stubborn ones, on web, iPhone, and Android.
What "Something Went Wrong" Actually Means
It's a generic catch-all. X shows this message whenever a request fails for a reason it can't (or won't) explain — so the same words can mean very different things underneath. The realistic causes in 2026:
- A corrupt or stale cache on your device or browser
- A network/connection problem between you and X
- You hit a rate limit from refreshing, scrolling, or browsing too fast
- An X server outage affecting many users at once
- An outdated app or browser that's out of sync with X's backend
- A browser extension or VPN interfering with the connection
Because the message itself tells you nothing, the fastest path is to run through the common fixes in order until one sticks.
How to Fix the "Something Went Wrong" Error on X
Work top to bottom — most people are back to normal within the first three steps.
1. Reload or Restart the App
- Web: do a hard refresh with Ctrl/Cmd + Shift + R to bypass the cached page.
- iPhone/Android: swipe the X app away from the recent-apps screen to fully close it, then reopen.
A surprising share of these errors are a single failed request that clears on a clean reload.
2. Check Whether X Is Down
Before you troubleshoot your own setup, rule out a platform outage. Open a status tracker like Downdetector and search "X" or "Twitter." If reports are spiking, the issue is on X's side — the only fix is to wait it out. Trying repeatedly during an outage can make things worse by burning through rate limits.
3. Clear the Cache
A corrupt cache is the single most common fixable cause.
- Browser: clear cached images and files, then close and reopen the browser.
- Android: Settings → Apps → X → Storage → Clear cache.
- iPhone: iOS has no per-app cache clear, so offload or reinstall the app (covered below).
4. Check Your Internet Connection
Toggle Wi-Fi off and on, or switch between Wi-Fi and mobile data. On a phone, flip Airplane Mode on for 10 seconds and off to force a fresh connection. If your network is flaky, restart your router by unplugging it for ~30 seconds.
5. Disable VPN, Proxy, or Conflicting Extensions
A VPN or proxy can route you through an IP that X has rate-limited or flagged, and ad blockers or script blockers can break X's requests. Turn off your VPN and disable extensions one at a time to find the culprit, then reload.
6. Update or Reinstall the App / Browser
X updates its backend frequently, and an outdated client can fall out of sync. Check your app store or browser update menu and install any updates. If the error persists, uninstall the X app, restart your device, and reinstall it from the official store, then sign back in.
7. Log Out and Back In
Forcing a fresh authentication clears many session-related glitches that produce the error.
The Hidden Cause: You Hit a Rate Limit
One trigger deserves its own section because it's frequently misdiagnosed. X enforces rate limits — caps on how many actions you can take in a window — and when you exceed one, the platform often returns a vague "something went wrong" instead of a clear "rate limit exceeded" message.
Common ways to trip it: refreshing your timeline over and over, scrolling huge search results fast, opening many profiles in quick succession, or sharing an IP with lots of other users (corporate networks, public Wi-Fi). As of 2026, non-Premium accounts are capped at roughly 1,000 post reads per day, so heavy browsing can hit the wall.
If you suspect this, the fix is simple: stop, wait 15–60 minutes, and try again. The limit clears on a rolling window. Our full guide on Twitter rate limit exceeded covers the current caps and how to avoid them.
Platform-Specific Quick Reference
| Platform | First thing to try | If that fails |
|---|---|---|
| Web (desktop) | Hard refresh (Ctrl/Cmd+Shift+R) | Clear cache, disable extensions/VPN |
| iPhone | Force-close and reopen app | Offload or reinstall the app |
| Android | Force-close and reopen app | Clear cache in app settings |
| All platforms | Check Downdetector for outage | Wait if it's a rate limit or outage |
When "Something Went Wrong" Hides a Bigger Problem
If the error only appears on certain actions — like trying to post, follow, or log in — and your timeline otherwise loads, it may be masking a more specific issue:
- Can't post? You may be rate-limited or your account may be restricted. Our account suspended guide explains how to tell which one it is.
- Can't log in or the account won't open? It may be locked or suspended. X explains the signals of a suspended X account in its help center, and our account suspended walkthrough covers how to recover one.
- Errors plus disappearing followers or follows? The error itself is harmless, but if you also notice follower changes, that's separate — our guide on Twitter follower count not updating explains the sync glitches behind it.
If you rely on tools that read your follower data — for example a browser extension like Unfollr that works from your own X session — and X is throwing this error site-wide, wait until X recovers before scanning, since the tool reads the same page that's currently failing to load.
FAQ
What causes the "something went wrong" error on Twitter/X?
It's a generic message for any failed request: a stale cache, a network problem, a rate limit, an X server outage, an outdated app, or an interfering VPN/extension. Because it doesn't specify, the fastest approach is to run through the common fixes in order.
How do I fix "something went wrong, try again" on X?
Hard refresh (web) or force-close and reopen (mobile) first. If that fails, check Downdetector for an outage, clear your cache, check your connection, disable VPN/extensions, and update or reinstall the app. Most cases resolve in the first few steps.
Is "something went wrong" a sign my account is banned?
Usually not — it's almost always a temporary technical glitch. But if it appears only when you try to post, follow, or log in, your account may be rate-limited, locked, or restricted. Check our account suspended guide if you suspect that.
Why do I get the error only when refreshing a lot?
That's a rate limit. Refreshing, scrolling, or opening profiles too quickly trips X's per-window caps, and the platform often reports it as a vague "something went wrong." Stop for 15–60 minutes and it clears — see Twitter rate limit exceeded.
How do I know if X is down for everyone?
Open Downdetector and search "X" or "Twitter." A spike in reports means it's a platform-wide outage, in which case no local fix will help — the only solution is to wait until X resolves it on their side.
Does clearing the cache delete my account data?
No. Clearing the app or browser cache only removes temporary stored files; your account, posts, followers, and settings are all safe on X's servers. You'll just need to log in again and the app will rebuild its cache.