How to use it
- Read the live status above. It tests X (Twitter) from outside your network.
- Open the official X API response codes and errors page for confirmed incidents.
- If X (Twitter) is up, work through the fixes below, cheapest first.
- Press the report button if it still fails, so other visitors see it.
Is X (Twitter) down for everyone or only for you?
X has a web app, mobile apps and a developer API. The website and apps load your timeline from backend services, and posting, search and direct messages are separate functions behind them. A single feature can break while the rest works, and limits tied to your account can look like an outage.
Our check requests x.com and the API host from outside your network. A not found reply from the API host is normal and still shows the server is answering. If both answer, the trouble is likely your session, your app version or an account limit.
The live check on this page requests x.com and api.x.com from our servers every few minutes. A normal answer from those addresses means the service is reachable from outside your network. It does not prove that every feature inside X (Twitter) works, which is why the problem reports and the fixes below matter.
What usually breaks with X (Twitter)
Timeline will not load
The feed is empty or shows a retry prompt. The web app loads the timeline separately from the page itself.
Posting and replying fail
Your post sits unsent or you see an error after tapping Post. Writes can fail while reading works.
Search and notifications lag
Search returns nothing or notifications arrive late. These are separate systems behind the app.
Direct messages
Messages do not send or conversations stay blank.
Login and session loops
You are logged out repeatedly or cannot sign in. This often relates to stale cookies or a changed password on another device.
How to fix X (Twitter) when it only fails for you
Start at the top. The first steps are the cheapest and fix most cases that are not a real outage.
- Reload the web app. Press Ctrl+Shift+R (Cmd+Shift+R on Mac) on x.com to bypass cached files, then try again.
- Try the other platform. If the app fails, open x.com in a browser. If the browser fails, try the app. This separates a client bug from a service problem.
- Clear cookies for x.com. In your browser's site settings, remove cookies and site data for x.com, then sign in again.
- Clear the app cache on Android. Open Settings, Apps, X, Storage and tap Clear cache. On iPhone, delete the app and reinstall it.
- Wait if you were refreshing a lot. Heavy scrolling, mass following or many posts in a short time can trigger account limits. Stop for a while and try later.
- Disable extensions. Content blockers and script managers can break the web app. Test in a private window.
- Update the app. Install the latest X app version from the App Store or Google Play.
- Check the clock on your device. A wrong date or time can break secure connections. Set date and time to automatic.
If none of this helps and the live check above shows the service as up, read our guide on why a website is not loading, or see how to flush DNS.
Common X (Twitter) error messages
| Message or code | What it means | What to do |
|---|---|---|
| 429 | You hit a rate limit or usage cap. The X API documentation uses this code for it. | Wait and retry later. Developers should watch rate limit headers and slow down. |
| 500 | An internal server error on X's side. | Retry later and check the status resources. |
| 502 | A bad gateway. The X API docs advise retrying later. | Wait a few minutes and retry. |
| 503 | The service is overloaded. | Retry later, with increasing delays in code. |
| 401 | Authentication is missing or invalid. | Sign in again, or check your API credentials if you build apps. |
Official X (Twitter) status and support
The company itself has the final word on outages. Check X API response codes and errors for confirmed incidents and use X Help Center if your account has a problem that is not an outage. We are not affiliated with X (Twitter).
Facts and menu names on this page were checked against the official sources below on October 25, 2026. Apps change their menus, so a setting may sit in a slightly different place in your version.
Other services people check
Frequently asked questions
How do I know if X is down or if it is just me?
Run the live check at the top. If X answers from our server but not on your device, the issue is local. Open x.com on a phone using mobile data to compare.
Does X have an official status page?
We could not verify a public status page for the consumer site. The developer documentation lists the API response codes, which helps tell an outage from a limit.
Why does X say I hit a limit when I did nothing unusual?
Limits apply to accounts and can be triggered by fast refreshing, many follows or many posts. X does not publish a fixed wait time that we could verify, so give it time before retrying.
Can only my account be affected?
Yes. Account restrictions, cached sessions and app version problems can affect one person while everyone else is fine.
Is the API down if the website works?
Not necessarily. The API has its own error codes, such as 503 for overload, and can fail separately.