Live reachability
The regional cards above show whether x.com is reachable now and whether failures cluster globally or by route.
Service Diagnostic
Run a live multi-region check for x.com and compare the result with official X sources, known failure modes, and local troubleshooting steps.
This page is built for outage triage: first confirm reachability, then verify official signals, then decide whether the problem is global, regional, or local to your account/network.
Checking x.com reachability from multiple regions.
The regional cards above show whether x.com is reachable now and whether failures cluster globally or by route.
The recent-check panel below adds public check history for this exact page when data is available.
This check confirms whether x.com responds from regional probes. It cannot prove every feed, post, notification, or mobile-app path inside X.
Recent verdict history from users checking this specific page.
Loading recent checks...
For X, start by separating x.com public reachability, home feed refresh, and account session. A reachable x.com does not prove every X workflow is healthy.
Use these provider-controlled or provider-owned sources after the live check, especially when the verdict is mixed or the issue only affects one workflow.
Confirms whether the primary x.com web surface is reachable outside the WebsiteDown.org probe.
Official product support and troubleshooting.
Official support account used for broad issue communication.
Useful when API and platform behavior diverge.
These are provider-controlled channels from the source list above. They are useful during incidents, but they can still lag behind live reachability symptoms.
These patterns help distinguish full x.com downtime from partial service degradation, account problems, or route-specific failures.
Use these steps when WebsiteDown.org or official sources suggest X is generally reachable, but your own session still fails.
Use this workflow to compare the WebsiteDown.org result with official sources, your own browser, and a second network before changing account or device settings.
WebsiteDown.org checks public reachability for x.com and separates that signal from product-specific symptoms inside X.
The X profile on this page is scoped to x.com, categorized as Social / Community, and grouped under x. It cross-checks related hosts (twitter.com, api.x.com, mobile.twitter.com), uses verification sources such as Official website, X Help Center, X Support, X Developer Docs, and compares nearby diagnostics including xAI, Facebook, Instagram, WhatsApp so parent, child, and sibling service outages do not get blended together.
For X, check x.com session state, For You timeline loading, Following timeline freshness, post creation, repost/like actions, media embeds, direct messages, Spaces entry points, and search recency. X incidents often involve timeline ranking APIs, account sessions, or media upload pipelines even when the landing page responds. Use this page for X-specific social graph and timeline behavior, not a generic community platform check. Strong X-specific evidence includes timelines stuck on old posts, posting returning retry prompts, media uploads failing after progress completes, DM inboxes loading blank, Spaces failing to join, search showing stale results, or logged-out users seeing a different status than logged-in users. Weak evidence includes a single suspended account, rate limiting after heavy usage, private post visibility, or a browser extension blocking embeds.
WebsiteDown.org keeps the live verdict, official sources, and service profile separate so you can see what is measured and what still needs confirmation.
These dates describe the editorial registry behind this page. Live check timestamps are shown in the result panel above.
Use these guides when the live verdict, official sources, and your own symptoms disagree.