Check X's live status in seconds. See whether Twitter / X is down for everyone or just on your end — with real-time community reports from other users.
Check X Status Now →Free · No signup · Instant global test
Click the button above. IsItGoneDown runs a global test from our server and a local test from your browser simultaneously. If both fail, X is genuinely down. If only your local test fails, the issue is your network or device.
Live community votes are especially useful for X because many "outages" are actually rate-limit errors that only affect some users.
X has had more visible outages since its acquisition than in previous years. When it happens, community reports spike fast because X users talk about the problem on other platforms.
X imposes daily read limits, especially for non-subscribers. If you see "rate limit exceeded", X isn't down — you've hit the cap. It resets daily.
X has many microservices: login, timeline, media, DMs, notifications. Any one can fail independently. A blank timeline while DMs still work is a partial outage.
X is blocked in several countries and throttled on some corporate, school and public Wi-Fi networks. If X fails only on one network, that's almost always why.
X restricted its API in 2023, breaking many third-party clients. If X.com works in a browser but your client doesn't, the client may be affected.
A stale login session can cause "something went wrong" errors on every action. Log out and back in, or clear cookies for x.com and twitter.com.
Given X's rate limits, many "Twitter is down" moments are actually just hitting a daily cap. A real X outage produces a flood of user complaints within minutes — typically visible on Mastodon, Bluesky, Threads, and IsItGoneDown.
Run the live check above for global status and real-time community reports.
If you see "rate limit exceeded", X isn't down — you've hit the daily read cap. It resets daily.
Same as above — a rate-limit error, not an outage. Wait 15 minutes and try again.
X is blocked in several countries. A VPN typically restores access.
Usually a partial service outage or a cached session issue. Log out and back in, or try the web version.