X had another one of its “trust us, it’s fine” mornings, this time in Spain. Starting around 9:50 a.m. local time (3:50 a.m. ET), users reported the same maddening symptom: the app opens, your account loads… and then your timeline is a blank wall.
People could still get into their profiles, but the main feed wouldn’t pull in new posts, or even old ones. For some users, the only thing showing was a handful of pinned posts on big, high-traffic accounts. Everything else? Gone.
Blank timelines, pinned posts, and a whole lot of nothing
The early reports were weirdly consistent. X would launch normally on both mobile and desktop, but it wouldn’t actually deliver the goods. No fresh posts. No scrolling back in time. Just a feed that refused to update.
Some users said they were seeing “who to follow” suggestions, because nothing says “functional platform” like being prompted to follow more accounts while you can’t see any content from the ones you already follow.
Search also reportedly broke, so discovery took a hit, too
Complaints piled up on Downdetector and spilled onto rival apps like Threads, where users vented that they couldn’t see posts and, in some cases, couldn’t run searches at all.
When both the feed and search start failing at the same time, it usually points to trouble in the systems that distribute and surface content, less “your phone is acting up,” more “something upstream is on fire.”
Déjà vu: Spain saw a similar outage about two weeks ago
Spanish users also dealt with a disruption roughly two weeks ago, and this latest hiccup is feeding a growing suspicion: X is getting flakier, more often.
And no, these outages don’t always look identical, which makes it harder to pin them on one repeatable cause. But the pattern, service stutters, timelines go empty, features fail, feels familiar.
Web vs. Android: uneven behavior as service sputtered back
Reports from people testing both the browser version and the mobile app showed inconsistent behavior. In some cases, the web version would intermittently load older posts again, while the Android app stayed stuck longer on a loading screen.
Others said they got an error message saying posts couldn’t be retrieved and to try again later, the classic digital shrug.
Downdetector spike after 9:50, easing around 10:40
Downdetector’s outage graph jumped sharply after 9:50 a.m., a sign the problem wasn’t isolated. Around 10:40 a.m. local time (4:40 a.m. ET), reports began to drop, suggesting a gradual recovery, at least for some users, in some places, on some devices.
But the comeback sounded patchy: partial, uneven, and dependent on when and how you logged in.
