# Why Is Twitter Not Working - Common Issues and How to Fix Them > Login loops, blank timelines, failed uploads and rate limits: how to tell an outage from a problem at your end, and what fixes each. - Source: https://tweetsweep.com/blog/why-is-twitter-not-working-common-issues-and-how-to-fix-them - Published: 2025-01-12 - Updated: 2026-08-16 - Reading time: 5 min --- ## Platform status Whenever X stops working, the cause is nearly always in one of five places: the platform itself, your connection, the app build, cached data, or your account state. This is much faster than checking them randomly. Start with the platform. Open a status tracker and glance through the last fifteen minutes worth of reports. No local change will hold, if the graph spikes or the same failure is reported by others. Partial outages of X have been common since 2023. Messages send but charts dies timeline stoodstill So images work on the website and not in the iOS app, or vice versa. You trained on compose works, and refresh didnt work. If the tracker silent, and your feed/search/notifications break on your own phone at once, proceed to next check. If only one is broken, which surface? That detail determines whether you clean cache or change networks or wait. ## Network connection Use WiFi or Mobile Data Defaulting to the app being wrong, if problem travels to network fault, not case. X domains often filtered by corporate and campus Wi-Fi, or TLS intercept causing application rejection. In under a minute, that gets isolated to a guest network or phone hotspot. The path should be fine if both networks fail the same way. If Wi-Fi is the only thing that crashed; forget the network and reconnect again. Only if cellular is failing, turn airplane mode on for 10 seconds to kick off a new radio attach. The same class of failure can be caused by VPN clients. Instead of pausing the VPN, turn the VPN off completely and reopen X; a paused connection from split-tunnel and always-on profiles leaves a stale route that is not cleared. ## App build and process Quit the app and launch it again. For iPhone, swipe up from the bottom and flick the X card away. For Android, open Recents and swipe the card away or use Force stop in App info A hung process holds a dead connection and will not recover by itself. Next go into the App Store or Google Play and see if a update is available. X deprecates old builds. They'll cease authentication or simply no longer render the timeline after some time. The store page is the only version check that can be reliably trusted. If you loaded on an old apk or hung onto a TestFlight build after its time was up, then replace it with the store build. ## Cached media and extensions Clear cached media on Mobile App Open Settings and privacy > Accessibility, display and languages > Data usage. After that, just use the control to clear your cached media (not the one that logs you out). A corrupted or buggy image and video cache is a known reason why timeline seems empty or frozen on the first cell. Create a new private window without extensions in the website Some content blockers make X unusable, ad blockers and privacy filters break it all the time, script blockers do too. The remove endpoints that the site requires for the timeline, for the compose box, or once again for media. When you only have to load one or the other in a private window with no extensions it shows you whether the problem is profile or page. If the private window helps, disable individual extensions in a normal window until the timeline comes back. Try a second browser as well. Such as a corrupt profile or a saturated disk cache and/or having stuck service worker making only one browser state become "ghosted". ## Rate limits If you see a rate limiting message, you've hit either a read or action ceiling. The only fix is waiting. It typically passes within an hour. Background polling also burn the same budget (rapid refresh, aggressive search, third-party clients). It is just faster to close every extra tab and let the app idle instead of Retry. A rate-limit error is neither a ban nor an outage. Different ceiling can trip each of posting, liking, following and loading the home timeline. When one action fails and another does not, wait on the failed. Do not sign up to a new account as a way around it. ## Account restrictions To check only the posting fails, open Settings and privacy then Your account; you may also find it under restricted or locked condition. Suspend and temporary caps result in mistakes that appear to be bugs. The compose button could just sit there and be still, or you get some vague try againt later. In fact, the account page shows the true reason. Here is where phone and email verification holds, copyright strikes, and spam flags end up. In a case where the account is locked, do not reinstall the app but complete it using the prompt. A restriction cannot be lifted by reinstalling. In case the app does not load and you are unable to reach Settings, use the website in the same account. Even a password reset or a forced logout from the security page may leave the mobile app in such a loop. If so reset the session next. ## Session tokens Sign out and sign back in. This is resetting a session token that goes stale, which accounts for a disappointmentingly significant share of permanent errors. Your app enters a half-authenticated state: it will show a cached timeline (if you've been to this page before) but all writes and every refresh fail. Signing out clears that token. Signing in fetches a new one. Not just the web, do this on the device that fails. Sessions are per client. Commenting or searching once signed in, but wait for the timeline to load a full round of posts first. That can bring about the stale state to recreate if you interrupt that load. If enabled, be prepared with the method for two-factor. For example, X being down can simply be a failed challenge mid-login. ## App reinstallation He only local option is to reinstall It empties out the app container: data, tokens, media downloaded by the user and leftover database files. Uninstall and reboot the phone then again install from store. Some Android devices that are missing a reboot end up with the package half removed. You will log in again and local drafts not published will be lost. Any drafts that previously synced to the account are retained. If those devices are trying on two networks and the failure persists, you cannot place the blame directly onto the device. ## Posted history But if the trigger was a post you made, the deletion is an effective cure. An account stays in a limited state that might cause the product to appear broken, after a post has tripped spam or copyright or abuse systems. Deleting the post, and then waiting, usually raises the limit without a support ticket. If the issue is an entire era of history rather than just a single post TweetSweep deletes Tweets and X posts in bulk per date. It's useful when you have a range to erase but not for a one status removal from an compose error. Wait some time before re-posting again after a bulk delete on the account Old content played Big Brothers are not always stripped away the moment the posts vanish. There is no panacea for all the issues that arise out of an outage or a bad network other than deleting. Only if the account is the constraint, and the content is causing it.