X returns to the air after failure with 36 thousand reports and correction by Cloudflare
A wave of access failures affected the X platform (formerly Twitter) this Monday morning (June 22, 2026), with users in several regions reporting problems loading the feed and publishing content. Reports quickly grew on digital service monitoring platforms, indicating a widespread disruption to the system.
The Downdetector website, which tracks digital service interruptions in real time, recorded a significant spike in complaints related to X. Thousands of users reported difficulties from the early hours of the day, with the number of notifications increasing exponentially around 9am (Brasília time).
Many internet users expressed frustration on social media, using other platforms to confirm that they were not alone in experiencing the glitches. Error messages such as “Oops, something went wrong” or extreme slowness were the main complaints, preventing publications from being viewed and new messages being sent on the platform.
Company X does not comment on the instability in the system
At the time of publication of this news, company X had not issued any official statement explaining the cause of the interruption or informing about the expected normalization of services. The lack of information generated even more uncertainty among affected users and companies that depend on the platform for communication.

Impact of failures and history of platform instability
Interruptions on large-scale platforms like X can have considerable impacts, from the loss of real-time communication for millions of people to losses for companies that use the service as a marketing or customer service tool. X’s reliability has been a recurring theme, especially after management and name changes, which preceded other episodes of instability, raising concerns about the service’s infrastructure.
Faced with the interruption, technology experts recommend that users try some basic actions, such as checking the internet connection, clearing the browser or application cache and waiting for new information from the platform. In many cases, resolving the problem depends on internal intervention by the X technical team.
















