Live Domain Check

Is X Down? Check x.com Status and Outages

Run a live reachability check for x.com. Compare the regional responses with the problem you see in X.

Find X help and reporting links, specific checks, and step-by-step guidance below the live result.

Ready

Running automatic check…

Checking reachability from multiple regions.

Checked -

Verdict -

Response Time -

Final URL -

Regional checks 8 regions

Rate:

No ratings yet.

Understanding X connection and service problems

X timeline access, posting, direct messages and developer API calls have different scopes.

The checker above requests x.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual X action that failed. A homepage response alone cannot verify an account, app workflow or transaction.

X status information and official help

X help and reporting

Use X Help for consumer account/technical issues and developer support for API errors.

Open x.com

Compare the website entrypoint with your browser or app. This website link is separate from a provider incident dashboard.

No separate incident dashboard is linked here. Use the official product help and any current announcements it links to; this does not mean that no outage is possible.

Where to report problems with X

Use X Help for consumer account/technical issues and developer support for API errors.

Open X help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.

Details to include in your report

Feature, post/request reference, client/version, error and time without private messages or tokens.

Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to X.

What to check when X is not working

These are troubleshooting comparisons, not claims that X is currently experiencing a particular incident.

Start with the action that failed

Compare a public post with the signed-in feature and check whether a supposedly failed post actually appeared.

Narrow down the affected service

Use X Help for account/technical issues and developer support for API failures; distinguish a limit or restriction notice from an outage.

Read the actual checker response

A 403 or 429 means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.

How to check if X is down

Capture the original failure. Save the exact action, error and time before refreshing. Preserve drafts and check whether a submission already completed.
Run the x.com check. Compare each response, the measurement time and available locations. A repeated click can reuse a cached observation.
Compare the relevant provider information. Open X help and use its guidance or announcements for the exact feature. Do not treat a general homepage as an outage bulletin.
Test one useful difference, then report. Compare another permitted session, network or service component using the tailored checks above. Send the result and the actual app error through the reporting route on this page.

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, compare its account, cookie and extension context before assuming the entire service is unavailable.

2. Preserve a working account session

Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader X issue.

3. Compare permitted network paths

Compare Wi-Fi and mobile data only where you are permitted to do so. Keep required VPN, proxy and security controls in place, and record which network fails.

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 about X problems

Is X down, or is the problem limited to one feature?

Run the x.com check and compare its original timestamps and responses with your actual error. X timeline access, posting, direct messages and developer API calls have different scopes.

Where can I report a problem with X?

Use the official help/reporting resource linked above. Use X Help for consumer account/technical issues and developer support for API errors.

What should I check first when X is not working?

Compare a public post with the signed-in feature and check whether a supposedly failed post actually appeared. Use X Help for account/technical issues and developer support for API failures; distinguish a limit or restriction notice from an outage.

What information helps X support investigate?

Feature, post/request reference, client/version, error and time without private messages or tokens.