Is Twitter (X) Down Right Now? How to Check and What to Try First

When X won't load, the first question is: is it down for everyone, or just me? Answer it with three tabs, in order:

1. status.x.com — X's official system status. Green means services are healthy; yellow/red means an active incident.
2. Downdetector — crowdsourced user reports. A steep 24-hour spike is the clearest sign of a live outage.
3. Google Trends — search for "twitter down" or "x down" and set the timeframe to "past 4 hours". Sharp spikes correlate almost perfectly with real outages.

If all three agree it's down, close the tabs, take a walk, and check back in 30 minutes. X's average outage in 2024–2026 has resolved in under 90 minutes.

Since the acquisition, X has had several high-profile outages driven by a small set of recurring causes:

• Infrastructure migrations. The team consolidated data centers in 2023–2024, which caused multi-hour outages when caches got misconfigured.
• Rate-limit bugs. A famous July 2023 incident capped tweet views per day at 600 for free accounts — technically the site was up, but for many users it was indistinguishable from an outage.
• DDoS attacks. Politically-charged events sometimes trigger volumetric attacks. X's cloud partners usually absorb these within an hour.
• Bad deploys. Occasional feature rollouts (a new For You ranker, a login redesign) have taken parts of the app offline for 15–60 minutes.

None of these are things you can fix from the client side. If it's genuinely X's fault, wait it out. (For context on how the platform even got to this operational state, our acquisition timeline covers the 2022 staff exodus that reshaped reliability.)

If status.x.com and Downdetector look calm but the app won't load for you, the problem is local. In order of likelihood:

1. Cellular or Wi-Fi issue. Toggle airplane mode on and off. Try loading any other site — if that fails too, your connection is the problem.
2. DNS problem. Switch your device's DNS to 1.1.1.1 or 8.8.8.8. In 2026, ISP-level DNS filtering (accidental or otherwise) still routinely breaks x.com for pockets of users.
3. App cache. On iOS, force-quit and reopen. On Android, Settings → Apps → X → Storage → Clear cache.
4. Blocked by network. Corporate, school, and some public Wi-Fi actively block x.com. Try a cellular connection or a VPN.
5. Country-level block. X has been fully blocked in several countries in the last three years. Downdetector will show near-zero reports from those regions even during an active block; use a VPN routed through a neighboring country to test.

Sometimes X is fine but you can't access something you expect. Two flavors of that:

Locked account. If X detects unusual login activity, it can lock the account and require a phone or email verification. Complete the challenge at the login screen — that usually clears it within minutes.

Rate-limit exceeded. Even in 2026, aggressive scrolling or hitting the API too fast can put you into "Rate limit exceeded" for 15 minutes to a few hours. Close the app, wait, come back.

If you suspect X has reduced your reach specifically, read the shadowban check guide — the site being "down for you" and your posts being visibility-filtered look identical from your feed.

Once an outage is significant, X's engineering account (@XEng) posts a short acknowledgement. It's the closest thing to an official statement you'll get in real time. Follow it in a Lists column if you want to know first.

For post-mortem detail, check the X Engineering blog a day or two after the incident. Not every outage gets a write-up, but the interesting ones usually do.

If you rely on X for news or work, keep two escape valves ready. First, subscribe to the RSS feed of a news site you trust — X is dominant but not irreplaceable when it's down. Second, if you were mid-download when things broke, remember that our Tweet Viewer tool can fetch already-cached tweet media even when the main site is having issues, as long as the tweet URL itself was loadable in the last few hours. Threads and already-posted video work through the bulk downloader, so a partial CDN outage doesn't have to kill your archive plans.