Is Twitter down right now, and how can you tell when X has no public status page?
Is Twitter down? X has no public status page for its app, so check @Support, X's developer status page, then your own device and network.
To tell if Twitter is down, check X's own signals first and your own setup second, because X has no public status page for its app or website. X posts about technical issues from its @Support account, and its developer status page and incident history cover the API, which is a hint and not a reading of the consumer app. If those are quiet, test another device, another network and the browser against the app.
Below: what each X source really covers, how to read outside signals, and the fixes X documents when the problem is on your side.
X has no public status page for Twitter's app or website
Twitter is now X, and the question "is Twitter down" has no official page that answers it for ordinary users. X doesn't publish a live status board for the app or for x.com.
An older one is still referenced. X's help page on limits says it will post an update on the X status site, and it links an address from the Twitter years.
That address did not load when it was checked for this article. Treat the link as dead.
So anyone who points you to "the official Twitter status page" is pointing at something that isn't there.
What X does offer is a support account and two developer pages, and each has limits.
The @Support account is X's channel for technical issues
One consumer-facing channel is named in X's help pages. On its page about limited reach, X says it uses @Support to update the community about technical issues.
That makes @Support the first place to look. If X is having a wide problem, this is where its help pages say it will speak.
There's an obvious catch. The account lives on X, so a full outage can stop you from reading it in the app.
Try it in a browser as well as the app. If the profile loads and nothing recent mentions a problem, that is a small piece of evidence that the service is up.
What X's developer status page shows
X runs a developer status page for people who build on its platform. X's developer support documentation describes it as real-time service availability.
Its scope is stated just as plainly. The page lets you check the current operational status of X API v2, the Enterprise APIs and the Developer Console.
That is the API platform, not the consumer app. A green board there doesn't prove the app on your phone is working.
It is still useful. Trouble reported on the developer side is a reason to suspect a wider problem, and X's own incident log shows the two can coincide.
What X's incident history records
The second developer page looks backwards. X's incident history is a record of past incidents, outages and service disruptions affecting the X API v2, Enterprise APIs, Ads API and streaming endpoints.
Entries are listed by month, with start and end times in UTC. Closed ones carry the note "Incident has been resolved."
The log does reach beyond developers at times. It has carried at least one entry titled as an X site-wide outage, tied to degraded API endpoints.
Use it to confirm what already happened. If the service stumbled an hour ago and is back, this page is where a record may show up.
Outage trackers and other networks are crowd signals
Most people check an outage-tracking site or search another social network. Both can be helpful, and neither is official.
No X page names a third-party monitor or says how many user reports amount to an outage. These sites count complaints from the public, and X doesn't publish a threshold for reading them.
Read them as a crowd, then. A sudden wave of people saying the same thing at the same minute suggests the problem is larger than you.
A thin trickle means little. Someone, somewhere, always has a broken connection.
News coverage works the same way. It confirms a large outage after the fact, and it rarely helps in the first few minutes.
Is Twitter down, or is it your connection?
Three quick tests separate the two. These are practical checks, not steps from X's documentation:
- Another device: open X on a different phone or computer.
- Another network: switch between Wi-Fi and mobile data and try again.
- App against browser: if the app fails, open x.com in a browser, and the other way round.
If X works anywhere, Twitter is not down. The fault is in the device, the network or the app that failed.
X's own first step agrees with this order. Its help page for the website says that if you're not able to launch x.com, check your network connection.
How to check X in a browser when the app won't load
X's fallback for a failing app is short: visit x.com in your browser. If the site misbehaves there as well, X's page on x.com issues gives four things to try:
- Open a private or incognito window and load x.com.
- Update your browser to its most recent version, or try an alternate browser.
- Clear your browser's cache and cookies.
- Disable browser add-ons, and turn ad-blocking software off one at a time.
X says many issues can be resolved by making sure you're using the most recent version of your browser. The fourth exists because some browser extensions can interfere with actions performed on X.com.
If a private window works and a normal one doesn't, the cause is in your browser, not at X.
A VPN can make Twitter look down
X addresses VPNs directly. If you're connected to a VPN, it says, try turning it off.
It also says who to ask next. If turning off the VPN fixes your connectivity issue, you'll need to contact your VPN provider for help.
This is a quick test and a clear result. X loading without the VPN and failing with it tells you the outage is in the tunnel.
Fixes X documents for the Android app
X's page on the Android app sets out an order. Work down it and stop when the app recovers:
- restart your device
- make sure you have a strong data connection, or try an alternate Wi-Fi connection
- clear the app's data in the device settings
- log out and log back in
- uninstall and reinstall the app
The Wi-Fi line comes with a diagnosis. If one connection works and the other does not, X says it is most likely that the Wi-Fi connection does not accept SSL or is blocking X.
Clearing data is milder than it sounds. X says it won't remove your account from the app, but it will reset your notification and sync settings.
Fixes X documents for the iPhone and iPad app
The iOS page is shorter, and it starts with a requirement. The X for iOS app is available for devices running iOS 14.0 and above, and X no longer supports older versions.
An old iPhone can therefore look like an outage. X says that on iOS 13.7 or lower, the app may not update to more recent versions, while X itself is fine.
Check the system version before anything else. If it's current, uninstalling and reinstalling the app is the last step X lists.
When neither helps, go back to the browser test. The site working while the app fails keeps the problem on your device.
Logging out of X to fix a problem can cost you drafts
X does suggest logging out, saying it may help solve the trouble you're experiencing. On Android the price is stated: logging out of your account will clear your drafts.
The website is kinder. X says a web logout keeps a draft, which you'll find under "Unsent posts" and then "Drafts".
Two-factor users have one more thing to do first. X says to store a backup code before logging out.
So copy anything you care about before you sign out, and have the backup code ready.
Errors on X that look like an outage but aren't
Some failures are aimed at your account, not at the service. X documents two common ones.
The first is a limit. If you reach one, X says, it will let you know with an error message telling you which limit you've hit.
The second is a sign-in lock. After too many failed sign-ins, X locks further attempts, and that lock lasts about an hour.
Neither means the service is down. Everyone else is posting normally, and your account is the one being held back.
Limits on Twitter can tighten when the site is busy
There is a middle state between working and down. X's page on X limits says its limits may be temporarily reduced during periods of heavy site usage.
On a day when everyone is on X at once, you may hit a cap sooner than usual. The service is up, and it's rationing.
Wait and try later. X says that when you hit a time-based limit, you'll be able to try again after the time limit has elapsed.
Missing posts and detached replies can be X's own technical issues
A subtler symptom is content that doesn't show. Your post isn't in search, or a reply has come loose from its conversation.
X accepts some of this as its own doing. It says such cases may be due to some current technical issues and limitations of the service.
This is the kind of partial trouble @Support exists to announce. Check there before you assume your account has been penalized.
When one part of Twitter fails and the rest works
Partial failures are common. The timeline loads but images don't, or one tab stays empty.
X points to connected apps as one cause. It suggests reviewing your "Apps" settings and revoking access you don't need.
A single feature failing is a different problem from an outage, and it usually has a narrower fix.
An empty feed of the people you follow, for instance, is covered under the Following tab not working.
Name the part that failed before you search for help. "X is down" and "one tab is empty" lead to different answers.
How to report a problem to X
If nothing on your side explains it, tell X. Its help pages encourage you to let it know by reporting the issue through its support forms.
Write down what you saw first:
- the device
- the app or browser
- the time
- the exact wording of any error
X doesn't promise a personal reply. A report adds your case to what X can see, which is the useful part.
Is it X or is it you? A way to decide
Go in this order:
- @Support mentions an issue: it's X. Wait.
- The developer status page shows trouble: probably X. Wait, and check again later.
- X works on another device or network: it's your setup. Use X's app and browser fixes.
- You see a named limit or a lock message: it's your account. Let the time pass.
If none of these fits, report it and try again in a while.
Start with the test that takes ten seconds: open x.com in a private window.
Common questions about Twitter outages
Which X accounts post developer updates?
X's developer documentation says to follow @API for live updates on API changes and service issues, and it also names @XDevelopers.
Can you fully uninstall a preloaded X app on Android?
Not always. X says it may not be possible to remove the app completely, and that uninstalling will uninstall the latest update.
Does the incident history show whether an outage is over?
For past entries, yes. Each one lists UTC start and end times, with the note "Incident has been resolved."