Live Domain Check

Is X Down? Check x.com Status and Outages

Check if X is down right now (x.com). Run a live multi-region check to see whether X is offline for everyone or just you.

Get official X outage status updates, support links, and targeted troubleshooting steps in one page.

Ready

Running automatic check…

Checking reachability from multiple regions.

Checked -

Verdict -

Response Time -

Final URL -

Regional checks 8 regions

Rate:

No ratings yet.

About X Outages and Server Issues

X incidents often surface as timeline load failures, delayed post publishing, broken notifications, or login/session errors. Traffic can also differ between x.com and legacy twitter.com endpoints, so testing both helps identify redirect and edge-cache issues.

For X, incident signals are often feature-specific: Posts publish slowly or fail with generic retry errors. Replies and notifications are delayed by several minutes. If this matches what you see on x.com, it usually points to partial degradation instead of a full outage, so confirm with official status updates and a second-network retest.

Official X Status, Support, and Social Channels

X does not maintain a consistently detailed public consumer outage dashboard, so combine official support channels with direct endpoint checks.

X Help Center

Official product support and troubleshooting.

X Support

Official support account used for broad issue communication.

X Developer Docs

Useful when API and platform behavior diverge.

Official X Social Profiles for Live Updates

Official teams often post outage status updates and recovery progress through these social channels.

Common X Problem Patterns

Use these service-specific patterns to identify likely root cause quickly and choose the right next step.

Posts publish slowly or fail with generic retry errors

When posts publish slowly or fail with generic retry errors, feature-level traffic may be failing while basic pages remain reachable. Test read and write actions separately on x.com, then compare from another connection to separate local route issues from platform instability.

Replies and notifications are delayed by several minutes

When replies and notifications are delayed by several minutes, feature-level traffic may be failing while basic pages remain reachable. Test read and write actions separately on x.com, then compare from another connection to separate local route issues from platform instability.

Media uploads fail while text posts still work

When media uploads fail while text posts still work, storage or sync pipelines are often degraded independently from page rendering. Retry a small test action on x.com, switch network once, and keep error code plus final URL for escalation to X support.

x.com and twitter.com redirects differ by region

This usually indicates redirect or edge-cache propagation differences, not always a full outage. Check both domains on mobile data and Wi-Fi, and compare final URLs before you clear DNS or browser cache.

How to Check if X Is Down

Practical steps to follow when x.com seems down. Use this checklist to confirm whether X is down for everyone or only for you.

1. Check in two places

Run x.com in WebsiteDown.org first, then open x.com in your own browser. If results disagree, the issue is often local rather than global.

2. Verify service status

Check the official X service status page and compare timestamps with your failed checks.

3. Isolate network path

Test related hosts such as twitter.com, api.x.com. If they work while x.com fails, this points to a partial endpoint issue.

4. Escalate with evidence

Capture final URL, status code, and response time for x.com, then share those details with X support for faster triage and recovery.

How to check if X is down (x.com): 4-step workflow. — WebsiteDown.org incident workflow for troubleshooting x.com availability issues.

If X Is Not Working Only For You, Start Here

Use these local troubleshooting steps after the down-check workflow when X seems broken only for you. This section focuses on app, browser, account, and network fixes.

1. Compare browser sessions

Open x.com in your current browser, then test in a private window or second browser. If only one session fails, the issue is usually local cache, cookie, or extension state.

2. Reset account session once

Sign out and sign back in one time, then retry the failing action on x.com. Avoid repeated password or security resets until you confirm this is not a broader X issue.

3. Remove network interference

Temporarily disable VPN, proxy, private DNS, and filtering extensions. Then switch between Wi-Fi and mobile data to isolate route-level differences.

4. Capture support-ready evidence

Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting X support.

Frequently Asked Questions

Is X down for everyone or just me?

Run the automatic multi-region check on this page for x.com. If most regions fail at the same time, X is likely experiencing a broader outage or partial incident.

If only one or two regions fail, the issue is usually local to your network path (DNS resolver, ISP route, VPN/proxy, or firewall). Re-check after 2 to 5 minutes and compare Wi-Fi with mobile data.

Where can I find official and real-time X outage updates?

Use the Official Status, Support, and Social Channels section above in this order:

Official status: X Help Center
Support/help: X Help Center and X Support
Social updates: X Help Center and X Support

Official dashboards are authoritative but can lag during the first minutes of an incident. Combine those sources with this checker to confirm whether X is down globally, regionally degraded, or only affecting specific users.

Why is X down for me but up for others?

That pattern usually points to path-specific issues rather than a full X outage. Common causes include:

Stale DNS cache or resolver mismatch
ISP peering/routing issues between your network and the provider
VPN/proxy exit-node blocking, geo filtering, or WAF policies
Browser extensions, cached sessions, cookies, or temporary rate limits

Test in a private window, temporarily disable VPN/extensions, and retry from a second network. If one feature fails while the homepage still loads, treat it as a partial incident.

What should I do first if X is not working?

Use this quick triage sequence for x.com:

Run the live check for x.com
Open the official status/support links above
Test another device or another network
Capture the exact error code, timestamp, and final URL
Only then clear cache or flush DNS if results look local

This order helps you avoid unnecessary account resets when the X issue is provider-side.