Is X (Twitter) down?
Is X (Twitter) not loading, failing to refresh, or refusing to send posts? Use the checks below to determine whether the problem affects X broadly or is limited to your browser, device, account, or network.
Site Administrator
Last reviewed: September 25, 2026
LATEST RECORDED STATUS
Up X (Twitter)’s website appeared to be up and responding normally at the last check.
| Endpoint | Status | Observed |
|---|---|---|
| x.com | Operational | 2026-11-09 13:55 UTC |
Is it working for you?
0 recent reports — more reports are needed for a useful trend.
What this check can tell you
- Test X on both Wi-Fi and mobile data to distinguish a broader service problem from a network-specific failure.
- If x.com fails across several devices and networks, an X-side or upstream connectivity issue is more plausible.
- If only one browser fails, check extensions, cookies, cached site data, and browser updates before changing account settings.
- A working homepage does not rule out a partial issue affecting login, posting, media, notifications, or messages.
- Repeated DNS, timeout, gateway, or connection-refused errors can indicate connectivity or upstream problems rather than an account issue.
About X (Twitter) reliability
Understanding X availability
X can be partially or fully unavailable. The main site may fail to open, pages may load without refreshing, or individual features such as sign-in, posting, media, notifications, or messages may stop working while other parts of X remain available.
A broader outage is more plausible when the same symptom appears across multiple devices and networks. If the problem is limited to one browser, device, account, or internet connection, a local or account-specific cause is more likely.
The service record identifies x.com as X's homepage domain. Availability checks can show whether access appears widespread, but they cannot by themselves identify the cause or confirm that every X feature is affected.
How to troubleshoot X (Twitter)
Troubleshooting X (Twitter) access problems
1. Identify the exact symptom
Note what fails: a blank page, failed refresh, login loop, missing media, error message, or a post that will not send. Check whether the entire site is affected or only one feature.
Open x.com in a private or incognito window, then test another browser or device. If possible, compare your usual connection with mobile data.
When a broader outage is more likely
An X-side or upstream problem is more plausible when:
- x.com fails on multiple devices and networks;
- several X features stop working at the same time; or
- requests repeatedly return server, gateway, or timeout errors.
If these conditions apply, retry later instead of repeatedly changing account or browser settings. A working homepage does not exclude a partial disruption affecting posting, media, notifications, or messages.
Browser and device problems
If X works in another browser or a private window, the original browser may have stale site data, a conflicting extension, blocked scripts, or a browser-specific problem. Disable extensions that modify scripts, privacy controls, or page content, then clear site data for x.com and try again.
If the problem affects only one device, restart it and check its date, time, browser, and operating system settings. Avoid clearing all browser data unless you are prepared to sign in again.
Network and DNS problems
If X works on mobile data but not Wi-Fi, investigate the Wi-Fi network, router, DNS resolver, VPN, proxy, firewall, or ISP path. Restart the router only if you are authorized to do so and understand that it will temporarily interrupt the connection. Compare another device on the same network, and temporarily disconnect a VPN or proxy for a controlled test if applicable.
A DNS error, connection refusal, or timeout that occurs only on one network points more strongly to local connectivity than to an X-wide outage.
Account or feature-specific problems
If x.com loads but sign-in, posting, media, notifications, or messages fail for only one account, look for an account-specific prompt, session problem, or feature limitation. Sign out and back in only when you can do so safely. Before retrying a post or request, check whether it already succeeded to avoid duplicates.
Third-party apps and developer access
A third-party X application or integration can fail even when direct access to x.com works. Compare the affected application with direct browser access and retain the exact error or response returned by the application. Do not assume that an integration problem represents a general X outage.
Related troubleshooting guides
TROUBLESHOOTING GUIDE
ERR_CONNECTION_TIMED_OUT
`ERR_CONNECTION_TIMED_OUT` means the browser waited for the destination server or an intermediary to respond, but no usable response arrived before the connection timeout. Common causes include an unreachable or overloaded server, a firewall silently dropping traffic, incorrect DNS, a broken network route, or a CDN or proxy that cannot reach the origin. Test from another network first, then check DNS, infrastructure health, firewall rules, and resource usage.
TROUBLESHOOTING GUIDE
ERR_CONNECTION_REFUSED
ERR_CONNECTION_REFUSED means the browser reached a destination address, but the connection was rejected before the website returned a response. Common causes include a stopped web server, no process listening on port 80 or 443, a service bound only to localhost, an incorrect DNS destination, or a firewall rule blocking access. Check the destination and listener first, then test from an external network.
TROUBLESHOOTING GUIDE
502 Bad Gateway
A 502 Bad Gateway means a reverse proxy, load balancer, or CDN could not obtain a valid response from the backend server. Check the backend process, proxy error log, upstream host or port, socket permissions, resource limits, and CDN-to-origin access. The fault is usually between servers rather than in the browser.
TROUBLESHOOTING GUIDE
503 Service Unavailable
A 503 Service Unavailable response means the service cannot handle the request at that time. Common causes include exhausted CPU, memory, worker, or connection capacity; incomplete maintenance mode; an unavailable database or other dependency; or a proxy, WAF, rate limiter, or load balancer returning 503. Identify which layer generated the response, then review logs and resource usage before changing settings.
TROUBLESHOOTING GUIDE
504 Gateway Timeout
A 504 Gateway Timeout means a proxy, CDN, load balancer, or gateway waited for a backend response but its timeout expired first. The backend may still be running; common causes include slow database queries, overloaded workers, long-running tasks, delayed third-party services, and restrictive intermediary timeouts. Compare direct backend timing with the full gateway path before changing timeout settings.
TROUBLESHOOTING GUIDE
DNS_PROBE_FINISHED_NXDOMAIN
DNS_PROBE_FINISHED_NXDOMAIN means DNS could not find the exact hostname requested. Check the spelling, subdomain, authoritative nameservers, required A, AAAA, or CNAME record, and domain registration status. If the DNS change was recent, cached negative responses may persist; it is usually a DNS or domain configuration issue rather than a web-server outage.
Sources & references
Source guidance
Use x.com as the direct service destination when testing access. For confirmation of a suspected platform-wide incident, consult X's official service announcements, support communications, or account notices rather than relying solely on third-party outage reports.
For application and integration problems, consult the relevant official X developer documentation and compare its reported error with direct browser access. For browser, DNS, VPN, proxy, or network errors, consult the documentation for the affected browser, operating system, router, DNS provider, or network administrator.
How this check works
Every time this page loads, our server makes its own request to x.com (and its API domain, when applicable) and reports what it got back — a real HTTP response, a timeout, or a connection failure. That result is cached for up to 2 minutes.
This confirms external reachability; it does not test every feature, region, account, or network path. Cross-check the official status page when one is available.
Embed this live status badge
Add this badge to a dashboard, documentation page, or blog. The badge reads the cached Erriscope observation and links back to this status page.
<a href="https://erriscope.com/status/x-twitter/"><img src="https://erriscope.com/status/badge/x-twitter.svg" alt="X (Twitter) status on Erriscope" width="210" height="34"></a>Frequently asked questions
Is this the same as X (Twitter)'s official status page?
No. This is a live, one-off connectivity check run from our own server, not X (Twitter)'s own incident reporting. Their official status page can show partial, regional, or component-level issues our single external check cannot detect.
Why does this show "Up" when X (Twitter) feels slow or broken for me?
A basic reachability check confirms that the server responded to our request. It does not test every feature, region, ISP, browser, or account-specific issue.
How often is this checked?
A check is refreshed after the two-minute cache expires. The displayed check time shows when the observation was made.
Does an API outage mean the whole product is down?
Not necessarily. Many services split their website and API onto separate infrastructure, so one can fail while the other keeps working.
How can I tell whether X is down for everyone?
Test x.com from more than one device and network. If the same failure affects multiple locations and several X features, a broader outage or upstream connectivity issue is more likely. A problem limited to one browser, device, or connection is less likely to be global.
Why does X load but not refresh or send posts?
The initial page can load even when later requests are failing. Possible causes include a partial service issue, an expired session, an account-specific problem, or a browser or network failure. Test a private window, another browser, and another network to narrow down the cause.
What should I do if X works on mobile data but not Wi-Fi?
The Wi-Fi network, router, DNS resolver, VPN, proxy, firewall, or ISP path is the more likely area to investigate. Restart the router if authorized, test without a VPN or proxy if applicable, and compare another device on the same Wi-Fi.
Why does X work in one browser but not another?
The failing browser may have stale site data, a conflicting extension, blocked scripts, or a browser-specific problem. Try a private window, disable relevant extensions, and clear site data for x.com.
Is a third-party X app outage the same as an X outage?
Not necessarily. A third-party application or integration can fail while direct access to x.com works, or it can have a separate authentication, network, or request problem. Compare both paths and keep the exact error from the affected application.
Should I keep retrying if a post will not send?
No. First check whether the post actually appeared, then test the connection, browser, or account session. Repeated retries can create duplicate posts or requests if the original action succeeded but the response was delayed.
This is a live connectivity check from our server, not an official statement from X (Twitter). A down result may also reflect a regional or partial outage.
LIVE CHECKS
